From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
"hthakar@cisco.com" <hthakar@cisco.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "xe-linux-external@cisco.com" <xe-linux-external@cisco.com>
Subject: Re: [OE-core][scarthgap][PATCH] python3-ply: set status for CVE-2025-56005
Date: Mon, 21 Sep 2026 17:07:03 +0200 [thread overview]
Message-ID: <DLL36OQUQAJS.8YKDBJUDHDWB@smile.fr> (raw)
In-Reply-To: <AS8PR10MB507315C1FA2936B1B4EF91D8FDBD2@AS8PR10MB5073.EURPRD10.PROD.OUTLOOK.COM>
On Sat Sep 12, 2026 at 4:37 PM CEST, Peter Marko wrote:
>
>
>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-
>> core@lists.openembedded.org> On Behalf Of Yoann Congal via
>> lists.openembedded.org
>> Sent: Friday, September 11, 2026 11:03 AM
>> To: hthakar@cisco.com; openembedded-core@lists.openembedded.org
>> Cc: xe-linux-external@cisco.com
>> Subject: Re: [OE-core][scarthgap][PATCH] python3-ply: set status for CVE-2025-
>> 56005
>>
>> On Thu Sep 3, 2026 at 7:19 AM CEST, Hetvi Thakar -X (hthakar - E INFOCHIPS
>> PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
>> > From: Hetvi Thakar <hthakar@cisco.com>
>> >
>> > PLY 3.11 contains the picklefile parameter described by
>> > CVE-2025-56005, but exploitation requires an application to
>> > explicitly pass an attacker-controlled pickle file to yacc().
>> >
>> > No OE-Core consumer uses this parameter. Ubuntu ignores the issue for
>> > the same reason [1], and NVD records the CVE as disputed [2].
>> >
>> > [1] https://ubuntu.com/security/CVE-2025-56005
>> > [2] https://nvd.nist.gov/vuln/detail/CVE-2025-56005
>> >
>> > Signed-off-by: Hetvi Thakar <hthakar@cisco.com>
>> > ---
>> > meta/recipes-devtools/python/python3-ply_3.11.bb | 1 +
>> > 1 file changed, 1 insertion(+)
>> >
>> > diff --git a/meta/recipes-devtools/python/python3-ply_3.11.bb b/meta/recipes-
>> devtools/python/python3-ply_3.11.bb
>> > index 0855c871cf..5bed977158 100644
>> > --- a/meta/recipes-devtools/python/python3-ply_3.11.bb
>> > +++ b/meta/recipes-devtools/python/python3-ply_3.11.bb
>> > @@ -16,5 +16,6 @@ RDEPENDS:${PN}:class-target += "\
>> > "
>> >
>> > CVE_PRODUCT = "dabeaz:ply"
>> > +CVE_STATUS[CVE-2025-56005] = "disputed: Exploitation requires application-
>> specific use of PLY's picklefile parameter with attacker-controlled pickle data"
>> >
>> > BBCLASSEXTEND = "native nativesdk"
>>
>> Hello,
>>
>> As fas as I can tell, this patch is also needed on wrynose.
>> I can't merge here until this is fixed there.
>>
>> Can you send a patch to fix this on this branch and then, ping back
>> here?
>
> Hello Yoann,
>
> In wrynose this will be fixed by update of sbom-cve-check tooling.
>
> Peter
Right, thanks Peter!
>
>>
>> Thanks!
>> --
>> Yoann Congal
>> Smile ECS
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-09-21 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 5:19 [OE-core][scarthgap][PATCH] python3-ply: set status for CVE-2025-56005 Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-11 9:03 ` Yoann Congal
2026-09-12 14:37 ` Marko, Peter
2026-09-21 15:07 ` Yoann Congal [this message]
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=DLL36OQUQAJS.8YKDBJUDHDWB@smile.fr \
--to=yoann.congal@smile.fr \
--cc=Peter.Marko@siemens.com \
--cc=hthakar@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xe-linux-external@cisco.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