linux-cve-announce.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2023-52602: jfs: fix slab-out-of-bounds Read in dtSearch
Date: Wed,  6 Mar 2024 06:46:00 +0000	[thread overview]
Message-ID: <2024030646-CVE-2023-52602-393a@gregkh> (raw)

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

jfs: fix slab-out-of-bounds Read in dtSearch

Currently while searching for current page in the sorted entry table
of the page there is a out of bound access. Added a bound check to fix
the error.

Dave:
Set return code to -EIO

The Linux kernel CVE team has assigned CVE-2023-52602 to this issue.


Affected and fixed versions
===========================

	Fixed in 4.19.307 with commit ce8bc22e9486
	Fixed in 5.4.269 with commit 1b9d6828589d
	Fixed in 5.10.210 with commit 1c40ca3d39d7
	Fixed in 5.15.149 with commit 6c6a96c3d74d
	Fixed in 6.1.77 with commit cab0c265ba18
	Fixed in 6.6.16 with commit 7110650b85dd
	Fixed in 6.7.4 with commit bff9d4078a23
	Fixed in 6.8-rc1 with commit fa5492ee8946

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-52602
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_dtree.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/ce8bc22e948634a5c0a3fa58a179177d0e3f3950
	https://git.kernel.org/stable/c/1b9d6828589d57f94a23fb1c46112cda39d7efdb
	https://git.kernel.org/stable/c/1c40ca3d39d769931b28295b3145c25f1decf5a6
	https://git.kernel.org/stable/c/6c6a96c3d74df185ee344977d46944d6f33bb4dd
	https://git.kernel.org/stable/c/cab0c265ba182fd266c2aa3c69d7e40640a7f612
	https://git.kernel.org/stable/c/7110650b85dd2f1cee819acd1345a9013a1a62f7
	https://git.kernel.org/stable/c/bff9d4078a232c01e42e9377d005fb2f4d31a472
	https://git.kernel.org/stable/c/fa5492ee89463a7590a1449358002ff7ef63529f

                 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-52602-393a@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).