From: Junjie Cao <junjie.cao@linux.dev>
To: openembedded-core@lists.openembedded.org
Cc: paul@pbarker.dev
Subject: [OE-core][PATCH v4 8/8] cve-exclusions: set status for CVE-2023-6240
Date: Sun, 23 Aug 2026 23:21:23 -0500 [thread overview]
Message-ID: <20260824042123.1456876-9-junjie.cao@linux.dev> (raw)
In-Reply-To: <20260824042123.1456876-1-junjie.cao@linux.dev>
"Marvin" is Hubert Kario's Bleichenbacher-style timing oracle research:
https://people.redhat.com/~hkario/marvin/
The affected code is the generic software RSA PKCS#1 v1.5 unpadding in
crypto/rsa-pkcs1pad.c. pkcs1pad_decrypt_complete() has three
secret-dependent early exits (leading zero byte, block type, minimum
padding length) and a loop whose trip count depends on the position of
the separator, so the time taken reveals padding validity. There is no
constant-time unpadding or implicit-rejection fallback in the tree.
Red Hat classifies it CWE-203 and has shipped fixes only in RHEL errata
(RHSA-2024:2758, RHSA-2024:3618 and others); the bugzilla is still NEW.
Ubuntu records "appears unfixed in upstream as of 2024.08.24" and
Debian lists src:linux vulnerable in all suites:
https://access.redhat.com/security/cve/CVE-2023-6240
https://ubuntu.com/security/CVE-2023-6240
https://security-tracker.debian.org/tracker/CVE-2023-6240
CC: Paul Barker <paul@pbarker.dev>
AI-Generated: Uses Claude (claude-opus-5)
Signed-off-by: Junjie Cao <junjie.cao@linux.dev>
---
v4:
- drop the practical-exposure paragraph; use the review's comment and
status wording
- quote Ubuntu's note verbatim
v3: https://lore.kernel.org/openembedded-core/20260812072842.1176341-1-junjie.cao@linux.dev/
meta/recipes-kernel/linux/cve-exclusion.inc | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/meta/recipes-kernel/linux/cve-exclusion.inc b/meta/recipes-kernel/linux/cve-exclusion.inc
index 4729191a..8714173c 100644
--- a/meta/recipes-kernel/linux/cve-exclusion.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion.inc
@@ -250,3 +250,13 @@ CVE_STATUS[CVE-2023-3397] = "unpatched: Proposed fix was withdrawn"
# https://ubuntu.com/security/CVE-2023-6238
# https://lore.kernel.org/linux-nvme/20231016060519.231880-1-joshi.k@samsung.com/
CVE_STATUS[CVE-2023-6238] = "unpatched: Proposed fix was not merged"
+
+# Triaged August 2026 - "Marvin" attack, Red Hat reports this fixed but the
+# exact patch is unidentified (see RHSA-2024:2758, RHSA-2024:3618 & others).
+# Unfixed in Debian, "Needs evaluation" in Ubuntu.
+# https://people.redhat.com/~hkario/marvin/
+# https://access.redhat.com/security/cve/cve-2023-6240
+# https://security-tracker.debian.org/tracker/CVE-2023-6240
+# https://ubuntu.com/security/CVE-2023-6240
+CVE_STATUS[CVE-2023-6240] = "unpatched: Fixed in RHEL but patch not identified \
+publicly"
--
2.43.0
next prev parent reply other threads:[~2026-08-24 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 4:21 [OE-core][PATCH v4 0/8] cve-exclusions: triage eight kernel CVEs lacking upstream fix data Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 1/8] cve-exclusions: set status for CVE-2019-14899 Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 2/8] cve-exclusions: set status for CVE-2021-3714 Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 3/8] cve-exclusions: set status for CVE-2021-3864 Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 4/8] cve-exclusions: set status for CVE-2022-1247 Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 5/8] cve-exclusions: set status for CVE-2022-4543 Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 6/8] cve-exclusions: set status for CVE-2023-3397 Junjie Cao
2026-08-24 4:21 ` [OE-core][PATCH v4 7/8] cve-exclusions: set status for CVE-2023-6238 Junjie Cao
2026-08-24 4:21 ` Junjie Cao [this message]
2026-08-24 7:57 ` [OE-core][PATCH v4 0/8] cve-exclusions: triage eight kernel CVEs lacking upstream fix data 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=20260824042123.1456876-9-junjie.cao@linux.dev \
--to=junjie.cao@linux.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
/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.