xserver-org: update CVE_PRODUCT
PATCH 1/2 xserver-org: update CVE_PRODUCT
From: Peter Marko <[email protected]>
In cvelistV5, CVE-2024-21886 uses CPE xorg:xserver ([1]). Detected because this CVE is shown for xwayland recipe.
--- meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-graphics/xorg-xserver/xserver-xorg.inc +1 -1
@@ -19,7 +19,7 @@ SRC_URI = "${XORG_MIRROR}/individual/xserver/${XORG_PN}-${PV}.tar.xz" UPSTREAM_CHECK_REGEX = "xorg-server-(?P<pver>\d+(\.(?!99)\d+)+)\.tar" -CVE_PRODUCT = "xorg-server x_server" +CVE_PRODUCT = "xorg-server x_server xorg:xserver" CVE_STATUS[CVE-2011-4613] = "not-applicable-platform: This is specific to Debian's xserver-wrapper.c" CVE_STATUS[CVE-2020-25697] = "upstream-wontfix: \
PATCH 2/2 xwayland: set status for CVE-2024-21886
From: Peter Marko <[email protected]>
Reference [1]:
Introduced in: xorg-server-1.13.0 (2012)
Fixed in: xorg-server-21.1.11 and xwayland-23.2.4
Note that the status should be "fixed-version", however that does not seem to work correctly with the new sbom-cve-check.
[1] https://lists.x.org/archives/xorg/2024-January/061525.html
--- meta/recipes-graphics/xwayland/xwayland_24.1.9.bb | 2 ++ 1 file changed, 2 insertions(+)
meta/recipes-graphics/xwayland/xwayland_24.1.9.bb +2 -0
@@ -14,6 +14,8 @@ SRC_URI[sha256sum] = "f297af27a84508db9b80d1cbbcc69c3801da38eb64c72f3b5b50f58245 UPSTREAM_CHECK_REGEX = "xwayland-(?P<pver>\d+(\.(?!90\d)\d+)+)\.tar" +CVE_STATUS[CVE-2024-21886] = "version-not-in-range: fixed since xwayland-23.2.4" + inherit meson features_check pkgconfig REQUIRED_DISTRO_FEATURES = "x11 opengl"
RE: [PATCH 2/2] xwayland: set status for CVE-2024-21886
Quoted 9 lines
-----Original Message-----
From: Marko, Peter (FT D EU SK BFS1) <[email protected]>
Sent: Sunday, April 12, 2026 8:52 PM
To: [email protected]
Cc: Marko, Peter (FT D EU SK BFS1) <[email protected]>
Subject: [PATCH 2/2] xwayland: set status for CVE-2024-21886
Quoted 8 lines
From: Peter Marko <[email protected]>
Reference [1]:
Introduced in: xorg-server-1.13.0 (2012)
Fixed in: xorg-server-21.1.11 and xwayland-23.2.4Note that the status should be "fixed-version", however that does not seem to work correctly with the new sbom-cve-check.
This looks like a bug in sbom-cve-check (or vex?) code.
Any idea why certain manual CVE_STATUSes would be overridden by cvelistV5 status?
Quoted 24 lines
[1] https://lists.x.org/archives/xorg/2024-January/061525.html
Signed-off-by Peter Marko <[email protected]>--- meta/recipes-graphics/xwayland/xwayland_24.1.9.bb | 2 ++ 1 file changed, 2 insertions(+)meta/recipes- renamed from meta/recipes-graphics/xwayland/xwayland_24.1.9.bb +0
-0graphics/xwayland/xwayland_24.1.9.bb
indexdf1bb7e31b..6c10eddb8e100644meta/recipes-graphics/xwayland/xwayland_24.1.9.bb +0
-0@@ -14,6 +14,8 @@ SRC_URI[sha256sum] ="
f297af27a84508db9b80d1cbbcc69c3801da38eb64c72f3b5b50f58245
UPSTREAM_CHECK_REGEX= "xwayland-(?P<pver>\d+(\.(?!90\d)\d+)+)\.tar"+CVE_STATUS[CVE-2024-21886] = "version-not-in-range: fixed since xwayland- 23.2.4"
+
inherit mesonfeatures_checkpkgconfigREQUIRED_DISTRO_FEATURES= "x11 opengl"
Re: [PATCH 2/2] xwayland: set status for CVE-2024-21886
Hello Peter,
Quoted 11 lines · Peter
Quoted 8 lines
From: Peter Marko <[email protected]>
Reference [1]:
Introduced in: xorg-server-1.13.0 (2012)
Fixed in: xorg-server-21.1.11 and xwayland-23.2.4Note that the status should be "fixed-version", however that does not seem to work correctly with the new sbom-cve-check.
This looks like a bug in sbom-cve-check (or vex?) code.
Any idea why certain manualCVE_STATUSeswould be overridden by cvelistV5 status?
This should not be possible. With default configuration a manual annotation cannot be overwritten. sbom-cve-check directly use the annotation without any extra processing.
Quoted 8 lines
Quoted 8 lines
meta/recipes- renamed from meta/recipes-graphics/xwayland/xwayland_24.1.9.bb +0
-0graphics/xwayland/xwayland_24.1.9.bb
indexdf1bb7e31b..6c10eddb8e100644meta/recipes-graphics/xwayland/xwayland_24.1.9.bb +0
-0@@ -14,6 +14,8 @@ SRC_URI[sha256sum] ="
f297af27a84508db9b80d1cbbcc69c3801da38eb64c72f3b5b50f58245
Quoted 7 lines
Quoted 7 lines
UPSTREAM_CHECK_REGEX= "xwayland-(?P<pver>\d+(\.(?!90\d)\d+)+)\.tar"+CVE_STATUS[CVE-2024-21886] = "version-not-in-range: fixed since xwayland- 23.2.4"
+
inherit mesonfeatures_checkpkgconfigREQUIRED_DISTRO_FEATURES= "x11 opengl"
What you see is perfectly normal.
The recipe is named "xwayland", without a CVE_PRODUCT specified, so the default CPE is "cpe:2.3:*:*:xwayland:24.1.9:*:*:*:*:*:*:*"
The CVE is associated with xorg-server and with xwayland. And if you notice, in the report the CVE is linked to xorg-server and to xwayland: The CVE is referenced twice in the report. When associated with xorg-server the annotation does not work, but when associated with xwayland it works.
I guess you also need to add the CVE_STATUS in xserver-xorg recipe.
Signature · 3 lines
Benjamin Robin, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
RE: [PATCH 2/2] xwayland: set status for CVE-2024-21886
Quoted 22 lines
-----Original Message-----
From: Benjamin Robin <[email protected]>
Sent: Sunday, April 12, 2026 10:23 PM
To: Ross Burton <[email protected]>; Marko, Peter (FT D EU SK BFS1) <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 2/2] xwayland: set status for CVE-2024-21886Hello Peter,
Quoted 9 lines · Peter
Quoted 8 lines
From: Peter Marko <[email protected]>
Reference [1]:
Introduced in: xorg-server-1.13.0 (2012)
Fixed in: xorg-server-21.1.11 and xwayland-23.2.4Note that the status should be "fixed-version", however that does not seem to work correctly with the new sbom-cve-check.
Quoted 7 lines
Quoted 2 lines
This looks like a bug in sbom-cve-check (or vex?) code.
Any idea why certain manualCVE_STATUSeswould be overridden by cvelistV5status?
This should not be possible. With default configuration a manual annotation cannot be overwritten. sbom-cve-check directly use the annotation without any extra processing.
I wonder what I'm doing wrong when using this new code for the first time... When I got to the "new" CVE for ovmf, cve-metrics shows only CVE-2024-1298. In my local build, I get all the CVEs (which are se to fixed-version in the recipe).
RECIPE=ovmf; bitbake $RECIPE -c sbom_cve_check_recipe; jq -r '.package[] | select(.name == "'$RECIPE'") | .issue[]? | select(.status == "Unpatched") | .id' tmp/deploy/images/qemux86-64/$RECIPE-recipe-sbom.sbom-cve-check.yocto.json CVE-2014-4859
CVE-2014-4860
CVE-2014-8271
CVE-2019-14553
CVE-2019-14559
CVE-2019-14562
CVE-2019-14563
CVE-2019-14575
CVE-2019-14586
CVE-2019-14587
CVE-2024-1298
My local.conf is:
DISTRO = "poky"
INHERIT += "sbom-cve-check-recipe" SRCREV:pn-sbom-cve-check-update-cvelist-native = "82e18eb3051039642ed8ec0b8eb15ea27dbbf52c" include conf/distro/include/cve-extra-exclusions.inc
Peter
Quoted 38 lines
Quoted 2 lines
Review
Quoted 2 lines
(quoted diff) +0
-0b/meta/recipes-
Quoted 8 lines
Quoted 8 lines
graphics/xwayland/xwayland_24.1.9.bb
indexdf1bb7e31b..6c10eddb8e100644meta/recipes-graphics/xwayland/xwayland_24.1.9.bb +0
-0@@ -14,6 +14,8 @@ SRC_URI[sha256sum] ="
f297af27a84508db9b80d1cbbcc69c3801da38eb64c72f3b5b50f58245
UPSTREAM_CHECK_REGEX= "xwayland-(?P<pver>\d+(\.(?!90\d)\d+)+)\.tar"
Quoted 2 lines
Quoted 2 lines
+CVE_STATUS[CVE-2024-21886] = "version-not-in-range: fixed since
xwayland-
Quoted 4 lines
Quoted 4 lines
23.2.4"
+
inherit mesonfeatures_checkpkgconfig
REQUIRED_DISTRO_FEATURES= "x11 opengl"What you see is perfectly normal.
The recipe is named "xwayland", without aCVE_PRODUCTspecified, so the default CPE is "cpe:2.3:*:*:xwayland:24.1.9:*:*:*:*:*:*:*"The CVE is associated with xorg-server and with xwayland. And if you notice, in the report the CVE is linked to xorg-server and to xwayland: The CVE is referenced twice in the report. When associated with xorg-server the annotation does not work, but when associated with xwayland it works.
I guess you also need to add the
CVE_STATUSin xserver-xorg recipe.--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Re: [PATCH 2/2] xwayland: set status for CVE-2024-21886
Quoted 22 lines · Peter
Quoted 4 lines
From: Benjamin Robin <[email protected]>
This should not be possible. With default configuration a manual annotation cannot be overwritten. sbom-cve-check directly use the annotation without any extra processing.I wonder what I'm doing wrong when using this new code for the first time... When I got to the "new" CVE for ovmf, cve-metrics shows only CVE-2024-1298. In my local build, I get all the CVEs (which are se to fixed-version in the recipe).
RECIPE=ovmf; bitbake $RECIPE -c
sbom_cve_check_recipe; jq -r '.package[] |select(.name == "'$RECIPE'")| .issue[]? |select(.status == "Unpatched")| .id'tmp/deploy/images/qemux86-64/$RECIPE-recipe-sbom.sbom-cve-check.yocto.jsonCVE-2014-4859
CVE-2014-4860
CVE-2014-8271
CVE-2019-14553
CVE-2019-14559
CVE-2019-14562
CVE-2019-14563
CVE-2019-14575
CVE-2019-14586
CVE-2019-14587
CVE-2024-1298
Quoted 5 lines
My local.conf is:
DISTRO = "poky"
INHERIT += "sbom-cve-check-recipe" SRCREV:pn-sbom-cve-check-update-cvelist-native = "82e18eb3051039642ed8ec0b8eb15ea27dbbf52c" include conf/distro/include/cve-extra-exclusions.inc
I still cannot reproduce your issue.
Could you share these 2 files (by email and compressed, and maybe only to me):
- ovmf-recipe-sbom.spdx.json
- ovmf-recipe-sbom.sbom-cve-check.yocto.json
If you also have a KAS configuration file of your current setup, this will be great.
Signature · 3 lines
Benjamin Robin, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
RE: [PATCH 2/2] xwayland: set status for CVE-2024-21886
Quoted 42 lines
-----Original Message-----
From: Benjamin Robin <[email protected]>
Sent: Monday, April 13, 2026 9:05 AM
To: Ross Burton <[email protected]>; Marko, Peter (FT D EU SK BFS1) <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 2/2] xwayland: set status for CVE-2024-21886Quoted 10 lines · Peter
Quoted 4 lines
From: Benjamin Robin <[email protected]>
This should not be possible. With default configuration a manual annotation cannot be overwritten. sbom-cve-check directly use the annotation without any extra processing.I wonder what I'm doing wrong when using this new code for the first time... When I got to the "new" CVE for ovmf, cve-metrics shows only CVE-2024-1298. In my local build, I get all the CVEs (which are se to fixed-version in the recipe).
RECIPE=ovmf; bitbake $RECIPE -c
sbom_cve_check_recipe; jq -r '.package[] |
select(.name == "'$RECIPE'")| .issue[]? |select(.status == "Unpatched")| .id'tmp/deploy/images/qemux86-64/$RECIPE-recipe-sbom.sbom-cve-check.yocto.jsonQuoted 12 lines
CVE-2014-4859
CVE-2014-4860
CVE-2014-8271
CVE-2019-14553
CVE-2019-14559
CVE-2019-14562
CVE-2019-14563
CVE-2019-14575
CVE-2019-14586
CVE-2019-14587
CVE-2024-1298Quoted 4 lines
My local.conf is:
DISTRO = "poky"
INHERIT += "sbom-cve-check-recipe"
SRCREV:pn-sbom-cve-check-update-cvelist-native ="
82e18eb3051039642ed8ec0b8eb15ea27dbbf52c"Quoted 1 line
include conf/distro/include/cve-extra-exclusions.inc
Quoted 7 lines
I still cannot reproduce your issue.
Could you share these 2 files (by email and compressed, and maybe only to me):
- ovmf-recipe-sbom.spdx.json
- ovmf-recipe-sbom.sbom-cve-check.yocto.jsonIf you also have a KAS configuration file of your current setup, this will be great.
OK, now I found the missing piece (in sbom-cve-check fragment) SPDX_INCLUDE_VEX = "all" is needed to pass the fixed-version flags.
Sorry for the noise, adopting new things takes sometimes lot of attempts.
Quoted 7 lines
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com