Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Benjamin Robin (Schneider Electric)" <benjamin.robin@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: "Benjamin Robin (Schneider Electric)"
	<benjamin.robin@bootlin.com>,
	thomas.petazzoni@bootlin.com, mathieu.dubois-briand@bootlin.com,
	miquel.raynal@bootlin.com, antonin.godard@bootlin.com,
	kamel.bouhara@bootlin.com, pascal.eberhard@se.com,
	jpewhacker@gmail.com
Subject: [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info
Date: Fri, 21 Nov 2025 10:54:08 +0100	[thread overview]
Message-ID: <20251121095415.288301-1-benjamin.robin@bootlin.com> (raw)

(I'm resending this series because it was blocked for spam, sorry for the noise)

Currently only CVEs with "Patched" status are exported in SPDX 3.0 files.
Moreover, CVE annotations provided by the CVE_STATUS_GROUPS variable are not
exported, since previously this was only handled by cve-check.bbclass.

Also the vex.bbclass is missing, which will helps users to extract all the
information needed to do a CVE analysis outside of Yocto.

These changes are realized since scarthgap Long Term Support ends in April
2028. Without these improvements, it is not possible to do a proper CVE
analysis outside of Yocto, solely based on the SBOM, since there are missing
CVE annotations in the artifact files. We want to be able to extract all CVE
annotations provided by the CVE_STATUS and the CVE_STATUS_GROUPS variables.

With this backport, great care has been taken to avoid breaking compatibility.
This is why the get_patched_cves() API was not changed. Everything that was
needed is implemented in the associated .bbclass:
 - Patch 1/5 modifies spdx30_tasks to extract all CVE status. This commit was
   not cherry-picked from master.
 - Patch 2/5 backports the vex.bbclass, but modify it a bit to use the old
   get_patched_cves() API.
 - Patch 3/5 and 4/5 are cherry-picked, these commits move the extraction of
   CVE_STATUS_GROUPS information to lib/oe/cve_check.py
 - Patch 5/5 is cherry-picked to backport a vex.bbclass improvement

This series should be applied on top of [1]:
[scarthgap] spdx30: fix cve status for patch files in VEX

[1]: https://patchwork.yoctoproject.org/project/oe-core/list/?series=40606

Benjamin Robin (Schneider Electric) (5):
  spdx30: provide all CVE_STATUS, not only Patched status
  vex.bbclass: add a new class
  cve-check: extract extending CVE_STATUS to library function
  spdx: extend CVE_STATUS variables
  vex: fix rootfs manifest

 meta/classes/cve-check.bbclass   |  17 +-
 meta/classes/spdx-common.bbclass |   5 +
 meta/classes/vex.bbclass         | 319 +++++++++++++++++++++++++++++++
 meta/lib/oe/cve_check.py         |  22 +++
 meta/lib/oe/spdx30_tasks.py      |  31 +--
 5 files changed, 365 insertions(+), 29 deletions(-)
 create mode 100644 meta/classes/vex.bbclass

-- 
2.51.2



             reply	other threads:[~2025-11-21  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  9:54 Benjamin Robin (Schneider Electric) [this message]
2025-11-21  9:54 ` [scarthgap v2 1/5] spdx30: provide all CVE_STATUS, not only Patched status Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 2/5] vex.bbclass: add a new class Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 3/5] cve-check: extract extending CVE_STATUS to library function Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 4/5] spdx: extend CVE_STATUS variables Benjamin Robin (Schneider Electric)
2025-11-21  9:54 ` [scarthgap v2 5/5] vex: fix rootfs manifest Benjamin Robin (Schneider Electric)
2025-11-21 10:35 ` [OE-core] [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info Marta Rybczynska
2025-11-21 10:42   ` Benjamin ROBIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251121095415.288301-1-benjamin.robin@bootlin.com \
    --to=benjamin.robin@bootlin.com \
    --cc=antonin.godard@bootlin.com \
    --cc=jpewhacker@gmail.com \
    --cc=kamel.bouhara@bootlin.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pascal.eberhard@se.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox