All of lore.kernel.org
 help / color / mirror / Atom feed
* [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410
@ 2025-10-15  6:35 Ankur Tyagi
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197 Ankur Tyagi
                   ` (3 more replies)
  0 siblings, 4 replies; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-15  6:35 UTC (permalink / raw)
  To: openembedded-devel; +Cc: Ninette Adhikari, Khem Raj, Ankur Tyagi

From: Ninette Adhikari <ninette@thehoodiefirm.com>

The recipe used in the `meta-openembedded` is a different mercurial package compared to the one which has the CVE issue.
Package used in `meta-embedded`: https://www.mercurial-scm.org/
Package with CVE issue is a Jenkins plugin: https://plugins.jenkins.io/mercurial/
(This is reflected in the CPE)

Signed-off-by: Ninette Adhikari <ninette@thehoodiefirm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit bf84ac1c4c1a00c2aa92a09fbdfae128d055fe05)
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
 meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
index 2451a36be2..53fe0a28ae 100644
--- a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
+++ b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
@@ -34,3 +34,4 @@ PACKAGES =+ "${PN}-python"
 FILES:${PN} += "${PYTHON_SITEPACKAGES_DIR} ${datadir}"
 FILES:${PN}-python = "${nonarch_libdir}/${PYTHON_DIR}"
 
+CVE_STATUS[CVE-2022-43410] = "cpe-incorrect: The recipe used in the `meta-openembedded` is a different mercurial package compared to the one which has the CVE issue."


^ permalink raw reply related	[flat|nested] 12+ messages in thread

* [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197
  2025-10-15  6:35 [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
@ 2025-10-15  6:35 ` Ankur Tyagi
  2025-10-15  8:44   ` Gyorgy Sarvari
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release Ankur Tyagi
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-15  6:35 UTC (permalink / raw)
  To: openembedded-devel; +Cc: Ankur Tyagi

Details https://nvd.nist.gov/vuln/detail/CVE-2024-5197
---
 .../webm/libvpx/CVE-2024-5197.patch           | 225 ++++++++++++++++++
 .../recipes-multimedia/webm/libvpx_1.14.0.bb  |   1 +
 2 files changed, 226 insertions(+)
 create mode 100644 meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch

diff --git a/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch b/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
new file mode 100644
index 0000000000..5ab7f6d8d5
--- /dev/null
+++ b/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
@@ -0,0 +1,225 @@
+From 402e649a26196152a1703a949a71e4c8985edb8a Mon Sep 17 00:00:00 2001
+From: Wan-Teh Chang <wtc@google.com>
+Date: Wed, 10 Apr 2024 17:01:10 -0700
+Subject: [PATCH] CVE-2024-5197
+
+[1] Fix integer overflows in calc of stride_in_bytes
+
+A port of the libaom CL
+https://aomedia-review.googlesource.com/c/aom/+/188761.
+
+Fix unsigned integer overflows in the calculation of stride_in_bytes in
+img_alloc_helper() when d_w is huge.
+
+Change the type of stride_in_bytes from unsigned int to int because it
+will be assigned to img->stride[VPX_PLANE_Y], which is of the int type.
+
+Test:
+. ../libvpx/tools/set_analyzer_env.sh integer
+../libvpx/configure --enable-debug --disable-optimizations
+make -j
+./test_libvpx --gtest_filter=VpxImageTest.VpxImgAllocHugeWidth
+
+Bug: chromium:332382766
+Change-Id: I3b39d78f61c7255e10cbf72ba2f4975425a05a82
+
+[2] Avoid integer overflows in arithmetic operations
+
+A port of the libaom CL
+https://aomedia-review.googlesource.com/c/aom/+/188823.
+
+Impose maximum values on the input parameters so that we can perform
+arithmetic operations without worrying about overflows.
+
+Also change the VpxImageTest.VpxImgAllocHugeWidth test to write to the
+first and last samples in the first row of the Y plane, so that the test
+will crash if there is unsigned integer overflow in the calculation of
+stride_in_bytes.
+
+Bug: chromium:332382766
+Change-Id: I54cec6c9e26377abaa8a991042ba277ff70afdf3
+
+[3] Fix a bug in alloc_size for high bit depths
+
+I introduced this bug in commit 2e32276:
+https://chromium-review.googlesource.com/c/webm/libvpx/+/5446333
+
+I changed the line
+
+  stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
+
+to three lines:
+
+  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
+  if (s > INT_MAX) goto fail;
+  stride_in_bytes = (int)s;
+
+But I didn't realize that `s` is used later in the calculation of
+alloc_size.
+
+As a quick fix, undo the effect of s * 2 for high bit depths after `s`
+has been assigned to stride_in_bytes.
+
+Bug: chromium:332382766
+Change-Id: I53fbf405555645ab1d7254d31aadabe4f426be8c
+
+(cherry picked from commit c5640e3300690705c336966e2a8bb346a388c829)
+(cherry picked from commit 9d7054c0cb83665a74cf6f59b6261f455e692149)
+(cherry picked from commit 61c4d556bd03b97d84e3fa49180d14bde5a62baa)
+Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
+
+CVE: CVE-2024-5197
+Upstream-Status: Backport
+[1] [https://chromium.googlesource.com/webm/libvpx/+/c5640e3300690705c336966e2a8bb346a388c829]
+[2] [https://chromium.googlesource.com/webm/libvpx/+/9d7054c0cb83665a74cf6f59b6261f455e692149]
+[3] [https://chromium.googlesource.com/webm/libvpx/+/61c4d556bd03b97d84e3fa49180d14bde5a62baa]
+---
+ vpx/src/vpx_image.c | 45 +++++++++++++++++++++++++++++++++------------
+ vpx/vpx_image.h     | 16 +++++++++++-----
+ 2 files changed, 44 insertions(+), 17 deletions(-)
+
+diff --git a/vpx/src/vpx_image.c b/vpx/src/vpx_image.c
+index f9f0dd602..838a9ea4e 100644
+--- a/vpx/src/vpx_image.c
++++ b/vpx/src/vpx_image.c
+@@ -8,6 +8,7 @@
+  *  be found in the AUTHORS file in the root of the source tree.
+  */
+ 
++#include <assert.h>
+ #include <limits.h>
+ #include <stdlib.h>
+ #include <string.h>
+@@ -21,12 +22,23 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
+                                      unsigned int buf_align,
+                                      unsigned int stride_align,
+                                      unsigned char *img_data) {
+-  unsigned int h, w, s, xcs, ycs, bps;
+-  unsigned int stride_in_bytes;
++  unsigned int h, w, xcs, ycs, bps;
++  uint64_t s;
++  int stride_in_bytes;
+   unsigned int align;
+ 
+   if (img != NULL) memset(img, 0, sizeof(vpx_image_t));
+ 
++  if (fmt == VPX_IMG_FMT_NONE) goto fail;
++
++  /* Impose maximum values on input parameters so that this function can
++   * perform arithmetic operations without worrying about overflows.
++   */
++  if (d_w > 0x08000000 || d_h > 0x08000000 || buf_align > 65536 ||
++      stride_align > 65536) {
++    goto fail;
++  }
++
+   /* Treat align==0 like align==1 */
+   if (!buf_align) buf_align = 1;
+ 
+@@ -80,9 +92,12 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
+    * and height shouldn't be adjusted. */
+   w = d_w;
+   h = d_h;
+-  s = (fmt & VPX_IMG_FMT_PLANAR) ? w : bps * w / 8;
+-  s = (s + stride_align - 1) & ~(stride_align - 1);
+-  stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
++  s = (fmt & VPX_IMG_FMT_PLANAR) ? w : (uint64_t)bps * w / 8;
++  s = (s + stride_align - 1) & ~((uint64_t)stride_align - 1);
++  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
++  if (s > INT_MAX) goto fail;
++  stride_in_bytes = (int)s;
++  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s / 2 : s;
+ 
+   /* Allocate the new image */
+   if (!img) {
+@@ -100,12 +115,16 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
+     /* Calculate storage sizes given the chroma subsampling */
+     align = (1 << xcs) - 1;
+     w = (d_w + align) & ~align;
++    assert(d_w <= w);
+     align = (1 << ycs) - 1;
+     h = (d_h + align) & ~align;
++    assert(d_h <= h);
+ 
+-    s = (fmt & VPX_IMG_FMT_PLANAR) ? w : bps * w / 8;
+-    s = (s + stride_align - 1) & ~(stride_align - 1);
+-    stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
++    s = (fmt & VPX_IMG_FMT_PLANAR) ? w : (uint64_t)bps * w / 8;
++    s = (s + stride_align - 1) & ~((uint64_t)stride_align - 1);
++    s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
++    if (s > INT_MAX) goto fail;
++    stride_in_bytes = (int)s;
+     alloc_size = (fmt & VPX_IMG_FMT_PLANAR) ? (uint64_t)h * s * bps / 8
+                                             : (uint64_t)h * s;
+ 
+@@ -170,12 +189,12 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
+       if (img->fmt & VPX_IMG_FMT_HAS_ALPHA) {
+         img->planes[VPX_PLANE_ALPHA] =
+             data + x * bytes_per_sample + y * img->stride[VPX_PLANE_ALPHA];
+-        data += img->h * img->stride[VPX_PLANE_ALPHA];
++        data += (size_t)img->h * img->stride[VPX_PLANE_ALPHA];
+       }
+ 
+       img->planes[VPX_PLANE_Y] =
+           data + x * bytes_per_sample + y * img->stride[VPX_PLANE_Y];
+-      data += img->h * img->stride[VPX_PLANE_Y];
++      data += (size_t)img->h * img->stride[VPX_PLANE_Y];
+ 
+       if (img->fmt == VPX_IMG_FMT_NV12) {
+         img->planes[VPX_PLANE_U] =
+@@ -186,7 +205,8 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
+         img->planes[VPX_PLANE_U] =
+             data + (x >> img->x_chroma_shift) * bytes_per_sample +
+             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
+-        data += (img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
++        data +=
++            (size_t)(img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
+         img->planes[VPX_PLANE_V] =
+             data + (x >> img->x_chroma_shift) * bytes_per_sample +
+             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
+@@ -194,7 +214,8 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
+         img->planes[VPX_PLANE_V] =
+             data + (x >> img->x_chroma_shift) * bytes_per_sample +
+             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
+-        data += (img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
++        data +=
++            (size_t)(img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
+         img->planes[VPX_PLANE_U] =
+             data + (x >> img->x_chroma_shift) * bytes_per_sample +
+             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
+diff --git a/vpx/vpx_image.h b/vpx/vpx_image.h
+index 1adc9b9d9..2c30a8993 100644
+--- a/vpx/vpx_image.h
++++ b/vpx/vpx_image.h
+@@ -132,10 +132,13 @@ typedef struct vpx_image_rect {
+  *                         is NULL, the storage for the descriptor will be
+  *                         allocated on the heap.
+  * \param[in]    fmt       Format for the image
+- * \param[in]    d_w       Width of the image
+- * \param[in]    d_h       Height of the image
++ * \param[in]    d_w       Width of the image. Must not exceed 0x08000000
++ *                         (2^27).
++ * \param[in]    d_h       Height of the image. Must not exceed 0x08000000
++ *                         (2^27).
+  * \param[in]    align     Alignment, in bytes, of the image buffer and
+- *                         each row in the image(stride).
++ *                         each row in the image (stride). Must not exceed
++ *                         65536.
+  *
+  * \return Returns a pointer to the initialized image descriptor. If the img
+  *         parameter is non-null, the value of the img parameter will be
+@@ -155,9 +158,12 @@ vpx_image_t *vpx_img_alloc(vpx_image_t *img, vpx_img_fmt_t fmt,
+  *                             parameter is NULL, the storage for the descriptor
+  *                             will be allocated on the heap.
+  * \param[in]    fmt           Format for the image
+- * \param[in]    d_w           Width of the image
+- * \param[in]    d_h           Height of the image
++ * \param[in]    d_w           Width of the image. Must not exceed 0x08000000
++ *                             (2^27).
++ * \param[in]    d_h           Height of the image. Must not exceed 0x08000000
++ *                             (2^27).
+  * \param[in]    stride_align  Alignment, in bytes, of each row in the image.
++ *                             Must not exceed 65536.
+  * \param[in]    img_data      Storage to use for the image
+  *
+  * \return Returns a pointer to the initialized image descriptor. If the img
diff --git a/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb b/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
index b4d49842ea..13e342d420 100644
--- a/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
+++ b/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=d5b04755015be901744a78cc30d390d4"
 SRCREV = "602e2e8979d111b02c959470da5322797dd96a19"
 SRC_URI += "git://chromium.googlesource.com/webm/libvpx;protocol=https;branch=main \
            file://libvpx-configure-support-blank-prefix.patch \
+           file://CVE-2024-5197.patch \
            "
 
 S = "${WORKDIR}/git"


^ permalink raw reply related	[flat|nested] 12+ messages in thread

* [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release
  2025-10-15  6:35 [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197 Ankur Tyagi
@ 2025-10-15  6:35 ` Ankur Tyagi
  2025-10-30  6:30   ` Mittal, Anuj
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644 Ankur Tyagi
  2025-10-30  6:38 ` [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Mittal, Anuj
  3 siblings, 1 reply; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-15  6:35 UTC (permalink / raw)
  To: openembedded-devel; +Cc: Ankur Tyagi

This release fixes CVE-2024-42458
https://github.com/any1/neatvnc/compare/v0.8.0...v0.8.1

Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
 .../neatvnc/{neatvnc_0.8.0.bb => neatvnc_0.8.1.bb}          | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
 rename meta-oe/recipes-graphics/neatvnc/{neatvnc_0.8.0.bb => neatvnc_0.8.1.bb} (81%)

diff --git a/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb b/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
similarity index 81%
rename from meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
rename to meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
index c9c4a6c27a..572134b47c 100644
--- a/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
+++ b/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
@@ -4,9 +4,9 @@ HOMEPAGE = "https://github.com/any1/neatvnc"
 LICENSE = "ISC"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94fc374e7174f41e3afe0f027ee59ff7"
 
-SRC_URI = "git://github.com/any1/neatvnc;branch=master;protocol=https"
+SRC_URI = "git://github.com/any1/neatvnc;branch=v0.8;protocol=https"
 
-SRCREV = "46432ce8cade0b54a38d4bb42eb07f96c8ff49fd"
+SRCREV = "07081567ab21a2b099ceb41ae8cab872a31cbb9a"
 
 S = "${WORKDIR}/git"
 
@@ -36,3 +36,5 @@ do_install:append () {
 }
 
 BBCLASSEXTEND = "native"
+
+CVE_STATUS[CVE-2024-42458] = "fixed-version: No action required. The current version (0.8.1) is not affected by the CVE."


^ permalink raw reply related	[flat|nested] 12+ messages in thread

* [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644
  2025-10-15  6:35 [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197 Ankur Tyagi
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release Ankur Tyagi
@ 2025-10-15  6:35 ` Ankur Tyagi
  2025-10-30  6:27   ` Mittal, Anuj
  2025-10-30  6:38 ` [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Mittal, Anuj
  3 siblings, 1 reply; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-15  6:35 UTC (permalink / raw)
  To: openembedded-devel; +Cc: Ankur Tyagi

Details https://nvd.nist.gov/vuln/detail/CVE-2025-53644

CVE was fixed by [1] but the change [2] which introduced CVE was not present this version (4.9.0).

$ git tag --no-contains 40faced6 | grep 4.9.0
4.9.0

[1] https://github.com/opencv/opencv/commit/a39db41390de546d18962ee1278bd6dbb715f466
[2] https://github.com/opencv/opencv/commit/40faced6c18baa6fbc7c1fbd409d59d6ddecc74f#diff-ae9fbe252ce7879e83e7ae22e594d50b5a8d2ea8dfb4cc8e02e896902a1a8f10R2872

Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
---
 meta-oe/recipes-support/opencv/opencv_4.9.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-oe/recipes-support/opencv/opencv_4.9.0.bb b/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
index cf836d3ecf..e4910553bf 100644
--- a/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
+++ b/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
@@ -208,3 +208,5 @@ do_install:append() {
         rm -rf ${D}${bindir}/setup_vars_opencv4.sh
     fi
 }
+
+CVE_STATUS[CVE-2025-53644] = "cpe-incorrect: This version (4.9.0) doesn't contain the change which introduced CVE."


^ permalink raw reply related	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197 Ankur Tyagi
@ 2025-10-15  8:44   ` Gyorgy Sarvari
  2025-10-15  9:23     ` Ankur Tyagi
  0 siblings, 1 reply; 12+ messages in thread
From: Gyorgy Sarvari @ 2025-10-15  8:44 UTC (permalink / raw)
  To: ankur.tyagi85, openembedded-devel

It looks that v1.14.1 contains this fix also - can the relevant commit
be cherry-picked from master? (Maybe not because it's a big change,
haven't checked, this is just a question...)

On 10/15/25 08:35, Ankur Tyagi via lists.openembedded.org wrote:
> Details https://nvd.nist.gov/vuln/detail/CVE-2024-5197
> ---
>  .../webm/libvpx/CVE-2024-5197.patch           | 225 ++++++++++++++++++
>  .../recipes-multimedia/webm/libvpx_1.14.0.bb  |   1 +
>  2 files changed, 226 insertions(+)
>  create mode 100644 meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
>
> diff --git a/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch b/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
> new file mode 100644
> index 0000000000..5ab7f6d8d5
> --- /dev/null
> +++ b/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
> @@ -0,0 +1,225 @@
> +From 402e649a26196152a1703a949a71e4c8985edb8a Mon Sep 17 00:00:00 2001
> +From: Wan-Teh Chang <wtc@google.com>
> +Date: Wed, 10 Apr 2024 17:01:10 -0700
> +Subject: [PATCH] CVE-2024-5197
> +
> +[1] Fix integer overflows in calc of stride_in_bytes
> +
> +A port of the libaom CL
> +https://aomedia-review.googlesource.com/c/aom/+/188761.
> +
> +Fix unsigned integer overflows in the calculation of stride_in_bytes in
> +img_alloc_helper() when d_w is huge.
> +
> +Change the type of stride_in_bytes from unsigned int to int because it
> +will be assigned to img->stride[VPX_PLANE_Y], which is of the int type.
> +
> +Test:
> +. ../libvpx/tools/set_analyzer_env.sh integer
> +../libvpx/configure --enable-debug --disable-optimizations
> +make -j
> +./test_libvpx --gtest_filter=VpxImageTest.VpxImgAllocHugeWidth
> +
> +Bug: chromium:332382766
> +Change-Id: I3b39d78f61c7255e10cbf72ba2f4975425a05a82
> +
> +[2] Avoid integer overflows in arithmetic operations
> +
> +A port of the libaom CL
> +https://aomedia-review.googlesource.com/c/aom/+/188823.
> +
> +Impose maximum values on the input parameters so that we can perform
> +arithmetic operations without worrying about overflows.
> +
> +Also change the VpxImageTest.VpxImgAllocHugeWidth test to write to the
> +first and last samples in the first row of the Y plane, so that the test
> +will crash if there is unsigned integer overflow in the calculation of
> +stride_in_bytes.
> +
> +Bug: chromium:332382766
> +Change-Id: I54cec6c9e26377abaa8a991042ba277ff70afdf3
> +
> +[3] Fix a bug in alloc_size for high bit depths
> +
> +I introduced this bug in commit 2e32276:
> +https://chromium-review.googlesource.com/c/webm/libvpx/+/5446333
> +
> +I changed the line
> +
> +  stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> +
> +to three lines:
> +
> +  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> +  if (s > INT_MAX) goto fail;
> +  stride_in_bytes = (int)s;
> +
> +But I didn't realize that `s` is used later in the calculation of
> +alloc_size.
> +
> +As a quick fix, undo the effect of s * 2 for high bit depths after `s`
> +has been assigned to stride_in_bytes.
> +
> +Bug: chromium:332382766
> +Change-Id: I53fbf405555645ab1d7254d31aadabe4f426be8c
> +
> +(cherry picked from commit c5640e3300690705c336966e2a8bb346a388c829)
> +(cherry picked from commit 9d7054c0cb83665a74cf6f59b6261f455e692149)
> +(cherry picked from commit 61c4d556bd03b97d84e3fa49180d14bde5a62baa)
> +Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> +
> +CVE: CVE-2024-5197
> +Upstream-Status: Backport
> +[1] [https://chromium.googlesource.com/webm/libvpx/+/c5640e3300690705c336966e2a8bb346a388c829]
> +[2] [https://chromium.googlesource.com/webm/libvpx/+/9d7054c0cb83665a74cf6f59b6261f455e692149]
> +[3] [https://chromium.googlesource.com/webm/libvpx/+/61c4d556bd03b97d84e3fa49180d14bde5a62baa]
> +---
> + vpx/src/vpx_image.c | 45 +++++++++++++++++++++++++++++++++------------
> + vpx/vpx_image.h     | 16 +++++++++++-----
> + 2 files changed, 44 insertions(+), 17 deletions(-)
> +
> +diff --git a/vpx/src/vpx_image.c b/vpx/src/vpx_image.c
> +index f9f0dd602..838a9ea4e 100644
> +--- a/vpx/src/vpx_image.c
> ++++ b/vpx/src/vpx_image.c
> +@@ -8,6 +8,7 @@
> +  *  be found in the AUTHORS file in the root of the source tree.
> +  */
> + 
> ++#include <assert.h>
> + #include <limits.h>
> + #include <stdlib.h>
> + #include <string.h>
> +@@ -21,12 +22,23 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
> +                                      unsigned int buf_align,
> +                                      unsigned int stride_align,
> +                                      unsigned char *img_data) {
> +-  unsigned int h, w, s, xcs, ycs, bps;
> +-  unsigned int stride_in_bytes;
> ++  unsigned int h, w, xcs, ycs, bps;
> ++  uint64_t s;
> ++  int stride_in_bytes;
> +   unsigned int align;
> + 
> +   if (img != NULL) memset(img, 0, sizeof(vpx_image_t));
> + 
> ++  if (fmt == VPX_IMG_FMT_NONE) goto fail;
> ++
> ++  /* Impose maximum values on input parameters so that this function can
> ++   * perform arithmetic operations without worrying about overflows.
> ++   */
> ++  if (d_w > 0x08000000 || d_h > 0x08000000 || buf_align > 65536 ||
> ++      stride_align > 65536) {
> ++    goto fail;
> ++  }
> ++
> +   /* Treat align==0 like align==1 */
> +   if (!buf_align) buf_align = 1;
> + 
> +@@ -80,9 +92,12 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
> +    * and height shouldn't be adjusted. */
> +   w = d_w;
> +   h = d_h;
> +-  s = (fmt & VPX_IMG_FMT_PLANAR) ? w : bps * w / 8;
> +-  s = (s + stride_align - 1) & ~(stride_align - 1);
> +-  stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> ++  s = (fmt & VPX_IMG_FMT_PLANAR) ? w : (uint64_t)bps * w / 8;
> ++  s = (s + stride_align - 1) & ~((uint64_t)stride_align - 1);
> ++  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> ++  if (s > INT_MAX) goto fail;
> ++  stride_in_bytes = (int)s;
> ++  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s / 2 : s;
> + 
> +   /* Allocate the new image */
> +   if (!img) {
> +@@ -100,12 +115,16 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
> +     /* Calculate storage sizes given the chroma subsampling */
> +     align = (1 << xcs) - 1;
> +     w = (d_w + align) & ~align;
> ++    assert(d_w <= w);
> +     align = (1 << ycs) - 1;
> +     h = (d_h + align) & ~align;
> ++    assert(d_h <= h);
> + 
> +-    s = (fmt & VPX_IMG_FMT_PLANAR) ? w : bps * w / 8;
> +-    s = (s + stride_align - 1) & ~(stride_align - 1);
> +-    stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> ++    s = (fmt & VPX_IMG_FMT_PLANAR) ? w : (uint64_t)bps * w / 8;
> ++    s = (s + stride_align - 1) & ~((uint64_t)stride_align - 1);
> ++    s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> ++    if (s > INT_MAX) goto fail;
> ++    stride_in_bytes = (int)s;
> +     alloc_size = (fmt & VPX_IMG_FMT_PLANAR) ? (uint64_t)h * s * bps / 8
> +                                             : (uint64_t)h * s;
> + 
> +@@ -170,12 +189,12 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
> +       if (img->fmt & VPX_IMG_FMT_HAS_ALPHA) {
> +         img->planes[VPX_PLANE_ALPHA] =
> +             data + x * bytes_per_sample + y * img->stride[VPX_PLANE_ALPHA];
> +-        data += img->h * img->stride[VPX_PLANE_ALPHA];
> ++        data += (size_t)img->h * img->stride[VPX_PLANE_ALPHA];
> +       }
> + 
> +       img->planes[VPX_PLANE_Y] =
> +           data + x * bytes_per_sample + y * img->stride[VPX_PLANE_Y];
> +-      data += img->h * img->stride[VPX_PLANE_Y];
> ++      data += (size_t)img->h * img->stride[VPX_PLANE_Y];
> + 
> +       if (img->fmt == VPX_IMG_FMT_NV12) {
> +         img->planes[VPX_PLANE_U] =
> +@@ -186,7 +205,8 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
> +         img->planes[VPX_PLANE_U] =
> +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> +-        data += (img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> ++        data +=
> ++            (size_t)(img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> +         img->planes[VPX_PLANE_V] =
> +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> +@@ -194,7 +214,8 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
> +         img->planes[VPX_PLANE_V] =
> +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> +-        data += (img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> ++        data +=
> ++            (size_t)(img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> +         img->planes[VPX_PLANE_U] =
> +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> +diff --git a/vpx/vpx_image.h b/vpx/vpx_image.h
> +index 1adc9b9d9..2c30a8993 100644
> +--- a/vpx/vpx_image.h
> ++++ b/vpx/vpx_image.h
> +@@ -132,10 +132,13 @@ typedef struct vpx_image_rect {
> +  *                         is NULL, the storage for the descriptor will be
> +  *                         allocated on the heap.
> +  * \param[in]    fmt       Format for the image
> +- * \param[in]    d_w       Width of the image
> +- * \param[in]    d_h       Height of the image
> ++ * \param[in]    d_w       Width of the image. Must not exceed 0x08000000
> ++ *                         (2^27).
> ++ * \param[in]    d_h       Height of the image. Must not exceed 0x08000000
> ++ *                         (2^27).
> +  * \param[in]    align     Alignment, in bytes, of the image buffer and
> +- *                         each row in the image(stride).
> ++ *                         each row in the image (stride). Must not exceed
> ++ *                         65536.
> +  *
> +  * \return Returns a pointer to the initialized image descriptor. If the img
> +  *         parameter is non-null, the value of the img parameter will be
> +@@ -155,9 +158,12 @@ vpx_image_t *vpx_img_alloc(vpx_image_t *img, vpx_img_fmt_t fmt,
> +  *                             parameter is NULL, the storage for the descriptor
> +  *                             will be allocated on the heap.
> +  * \param[in]    fmt           Format for the image
> +- * \param[in]    d_w           Width of the image
> +- * \param[in]    d_h           Height of the image
> ++ * \param[in]    d_w           Width of the image. Must not exceed 0x08000000
> ++ *                             (2^27).
> ++ * \param[in]    d_h           Height of the image. Must not exceed 0x08000000
> ++ *                             (2^27).
> +  * \param[in]    stride_align  Alignment, in bytes, of each row in the image.
> ++ *                             Must not exceed 65536.
> +  * \param[in]    img_data      Storage to use for the image
> +  *
> +  * \return Returns a pointer to the initialized image descriptor. If the img
> diff --git a/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb b/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
> index b4d49842ea..13e342d420 100644
> --- a/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
> +++ b/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
> @@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=d5b04755015be901744a78cc30d390d4"
>  SRCREV = "602e2e8979d111b02c959470da5322797dd96a19"
>  SRC_URI += "git://chromium.googlesource.com/webm/libvpx;protocol=https;branch=main \
>             file://libvpx-configure-support-blank-prefix.patch \
> +           file://CVE-2024-5197.patch \
>             "
>  
>  S = "${WORKDIR}/git"
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#120691): https://lists.openembedded.org/g/openembedded-devel/message/120691
> Mute This Topic: https://lists.openembedded.org/mt/115766812/6084445
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197
  2025-10-15  8:44   ` Gyorgy Sarvari
@ 2025-10-15  9:23     ` Ankur Tyagi
  0 siblings, 0 replies; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-15  9:23 UTC (permalink / raw)
  To: Gyorgy Sarvari; +Cc: openembedded-devel

On Wed, Oct 15, 2025 at 9:44 PM Gyorgy Sarvari <skandigraun@gmail.com> wrote:
>
> It looks that v1.14.1 contains this fix also - can the relevant commit
> be cherry-picked from master? (Maybe not because it's a big change,
> haven't checked, this is just a question...)
>
Yeah, the patch is big but the CVE fix is actually three commits which
I cherry-picked from v1.14.1 and squashed in one patch.
It made the patch big but I thought it was better than keeping three
separate patches for a single CVE.
I included all three commit details in the patch description along
with bug ID to avoid any loss of information.

But open to other ideas if it simplifies the situation.

> On 10/15/25 08:35, Ankur Tyagi via lists.openembedded.org wrote:
> > Details https://nvd.nist.gov/vuln/detail/CVE-2024-5197
> > ---
> >  .../webm/libvpx/CVE-2024-5197.patch           | 225 ++++++++++++++++++
> >  .../recipes-multimedia/webm/libvpx_1.14.0.bb  |   1 +
> >  2 files changed, 226 insertions(+)
> >  create mode 100644 meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
> >
> > diff --git a/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch b/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
> > new file mode 100644
> > index 0000000000..5ab7f6d8d5
> > --- /dev/null
> > +++ b/meta-oe/recipes-multimedia/webm/libvpx/CVE-2024-5197.patch
> > @@ -0,0 +1,225 @@
> > +From 402e649a26196152a1703a949a71e4c8985edb8a Mon Sep 17 00:00:00 2001
> > +From: Wan-Teh Chang <wtc@google.com>
> > +Date: Wed, 10 Apr 2024 17:01:10 -0700
> > +Subject: [PATCH] CVE-2024-5197
> > +
> > +[1] Fix integer overflows in calc of stride_in_bytes
> > +
> > +A port of the libaom CL
> > +https://aomedia-review.googlesource.com/c/aom/+/188761.
> > +
> > +Fix unsigned integer overflows in the calculation of stride_in_bytes in
> > +img_alloc_helper() when d_w is huge.
> > +
> > +Change the type of stride_in_bytes from unsigned int to int because it
> > +will be assigned to img->stride[VPX_PLANE_Y], which is of the int type.
> > +
> > +Test:
> > +. ../libvpx/tools/set_analyzer_env.sh integer
> > +../libvpx/configure --enable-debug --disable-optimizations
> > +make -j
> > +./test_libvpx --gtest_filter=VpxImageTest.VpxImgAllocHugeWidth
> > +
> > +Bug: chromium:332382766
> > +Change-Id: I3b39d78f61c7255e10cbf72ba2f4975425a05a82
> > +
> > +[2] Avoid integer overflows in arithmetic operations
> > +
> > +A port of the libaom CL
> > +https://aomedia-review.googlesource.com/c/aom/+/188823.
> > +
> > +Impose maximum values on the input parameters so that we can perform
> > +arithmetic operations without worrying about overflows.
> > +
> > +Also change the VpxImageTest.VpxImgAllocHugeWidth test to write to the
> > +first and last samples in the first row of the Y plane, so that the test
> > +will crash if there is unsigned integer overflow in the calculation of
> > +stride_in_bytes.
> > +
> > +Bug: chromium:332382766
> > +Change-Id: I54cec6c9e26377abaa8a991042ba277ff70afdf3
> > +
> > +[3] Fix a bug in alloc_size for high bit depths
> > +
> > +I introduced this bug in commit 2e32276:
> > +https://chromium-review.googlesource.com/c/webm/libvpx/+/5446333
> > +
> > +I changed the line
> > +
> > +  stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> > +
> > +to three lines:
> > +
> > +  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> > +  if (s > INT_MAX) goto fail;
> > +  stride_in_bytes = (int)s;
> > +
> > +But I didn't realize that `s` is used later in the calculation of
> > +alloc_size.
> > +
> > +As a quick fix, undo the effect of s * 2 for high bit depths after `s`
> > +has been assigned to stride_in_bytes.
> > +
> > +Bug: chromium:332382766
> > +Change-Id: I53fbf405555645ab1d7254d31aadabe4f426be8c
> > +
> > +(cherry picked from commit c5640e3300690705c336966e2a8bb346a388c829)
> > +(cherry picked from commit 9d7054c0cb83665a74cf6f59b6261f455e692149)
> > +(cherry picked from commit 61c4d556bd03b97d84e3fa49180d14bde5a62baa)
> > +Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> > +
> > +CVE: CVE-2024-5197
> > +Upstream-Status: Backport
> > +[1] [https://chromium.googlesource.com/webm/libvpx/+/c5640e3300690705c336966e2a8bb346a388c829]
> > +[2] [https://chromium.googlesource.com/webm/libvpx/+/9d7054c0cb83665a74cf6f59b6261f455e692149]
> > +[3] [https://chromium.googlesource.com/webm/libvpx/+/61c4d556bd03b97d84e3fa49180d14bde5a62baa]
> > +---
> > + vpx/src/vpx_image.c | 45 +++++++++++++++++++++++++++++++++------------
> > + vpx/vpx_image.h     | 16 +++++++++++-----
> > + 2 files changed, 44 insertions(+), 17 deletions(-)
> > +
> > +diff --git a/vpx/src/vpx_image.c b/vpx/src/vpx_image.c
> > +index f9f0dd602..838a9ea4e 100644
> > +--- a/vpx/src/vpx_image.c
> > ++++ b/vpx/src/vpx_image.c
> > +@@ -8,6 +8,7 @@
> > +  *  be found in the AUTHORS file in the root of the source tree.
> > +  */
> > +
> > ++#include <assert.h>
> > + #include <limits.h>
> > + #include <stdlib.h>
> > + #include <string.h>
> > +@@ -21,12 +22,23 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
> > +                                      unsigned int buf_align,
> > +                                      unsigned int stride_align,
> > +                                      unsigned char *img_data) {
> > +-  unsigned int h, w, s, xcs, ycs, bps;
> > +-  unsigned int stride_in_bytes;
> > ++  unsigned int h, w, xcs, ycs, bps;
> > ++  uint64_t s;
> > ++  int stride_in_bytes;
> > +   unsigned int align;
> > +
> > +   if (img != NULL) memset(img, 0, sizeof(vpx_image_t));
> > +
> > ++  if (fmt == VPX_IMG_FMT_NONE) goto fail;
> > ++
> > ++  /* Impose maximum values on input parameters so that this function can
> > ++   * perform arithmetic operations without worrying about overflows.
> > ++   */
> > ++  if (d_w > 0x08000000 || d_h > 0x08000000 || buf_align > 65536 ||
> > ++      stride_align > 65536) {
> > ++    goto fail;
> > ++  }
> > ++
> > +   /* Treat align==0 like align==1 */
> > +   if (!buf_align) buf_align = 1;
> > +
> > +@@ -80,9 +92,12 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
> > +    * and height shouldn't be adjusted. */
> > +   w = d_w;
> > +   h = d_h;
> > +-  s = (fmt & VPX_IMG_FMT_PLANAR) ? w : bps * w / 8;
> > +-  s = (s + stride_align - 1) & ~(stride_align - 1);
> > +-  stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> > ++  s = (fmt & VPX_IMG_FMT_PLANAR) ? w : (uint64_t)bps * w / 8;
> > ++  s = (s + stride_align - 1) & ~((uint64_t)stride_align - 1);
> > ++  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> > ++  if (s > INT_MAX) goto fail;
> > ++  stride_in_bytes = (int)s;
> > ++  s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s / 2 : s;
> > +
> > +   /* Allocate the new image */
> > +   if (!img) {
> > +@@ -100,12 +115,16 @@ static vpx_image_t *img_alloc_helper(vpx_image_t *img, vpx_img_fmt_t fmt,
> > +     /* Calculate storage sizes given the chroma subsampling */
> > +     align = (1 << xcs) - 1;
> > +     w = (d_w + align) & ~align;
> > ++    assert(d_w <= w);
> > +     align = (1 << ycs) - 1;
> > +     h = (d_h + align) & ~align;
> > ++    assert(d_h <= h);
> > +
> > +-    s = (fmt & VPX_IMG_FMT_PLANAR) ? w : bps * w / 8;
> > +-    s = (s + stride_align - 1) & ~(stride_align - 1);
> > +-    stride_in_bytes = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> > ++    s = (fmt & VPX_IMG_FMT_PLANAR) ? w : (uint64_t)bps * w / 8;
> > ++    s = (s + stride_align - 1) & ~((uint64_t)stride_align - 1);
> > ++    s = (fmt & VPX_IMG_FMT_HIGHBITDEPTH) ? s * 2 : s;
> > ++    if (s > INT_MAX) goto fail;
> > ++    stride_in_bytes = (int)s;
> > +     alloc_size = (fmt & VPX_IMG_FMT_PLANAR) ? (uint64_t)h * s * bps / 8
> > +                                             : (uint64_t)h * s;
> > +
> > +@@ -170,12 +189,12 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
> > +       if (img->fmt & VPX_IMG_FMT_HAS_ALPHA) {
> > +         img->planes[VPX_PLANE_ALPHA] =
> > +             data + x * bytes_per_sample + y * img->stride[VPX_PLANE_ALPHA];
> > +-        data += img->h * img->stride[VPX_PLANE_ALPHA];
> > ++        data += (size_t)img->h * img->stride[VPX_PLANE_ALPHA];
> > +       }
> > +
> > +       img->planes[VPX_PLANE_Y] =
> > +           data + x * bytes_per_sample + y * img->stride[VPX_PLANE_Y];
> > +-      data += img->h * img->stride[VPX_PLANE_Y];
> > ++      data += (size_t)img->h * img->stride[VPX_PLANE_Y];
> > +
> > +       if (img->fmt == VPX_IMG_FMT_NV12) {
> > +         img->planes[VPX_PLANE_U] =
> > +@@ -186,7 +205,8 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
> > +         img->planes[VPX_PLANE_U] =
> > +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> > +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> > +-        data += (img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> > ++        data +=
> > ++            (size_t)(img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> > +         img->planes[VPX_PLANE_V] =
> > +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> > +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> > +@@ -194,7 +214,8 @@ int vpx_img_set_rect(vpx_image_t *img, unsigned int x, unsigned int y,
> > +         img->planes[VPX_PLANE_V] =
> > +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> > +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> > +-        data += (img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> > ++        data +=
> > ++            (size_t)(img->h >> img->y_chroma_shift) * img->stride[VPX_PLANE_V];
> > +         img->planes[VPX_PLANE_U] =
> > +             data + (x >> img->x_chroma_shift) * bytes_per_sample +
> > +             (y >> img->y_chroma_shift) * img->stride[VPX_PLANE_U];
> > +diff --git a/vpx/vpx_image.h b/vpx/vpx_image.h
> > +index 1adc9b9d9..2c30a8993 100644
> > +--- a/vpx/vpx_image.h
> > ++++ b/vpx/vpx_image.h
> > +@@ -132,10 +132,13 @@ typedef struct vpx_image_rect {
> > +  *                         is NULL, the storage for the descriptor will be
> > +  *                         allocated on the heap.
> > +  * \param[in]    fmt       Format for the image
> > +- * \param[in]    d_w       Width of the image
> > +- * \param[in]    d_h       Height of the image
> > ++ * \param[in]    d_w       Width of the image. Must not exceed 0x08000000
> > ++ *                         (2^27).
> > ++ * \param[in]    d_h       Height of the image. Must not exceed 0x08000000
> > ++ *                         (2^27).
> > +  * \param[in]    align     Alignment, in bytes, of the image buffer and
> > +- *                         each row in the image(stride).
> > ++ *                         each row in the image (stride). Must not exceed
> > ++ *                         65536.
> > +  *
> > +  * \return Returns a pointer to the initialized image descriptor. If the img
> > +  *         parameter is non-null, the value of the img parameter will be
> > +@@ -155,9 +158,12 @@ vpx_image_t *vpx_img_alloc(vpx_image_t *img, vpx_img_fmt_t fmt,
> > +  *                             parameter is NULL, the storage for the descriptor
> > +  *                             will be allocated on the heap.
> > +  * \param[in]    fmt           Format for the image
> > +- * \param[in]    d_w           Width of the image
> > +- * \param[in]    d_h           Height of the image
> > ++ * \param[in]    d_w           Width of the image. Must not exceed 0x08000000
> > ++ *                             (2^27).
> > ++ * \param[in]    d_h           Height of the image. Must not exceed 0x08000000
> > ++ *                             (2^27).
> > +  * \param[in]    stride_align  Alignment, in bytes, of each row in the image.
> > ++ *                             Must not exceed 65536.
> > +  * \param[in]    img_data      Storage to use for the image
> > +  *
> > +  * \return Returns a pointer to the initialized image descriptor. If the img
> > diff --git a/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb b/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
> > index b4d49842ea..13e342d420 100644
> > --- a/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
> > +++ b/meta-oe/recipes-multimedia/webm/libvpx_1.14.0.bb
> > @@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=d5b04755015be901744a78cc30d390d4"
> >  SRCREV = "602e2e8979d111b02c959470da5322797dd96a19"
> >  SRC_URI += "git://chromium.googlesource.com/webm/libvpx;protocol=https;branch=main \
> >             file://libvpx-configure-support-blank-prefix.patch \
> > +           file://CVE-2024-5197.patch \
> >             "
> >
> >  S = "${WORKDIR}/git"
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#120691): https://lists.openembedded.org/g/openembedded-devel/message/120691
> > Mute This Topic: https://lists.openembedded.org/mt/115766812/6084445
> > Group Owner: openembedded-devel+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [skandigraun@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644 Ankur Tyagi
@ 2025-10-30  6:27   ` Mittal, Anuj
  2025-10-30  8:10     ` Ankur Tyagi
  0 siblings, 1 reply; 12+ messages in thread
From: Mittal, Anuj @ 2025-10-30  6:27 UTC (permalink / raw)
  To: ankur.tyagi85@gmail.com,
	openembedded-devel@lists.openembedded.org

On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
lists.openembedded.org wrote:
> Details https://nvd.nist.gov/vuln/detail/CVE-2025-53644
> 
> CVE was fixed by [1] but the change [2] which introduced CVE was not
> present this version (4.9.0).
> 
> $ git tag --no-contains 40faced6 | grep 4.9.0
> 4.9.0
> 
> [1]
> https://github.com/opencv/opencv/commit/a39db41390de546d18962ee1278bd6dbb715f466
> [2]
> https://github.com/opencv/opencv/commit/40faced6c18baa6fbc7c1fbd409d59d6ddecc74f#diff-ae9fbe252ce7879e83e7ae22e594d50b5a8d2ea8dfb4cc8e02e896902a1a8f10R2872
> 
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
>  meta-oe/recipes-support/opencv/opencv_4.9.0.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta-oe/recipes-support/opencv/opencv_4.9.0.bb b/meta-
> oe/recipes-support/opencv/opencv_4.9.0.bb
> index cf836d3ecf..e4910553bf 100644
> --- a/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
> +++ b/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
> @@ -208,3 +208,5 @@ do_install:append() {
>          rm -rf ${D}${bindir}/setup_vars_opencv4.sh
>      fi
>  }
> +
> +CVE_STATUS[CVE-2025-53644] = "cpe-incorrect: This version (4.9.0)
> doesn't contain the change which introduced CVE."

Actually it looks like CPE data was revised recently to include minimum
version as 4.10.0 so this should not be required now. Can you please
check again?

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#120693):
> https://lists.openembedded.org/g/openembedded-devel/message/120693
> Mute This Topic: https://lists.openembedded.org/mt/115766814/3616702
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-devel/unsub [
> anuj.mittal@intel.com]
> -=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release Ankur Tyagi
@ 2025-10-30  6:30   ` Mittal, Anuj
  2025-10-30  8:33     ` Ankur Tyagi
  0 siblings, 1 reply; 12+ messages in thread
From: Mittal, Anuj @ 2025-10-30  6:30 UTC (permalink / raw)
  To: ankur.tyagi85@gmail.com,
	openembedded-devel@lists.openembedded.org

On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
lists.openembedded.org wrote:
> This release fixes CVE-2024-42458
> https://github.com/any1/neatvnc/compare/v0.8.0...v0.8.1
> 
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
>  .../neatvnc/{neatvnc_0.8.0.bb => neatvnc_0.8.1.bb}          | 6
> ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
>  rename meta-oe/recipes-graphics/neatvnc/{neatvnc_0.8.0.bb =>
> neatvnc_0.8.1.bb} (81%)
> 
> diff --git a/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
> b/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
> similarity index 81%
> rename from meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
> rename to meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
> index c9c4a6c27a..572134b47c 100644
> --- a/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
> +++ b/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
> @@ -4,9 +4,9 @@ HOMEPAGE = "https://github.com/any1/neatvnc"
>  LICENSE = "ISC"
>  LIC_FILES_CHKSUM =
> "file://COPYING;md5=94fc374e7174f41e3afe0f027ee59ff7"
>  
> -SRC_URI =
> "git://github.com/any1/neatvnc;branch=master;protocol=https"
> +SRC_URI = "git://github.com/any1/neatvnc;branch=v0.8;protocol=https"
>  
> -SRCREV = "46432ce8cade0b54a38d4bb42eb07f96c8ff49fd"
> +SRCREV = "07081567ab21a2b099ceb41ae8cab872a31cbb9a"
>  
>  S = "${WORKDIR}/git"
>  
> @@ -36,3 +36,5 @@ do_install:append () {
>  }
>  
>  BBCLASSEXTEND = "native"
> +
> +CVE_STATUS[CVE-2024-42458] = "fixed-version: No action required. The
> current version (0.8.1) is not affected by the CVE."

Why is this required? The data shows versions till 0.8.1 (excluding) to
be vulnerable so this shouldn't be required? Am I misinterpreting
something?

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#120692):
> https://lists.openembedded.org/g/openembedded-devel/message/120692
> Mute This Topic: https://lists.openembedded.org/mt/115766813/3616702
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-devel/unsub [
> anuj.mittal@intel.com]
> -=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410
  2025-10-15  6:35 [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
                   ` (2 preceding siblings ...)
  2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644 Ankur Tyagi
@ 2025-10-30  6:38 ` Mittal, Anuj
  2025-10-31  0:41   ` Ankur Tyagi
  3 siblings, 1 reply; 12+ messages in thread
From: Mittal, Anuj @ 2025-10-30  6:38 UTC (permalink / raw)
  To: ankur.tyagi85@gmail.com,
	openembedded-devel@lists.openembedded.org
  Cc: ninette@thehoodiefirm.com, raj.khem@gmail.com

On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
lists.openembedded.org wrote:
> From: Ninette Adhikari <ninette@thehoodiefirm.com>
> 
> The recipe used in the `meta-openembedded` is a different mercurial
> package compared to the one which has the CVE issue.
> Package used in `meta-embedded`: https://www.mercurial-scm.org/
> Package with CVE issue is a Jenkins plugin:
> https://plugins.jenkins.io/mercurial/
> (This is reflected in the CPE)
> 
> Signed-off-by: Ninette Adhikari <ninette@thehoodiefirm.com>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> (cherry picked from commit bf84ac1c4c1a00c2aa92a09fbdfae128d055fe05)
> Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> ---
>  meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> index 2451a36be2..53fe0a28ae 100644
> --- a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> +++ b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> @@ -34,3 +34,4 @@ PACKAGES =+ "${PN}-python"
>  FILES:${PN} += "${PYTHON_SITEPACKAGES_DIR} ${datadir}"
>  FILES:${PN}-python = "${nonarch_libdir}/${PYTHON_DIR}"
>  
> +CVE_STATUS[CVE-2022-43410] = "cpe-incorrect: The recipe used in the
> `meta-openembedded` is a different mercurial package compared to the
> one which has the CVE issue."

This shouldn't be a cpe-incorrect in that case and should use
mercurial-scm as the vendor in CVE_PRODUCT.

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#120690):
> https://lists.openembedded.org/g/openembedded-devel/message/120690
> Mute This Topic: https://lists.openembedded.org/mt/115766810/3616702
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-devel/unsub [
> anuj.mittal@intel.com]
> -=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644
  2025-10-30  6:27   ` Mittal, Anuj
@ 2025-10-30  8:10     ` Ankur Tyagi
  0 siblings, 0 replies; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-30  8:10 UTC (permalink / raw)
  To: Mittal, Anuj; +Cc: openembedded-devel@lists.openembedded.org

On Thu, Oct 30, 2025 at 7:27 PM Mittal, Anuj <anuj.mittal@intel.com> wrote:
>
> On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
> lists.openembedded.org wrote:
> > Details https://nvd.nist.gov/vuln/detail/CVE-2025-53644
> >
> > CVE was fixed by [1] but the change [2] which introduced CVE was not
> > present this version (4.9.0).
> >
> > $ git tag --no-contains 40faced6 | grep 4.9.0
> > 4.9.0
> >
> > [1]
> > https://github.com/opencv/opencv/commit/a39db41390de546d18962ee1278bd6dbb715f466
> > [2]
> > https://github.com/opencv/opencv/commit/40faced6c18baa6fbc7c1fbd409d59d6ddecc74f#diff-ae9fbe252ce7879e83e7ae22e594d50b5a8d2ea8dfb4cc8e02e896902a1a8f10R2872
> >
> > Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> > ---
> >  meta-oe/recipes-support/opencv/opencv_4.9.0.bb | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/meta-oe/recipes-support/opencv/opencv_4.9.0.bb b/meta-
> > oe/recipes-support/opencv/opencv_4.9.0.bb
> > index cf836d3ecf..e4910553bf 100644
> > --- a/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
> > +++ b/meta-oe/recipes-support/opencv/opencv_4.9.0.bb
> > @@ -208,3 +208,5 @@ do_install:append() {
> >          rm -rf ${D}${bindir}/setup_vars_opencv4.sh
> >      fi
> >  }
> > +
> > +CVE_STATUS[CVE-2025-53644] = "cpe-incorrect: This version (4.9.0)
> > doesn't contain the change which introduced CVE."
>
> Actually it looks like CPE data was revised recently to include minimum
> version as 4.10.0 so this should not be required now. Can you please
> check again?
>

You are right about updated CPE, it is not valid anymore for v4.9.0.
Thanks for looking into it.

> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#120693):
> > https://lists.openembedded.org/g/openembedded-devel/message/120693
> > Mute This Topic: https://lists.openembedded.org/mt/115766814/3616702
> > Group Owner: openembedded-devel+owner@lists.openembedded.org
> > Unsubscribe:
> > https://lists.openembedded.org/g/openembedded-devel/unsub [
> > anuj.mittal@intel.com]
> > -=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release
  2025-10-30  6:30   ` Mittal, Anuj
@ 2025-10-30  8:33     ` Ankur Tyagi
  0 siblings, 0 replies; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-30  8:33 UTC (permalink / raw)
  To: anuj.mittal; +Cc: openembedded-devel@lists.openembedded.org

On Thu, Oct 30, 2025 at 7:30 PM Anuj Mittal via lists.openembedded.org
<anuj.mittal=intel.com@lists.openembedded.org> wrote:
>
> On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
> lists.openembedded.org wrote:
> > This release fixes CVE-2024-42458
> > https://github.com/any1/neatvnc/compare/v0.8.0...v0.8.1
> >
> > Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> > ---
> >  .../neatvnc/{neatvnc_0.8.0.bb => neatvnc_0.8.1.bb}          | 6
> > ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> >  rename meta-oe/recipes-graphics/neatvnc/{neatvnc_0.8.0.bb =>
> > neatvnc_0.8.1.bb} (81%)
> >
> > diff --git a/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
> > b/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
> > similarity index 81%
> > rename from meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
> > rename to meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
> > index c9c4a6c27a..572134b47c 100644
> > --- a/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.0.bb
> > +++ b/meta-oe/recipes-graphics/neatvnc/neatvnc_0.8.1.bb
> > @@ -4,9 +4,9 @@ HOMEPAGE = "https://github.com/any1/neatvnc"
> >  LICENSE = "ISC"
> >  LIC_FILES_CHKSUM =
> > "file://COPYING;md5=94fc374e7174f41e3afe0f027ee59ff7"
> >
> > -SRC_URI =
> > "git://github.com/any1/neatvnc;branch=master;protocol=https"
> > +SRC_URI = "git://github.com/any1/neatvnc;branch=v0.8;protocol=https"
> >
> > -SRCREV = "46432ce8cade0b54a38d4bb42eb07f96c8ff49fd"
> > +SRCREV = "07081567ab21a2b099ceb41ae8cab872a31cbb9a"
> >
> >  S = "${WORKDIR}/git"
> >
> > @@ -36,3 +36,5 @@ do_install:append () {
> >  }
> >
> >  BBCLASSEXTEND = "native"
> > +
> > +CVE_STATUS[CVE-2024-42458] = "fixed-version: No action required. The
> > current version (0.8.1) is not affected by the CVE."
>
> Why is this required? The data shows versions till 0.8.1 (excluding) to
> be vulnerable so this shouldn't be required? Am I misinterpreting
> something?

No, you are not.
Please drop this patch and I'll re-send it separately

>
> >
> >
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#121194): https://lists.openembedded.org/g/openembedded-devel/message/121194
> Mute This Topic: https://lists.openembedded.org/mt/115766813/3619737
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [ankur.tyagi85@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410
  2025-10-30  6:38 ` [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Mittal, Anuj
@ 2025-10-31  0:41   ` Ankur Tyagi
  0 siblings, 0 replies; 12+ messages in thread
From: Ankur Tyagi @ 2025-10-31  0:41 UTC (permalink / raw)
  To: Mittal, Anuj
  Cc: openembedded-devel@lists.openembedded.org,
	ninette@thehoodiefirm.com, raj.khem@gmail.com

On Thu, Oct 30, 2025 at 7:38 PM Mittal, Anuj <anuj.mittal@intel.com> wrote:
>
> On Wed, 2025-10-15 at 19:35 +1300, Ankur Tyagi via
> lists.openembedded.org wrote:
> > From: Ninette Adhikari <ninette@thehoodiefirm.com>
> >
> > The recipe used in the `meta-openembedded` is a different mercurial
> > package compared to the one which has the CVE issue.
> > Package used in `meta-embedded`: https://www.mercurial-scm.org/
> > Package with CVE issue is a Jenkins plugin:
> > https://plugins.jenkins.io/mercurial/
> > (This is reflected in the CPE)
> >
> > Signed-off-by: Ninette Adhikari <ninette@thehoodiefirm.com>
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > (cherry picked from commit bf84ac1c4c1a00c2aa92a09fbdfae128d055fe05)
> > Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
> > ---
> >  meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> > b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> > index 2451a36be2..53fe0a28ae 100644
> > --- a/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> > +++ b/meta-oe/recipes-devtools/mercurial/mercurial_6.5.bb
> > @@ -34,3 +34,4 @@ PACKAGES =+ "${PN}-python"
> >  FILES:${PN} += "${PYTHON_SITEPACKAGES_DIR} ${datadir}"
> >  FILES:${PN}-python = "${nonarch_libdir}/${PYTHON_DIR}"
> >
> > +CVE_STATUS[CVE-2022-43410] = "cpe-incorrect: The recipe used in the
> > `meta-openembedded` is a different mercurial package compared to the
> > one which has the CVE issue."
>
> This shouldn't be a cpe-incorrect in that case and should use
> mercurial-scm as the vendor in CVE_PRODUCT.

Good point, I'll send the fix to the master branch as well.
Please drop this patch.

>
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#120690):
> > https://lists.openembedded.org/g/openembedded-devel/message/120690
> > Mute This Topic: https://lists.openembedded.org/mt/115766810/3616702
> > Group Owner: openembedded-devel+owner@lists.openembedded.org
> > Unsubscribe:
> > https://lists.openembedded.org/g/openembedded-devel/unsub [
> > anuj.mittal@intel.com]
> > -=-=-=-=-=-=-=-=-=-=-=-


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2025-10-31  0:41 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-10-15  6:35 [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Ankur Tyagi
2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 2/4] libvpx: patch CVE-2024-5197 Ankur Tyagi
2025-10-15  8:44   ` Gyorgy Sarvari
2025-10-15  9:23     ` Ankur Tyagi
2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 3/4] neatvnc: upgrade to 0.8.1 release Ankur Tyagi
2025-10-30  6:30   ` Mittal, Anuj
2025-10-30  8:33     ` Ankur Tyagi
2025-10-15  6:35 ` [oe][meta-oe][scarthgap][PATCH 4/4] opencv: ignore CVE-2025-53644 Ankur Tyagi
2025-10-30  6:27   ` Mittal, Anuj
2025-10-30  8:10     ` Ankur Tyagi
2025-10-30  6:38 ` [oe][meta-oe][scarthgap][PATCH 1/4] mercurial: Update CVE status for CVE-2022-43410 Mittal, Anuj
2025-10-31  0:41   ` Ankur Tyagi

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.