From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2023-52600: jfs: fix uaf in jfs_evict_inode
Date: Wed, 6 Mar 2024 06:45:58 +0000 [thread overview]
Message-ID: <2024030646-CVE-2023-52600-6ffe@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
jfs: fix uaf in jfs_evict_inode
When the execution of diMount(ipimap) fails, the object ipimap that has been
released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs
when rcu_core() calls jfs_free_node().
Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as
ipimap.
The Linux kernel CVE team has assigned CVE-2023-52600 to this issue.
Affected and fixed versions
===========================
Fixed in 4.19.307 with commit 81b4249ef372
Fixed in 5.4.269 with commit 93df0a2a0b3c
Fixed in 5.10.210 with commit bc6ef64dbe71
Fixed in 5.15.149 with commit 8e44dc3f96e9
Fixed in 6.1.77 with commit 32e8f2d95528
Fixed in 6.6.16 with commit 1696d6d7d4a1
Fixed in 6.7.4 with commit bacdaa042513
Fixed in 6.8-rc1 with commit e0e1958f4c36
Please see https://www.kernel.org or 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-52600
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/jfs_mount.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/81b4249ef37297fb17ba102a524039a05c6c5d35
https://git.kernel.org/stable/c/93df0a2a0b3cde2d7ab3a52ed46ea1d6d4aaba5f
https://git.kernel.org/stable/c/bc6ef64dbe71136f327d63b2b9071b828af2c2a8
https://git.kernel.org/stable/c/8e44dc3f96e903815dab1d74fff8faafdc6feb61
https://git.kernel.org/stable/c/32e8f2d95528d45828c613417cb2827d866cbdce
https://git.kernel.org/stable/c/1696d6d7d4a1b373e96428d0fe1166bd7c3c795e
https://git.kernel.org/stable/c/bacdaa04251382d7efd4f09f9a0686bfcc297e2e
https://git.kernel.org/stable/c/e0e1958f4c365e380b17ccb35617345b31ef7bf3
reply other threads:[~2024-03-06 6:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2024030646-CVE-2023-52600-6ffe@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).