[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100105-CVE-2023-53457-629a@gregkh>
Date: Wed, 1 Oct 2025 13:42:27 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53457: FS: JFS: Fix null-ptr-deref Read in txBegin
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
FS: JFS: Fix null-ptr-deref Read in txBegin
Syzkaller reported an issue where txBegin may be called
on a superblock in a read-only mounted filesystem which leads
to NULL pointer deref. This could be solved by checking if
the filesystem is read-only before calling txBegin, and returning
with appropiate error code.
The Linux kernel CVE team has assigned CVE-2023-53457 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.324 with commit a7225e9e09519deb7e0c42eb6070029cc456e84d
Fixed in 4.19.293 with commit 1b4c144767736221cad92c132f72b3c6ed06a0ea
Fixed in 5.4.255 with commit a7d17d6bd7cd4f6940b335ea7a6fce5b6d22adc2
Fixed in 5.10.192 with commit 2a3f20efe6c901d4c0871cfd1d8c65e2ade71fc1
Fixed in 5.15.123 with commit 3e94d0d378d2754b26fc54b429582553f7b53e15
Fixed in 6.1.42 with commit 3e5eb6c5ecd8ddb9cfea751cf30f9e23eac97ca3
Fixed in 6.4.7 with commit fd2db13fb72ff18c633a48229589d42ceb89d1f8
Fixed in 6.5 with commit 47cfdc338d674d38f4b2f22b7612cc6a2763ba27
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53457
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/jfs/namei.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/a7225e9e09519deb7e0c42eb6070029cc456e84d
https://git.kernel.org/stable/c/1b4c144767736221cad92c132f72b3c6ed06a0ea
https://git.kernel.org/stable/c/a7d17d6bd7cd4f6940b335ea7a6fce5b6d22adc2
https://git.kernel.org/stable/c/2a3f20efe6c901d4c0871cfd1d8c65e2ade71fc1
https://git.kernel.org/stable/c/3e94d0d378d2754b26fc54b429582553f7b53e15
https://git.kernel.org/stable/c/3e5eb6c5ecd8ddb9cfea751cf30f9e23eac97ca3
https://git.kernel.org/stable/c/fd2db13fb72ff18c633a48229589d42ceb89d1f8
https://git.kernel.org/stable/c/47cfdc338d674d38f4b2f22b7612cc6a2763ba27
Powered by blists - more mailing lists