From: Junjie Cao <junjie.cao@linux.dev>
To: openembedded-core@lists.openembedded.org
Cc: paul@pbarker.dev
Subject: [OE-core][PATCH v4 6/8] cve-exclusions: set status for CVE-2023-3397
Date: Sun, 23 Aug 2026 23:21:21 -0500 [thread overview]
Message-ID: <20260824042123.1456876-7-junjie.cao@linux.dev> (raw)
In-Reply-To: <20260824042123.1456876-1-junjie.cao@linux.dev>
txEnd() in fs/jfs/jfs_txnmgr.c reads the log pointer from the
superblock info, drops TXN_LOCK and then takes log->gclock, while
lmLogClose() can free that log during umount.
No fix has been merged. The 2023 proposal was withdrawn by its author
("I think my fix method is not a good solution"), and proposals in 2026
for similar jfs slab use-after-free races are unreviewed:
https://lore.kernel.org/all/20230515095956.17898-1-zyytlz.wz@163.com/
https://lore.kernel.org/all/20260505123330.2822833-1-tristmd@gmail.com/
https://lore.kernel.org/all/20260603171620.2532527-1-jie.wang@intel.com/
A similar use-after-free was reported against 7.0-rc1 in June 2026,
with the free stack in lmLogClose() via jfs_umount(), and syzbot has
an open slab use-after-free write in lmLogSync(); the txEnd() sequence
is unchanged in linux-next 20260727:
https://lore.kernel.org/all/6a3eedfa.fd822575.2d6b21.e180@mx.google.com/
https://syzkaller.appspot.com/bug?extid=ea7ed3bb2f444cb4dfeb
CC: Paul Barker <paul@pbarker.dev>
AI-Generated: Uses Claude (claude-opus-5)
Signed-off-by: Junjie Cao <junjie.cao@linux.dev>
---
v4:
- describe the 2026 proposals and reports as similar races rather than
the same one; drop the kernel-cache configuration paragraph; use the
review's comment and status wording
- name the open syzbot bug as the lmLogSync write rather than the
txEnd write
v3: https://lore.kernel.org/openembedded-core/20260812072842.1176341-1-junjie.cao@linux.dev/
meta/recipes-kernel/linux/cve-exclusion.inc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/meta/recipes-kernel/linux/cve-exclusion.inc b/meta/recipes-kernel/linux/cve-exclusion.inc
index 4318fc79..a133bf08 100644
--- a/meta/recipes-kernel/linux/cve-exclusion.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion.inc
@@ -231,3 +231,12 @@ CVE_STATUS[CVE-2022-1247] = "fixed-version: Fixed from version 6.17"
# https://security-tracker.debian.org/tracker/CVE-2022-4543
# https://ubuntu.com/security/CVE-2022-4543
CVE_STATUS[CVE-2022-4543] = "unpatched: No fix has been proposed"
+
+# Triaged August 2026 - Originally proposed fix was withdrawn, similar
+# slab-use-after-free appears to have been re-found by syzkaller in 2026.
+# Unfixed in Debian, "needs evaluation" in Ubuntu.
+# https://lore.kernel.org/lkml/CAJedcCzmx02bfa22QezE8mu-iDsSdSy_oApT2ozCWO8O-8MJEQ@mail.gmail.com/
+# https://syzkaller.appspot.com/bug?extid=ea7ed3bb2f444cb4dfeb
+# https://security-tracker.debian.org/tracker/CVE-2023-3397
+# https://ubuntu.com/security/CVE-2023-3397
+CVE_STATUS[CVE-2023-3397] = "unpatched: Proposed fix was withdrawn"
--
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 ` Junjie Cao [this message]
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 ` [OE-core][PATCH v4 8/8] cve-exclusions: set status for CVE-2023-6240 Junjie Cao
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-7-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox