From: "Benjamin Robin (Schneider Electric)" <benjamin.robin@bootlin.com>
To: openembedded-core@lists.openembedded.org
Cc: olivier.benjamin@bootlin.com, mathieu.dubois-briand@bootlin.com,
pascal.eberhard@se.com, wahid.essid@se.com,
"Benjamin Robin (Schneider Electric)"
<benjamin.robin@bootlin.com>
Subject: [scarthgap][PATCH 0/3] python3: fix CVE-2026-11940, CVE-2026-11972 and CVE-2026-9669
Date: Mon, 06 Jul 2026 13:01:34 +0200 [thread overview]
Message-ID: <20260706-fix-cves-python-scarthgap-v1-0-8d51db14f7ac@bootlin.com> (raw)
This series fix the following CVEs:
- CVE-2026-11940
- CVE-2026-11972
- CVE-2026-9669
On master and wrynose the CVE-2026-9669 patch is not necessary since it is
already included in 3.14.6
Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
---
Benjamin Robin (Schneider Electric) (3):
python3: fix CVE-2026-11940
python3: fix CVE-2026-11972
python3: fix CVE-2026-9669
.../python/python3/CVE-2026-11940.patch | 66 +++++++++++++++
.../python/python3/CVE-2026-11972.patch | 58 +++++++++++++
.../python/python3/CVE-2026-9669.patch | 97 ++++++++++++++++++++++
meta/recipes-devtools/python/python3_3.12.13.bb | 3 +
4 files changed, 224 insertions(+)
---
base-commit: 2814f0962f56c8d1afa4de76d2895ba9b5cb767d
change-id: 20260706-fix-cves-python-scarthgap-76eb4e1f3d78
Best regards,
--
Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
next reply other threads:[~2026-07-06 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 11:01 Benjamin Robin (Schneider Electric) [this message]
2026-07-06 11:01 ` [scarthgap][PATCH 1/3] python3: fix CVE-2026-11940 Benjamin Robin (Schneider Electric)
2026-07-06 11:01 ` [scarthgap][PATCH 2/3] python3: fix CVE-2026-11972 Benjamin Robin (Schneider Electric)
2026-07-06 11:01 ` [scarthgap][PATCH 3/3] python3: fix CVE-2026-9669 Benjamin Robin (Schneider Electric)
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=20260706-fix-cves-python-scarthgap-v1-0-8d51db14f7ac@bootlin.com \
--to=benjamin.robin@bootlin.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=olivier.benjamin@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pascal.eberhard@se.com \
--cc=wahid.essid@se.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 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.