From: "Marko, Peter" <Peter.Marko@siemens.com>
To: "mail2szahir@gmail.com" <mail2szahir@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [scarthgap 03/11] ffmpeg: set status for CVE-2025-12343
Date: Wed, 11 Mar 2026 09:33:36 +0000 [thread overview]
Message-ID: <AS1PR10MB56976278971462FACDFCA9DAFD47A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <360188.1773220189767290718@lists.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
That’s a recurring question and my answer to it is unchanged - no.
However, feel free to contribute to that direction yourself.
Peter
From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of aszh07 via lists.openembedded.org
Sent: Wednesday, March 11, 2026 10:10
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [scarthgap 03/11] ffmpeg: set status for CVE-2025-12343
Hi Peter,
As you mentioned, these CVEs do not affect version 6.1.x. You verified this.
However, instead of doing these changes here, could we request that the NVD database be updated?
Thanks and regards,
Zahir
[-- Attachment #2: Type: text/html, Size: 3037 bytes --]
next prev parent reply other threads:[~2026-03-11 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 22:52 [OE-core][scarthgap 00/11] Patch review Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 01/11] gdk-pixbuf: Fix CVE-2025-6199 Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 02/11] ffmpeg: set status for CVE-2025-10256 Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 03/11] ffmpeg: set status for CVE-2025-12343 Yoann Congal
2026-03-11 9:09 ` [scarthgap " aszh07
2026-03-11 9:33 ` Marko, Peter [this message]
2026-03-07 22:52 ` [OE-core][scarthgap 04/11] zlib: Fix CVE-2026-27171 Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 05/11] harfbuzz: Fix CVE-2026-22693 Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 06/11] openssl: upgrade 3.2.6 -> 3.5.5 Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 07/11] scripts/install-buildtools: Update to 5.0.16 Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 08/11] uboot-config: Fix devtool modify Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 09/11] README: Add scarthgap subject-prefix to git-send-email suggestion Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 10/11] create-pull-request: Keep commit hash to be pulled in cover email Yoann Congal
2026-03-07 22:52 ` [OE-core][scarthgap 11/11] busybox: Fixes CVE-2025-60876 Yoann Congal
2026-03-09 8:18 ` [OE-core][scarthgap 00/11] Patch review Paul Barker
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=AS1PR10MB56976278971462FACDFCA9DAFD47A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM \
--to=peter.marko@siemens.com \
--cc=mail2szahir@gmail.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