From: "Marko, Peter" <Peter.Marko@siemens.com>
To: "Benjamin Robin (Schneider Electric)"
<benjamin.robin@bootlin.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "ross.burton@arm.com" <ross.burton@arm.com>,
"olivier.benjamin@bootlin.com" <olivier.benjamin@bootlin.com>,
"mathieu.dubois-briand@bootlin.com"
<mathieu.dubois-briand@bootlin.com>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"pascal.eberhard@se.com" <pascal.eberhard@se.com>,
"wahid.essid@se.com" <wahid.essid@se.com>
Subject: RE: [PATCH 0/3] sbom-cve-check: Update to version 1.3.3 and update CVE databases
Date: Wed, 5 Aug 2026 10:00:13 +0000 [thread overview]
Message-ID: <AS8PR10MB5073728DC68610A9254ED210FDD32@AS8PR10MB5073.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20260803-update-sbom-cve-check-1-3-3-v1-0-c0e5e198030e@bootlin.com>
I have noticed that right after merging this commit, 9 historical CVEs were newly reported in Yocto master metrics.
(which is higher number than what was resolved by this update, which was 3 or 4).
All are caused by "no-version-ranges":
gnutls CVE-2023-0361
glibc CVE-2011-0536
glibc CVE-2025-0577 (was "Fixed from version >2.40-17.fc41")
ovmf CVE-2017-5731
ovmf CVE-2019-14584
pulseaudio CVE-2020-15710
pulseaudio CVE-2020-16123
openssl CVE-2015-3216
ppp CVE-2020-15704 (was "Fixed from version 2.4.7-2\\+2ubuntu1.3")
I guess the two above which I extra commented are something which in theory could be looked at and handled in code?
The rest are unfortunately all data source issues.
I'll send annotations for all anyway...
Peter
> -----Original Message-----
> From: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
> Sent: Monday, August 3, 2026 11:26 AM
> To: openembedded-core@lists.openembedded.org
> Cc: ross.burton@arm.com; Marko, Peter (FT D EU SK BFS1)
> <Peter.Marko@siemens.com>; olivier.benjamin@bootlin.com; mathieu.dubois-
> briand@bootlin.com; thomas.petazzoni@bootlin.com; pascal.eberhard@se.com;
> wahid.essid@se.com; Benjamin Robin (Schneider Electric)
> <benjamin.robin@bootlin.com>
> Subject: [PATCH 0/3] sbom-cve-check: Update to version 1.3.3 and update CVE
> databases
>
> This series update sbom-cve-check to the latest release.
> This release of sbom-cve-check addresses various fixes and improvements
> as detailed in the changelog [1]
>
> This series also updates the sbom-cve-check-update-* recipes to fetch
> a more recent version of the CVE databases.
>
> [1] https://github.com/bootlin/sbom-cve-check/blob/main/CHANGELOG.md#v133
>
> Signed-off-by: Benjamin Robin (Schneider Electric)
> <benjamin.robin@bootlin.com>
> ---
> Benjamin Robin (Schneider Electric) (3):
> python3-sbom-cve-check: update to version 1.3.3
> sbom-cve-check-update-cvelist-native: update to version 2026-08-03
> sbom-cve-check-update-nvd-native: update to version 2026.08.03-000011
>
> ...{python3-sbom-cve-check_1.3.2.bb => python3-sbom-cve-check_1.3.3.bb} | 2
> +-
> ...2026-07-23.bb => sbom-cve-check-update-cvelist-native_2026-08-03.bb} | 2 +-
> ...-000007.bb => sbom-cve-check-update-nvd-native_2026.08.03-000011.bb} | 2
> +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
> ---
> base-commit: 6a91494f29a1f9da28280bc93771714c4545da46
> change-id: 20260803-update-sbom-cve-check-1-3-3-d9347fb56ae6
>
> Best regards,
> --
> Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
next prev parent reply other threads:[~2026-08-05 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 9:25 [PATCH 0/3] sbom-cve-check: Update to version 1.3.3 and update CVE databases Benjamin Robin (Schneider Electric)
2026-08-03 9:25 ` [PATCH 1/3] python3-sbom-cve-check: update to version 1.3.3 Benjamin Robin (Schneider Electric)
2026-08-03 9:25 ` [PATCH 2/3] sbom-cve-check-update-cvelist-native: update to version 2026-08-03 Benjamin Robin (Schneider Electric)
2026-08-03 9:25 ` [PATCH 3/3] sbom-cve-check-update-nvd-native: update to version 2026.08.03-000011 Benjamin Robin (Schneider Electric)
2026-08-05 10:00 ` Marko, Peter [this message]
2026-08-05 11:53 ` [PATCH 0/3] sbom-cve-check: Update to version 1.3.3 and update CVE databases 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=AS8PR10MB5073728DC68610A9254ED210FDD32@AS8PR10MB5073.EURPRD10.PROD.OUTLOOK.COM \
--to=peter.marko@siemens.com \
--cc=benjamin.robin@bootlin.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=olivier.benjamin@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pascal.eberhard@se.com \
--cc=ross.burton@arm.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wahid.essid@se.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