Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <bhavesh.maheshwari@einfochips.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [wrynose][oe-core][PATCH 03/10] ffmpeg: set CVE_STATUS for CVE-2026-64832
Date: Tue, 15 Sep 2026 16:23:59 +0200	[thread overview]
Message-ID: <DLFYIFTG2IKP.NGNVCLRC36D0@smile.fr> (raw)
In-Reply-To: <20260910133357.452394-3-bhavesh.maheshwari@einfochips.com>

On Thu Sep 10, 2026 at 3:31 PM CEST, Bhavesh R Maheshwari via lists.openembedded.org wrote:
> From: Bhavesh R Maheshwari <bhavesh.maheshwari@einfochips.com>
>
> Analysis:
> - CVE-2026-64832 affects NVIDIA NVDEC hardware acceleration.[1]
> - The ffmpeg recipe does not enable or build NVIDIA NVDEC hardware acceleration by default.
> - Hence CVE is not applicable.
>
> Reference:
> [1] https://nvd.nist.gov/vuln/detail/CVE-2026-64832
>
> Signed-off-by: Bhavesh R Maheshwari <bhavesh.maheshwari@einfochips.com>
> ---
>  meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.3.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.3.bb b/meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.3.bb
> index af05ab4af9..68f09c2bc4 100644
> --- a/meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.3.bb
> +++ b/meta/recipes-multimedia/ffmpeg/ffmpeg_8.0.3.bb
> @@ -187,3 +187,4 @@ CVE_STATUS[CVE-2025-59730] = "fixed-version: this CVE are fixed since v8.0"
>  CVE_STATUS[CVE-2026-8461] = "cpe-stable-backport: this CVE are fixed since v8.0.3"
>  CVE_STATUS[CVE-2026-40962] = "cpe-stable-backport: this CVE are fixed since v8.0.2"
>  CVE_STATUS[CVE-2026-64831] = "not-applicable-config: Vulkan HEVC hardware acceleration is not enabled or built by this recipe."
> +CVE_STATUS[CVE-2026-64832] = "not-applicable-config: NVIDIA NVDEC hardware acceleration is not enabled or built by this recipe."

Same as 2/10.

Regards,
-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-09-15 14:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 13:31 [wrynose][oe-core][PATCH 01/10] ffmpeg: Fix for CVE-2026-64830 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 02/10] ffmpeg: set CVE_STATUS for CVE-2026-64831 bhavesh.maheshwari
2026-09-15 14:20   ` Yoann Congal
2026-09-15 15:06     ` [External] " Bhavesh Rajesh Maheshwari
2026-09-16  9:22     ` Bhavesh Rajesh Maheshwari
2026-09-16 10:22       ` Yoann Congal
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 03/10] ffmpeg: set CVE_STATUS for CVE-2026-64832 bhavesh.maheshwari
2026-09-15 14:23   ` Yoann Congal [this message]
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 04/10] ffmpeg: Fix for CVE-2026-64833 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 05/10] ffmpeg: Fix for CVE-2026-64834 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 06/10] ffmpeg: Fix for CVE-2026-64835 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 07/10] ffmpeg: Fix for CVE-2026-65703 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 08/10] ffmpeg: Fix for CVE-2026-65704 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 09/10] ffmpeg: Fix for CVE-2026-65705 bhavesh.maheshwari
2026-09-10 13:31 ` [wrynose][oe-core][PATCH 10/10] ffmpeg: Fix for CVE-2026-65706 bhavesh.maheshwari

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=DLFYIFTG2IKP.NGNVCLRC36D0@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=bhavesh.maheshwari@einfochips.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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