blob: 28feabd1b20853b0a723f9efacf0313b740dce3f [file] [log] [blame]
From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-47670: ocfs2: add bounds checking to ocfs2_xattr_find_entry()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: add bounds checking to ocfs2_xattr_find_entry()
Add a paranoia check to make sure it doesn't stray beyond valid memory
region containing ocfs2 xattr entries when scanning for a match. It will
prevent out-of-bound access in case of crafted images.
The Linux kernel CVE team has assigned CVE-2024-47670 to this issue.
Affected and fixed versions
===========================
Fixed in 4.19.323 with commit b49a786beb11ff740cb9e0c20b999c2a0e1729c2
Fixed in 5.4.285 with commit 60c0d36189bad58b1a8e69af8781d90009559ea1
Fixed in 5.10.227 with commit 34759b7e4493d7337cbc414c132cef378c492a2c
Fixed in 5.15.168 with commit 5bbe51eaf01a5dd6fb3f0dea81791e5dbc6dc6dd
Fixed in 6.1.112 with commit 9b32539590a8e6400ac2f6e7cf9cbb8e08711a2f
Fixed in 6.6.53 with commit 1f6e167d6753fe3ea493cdc7f7de8d03147a4d39
Fixed in 6.10.12 with commit 8e7bef408261746c160853fc27df3139659f5f77
Fixed in 6.11 with commit 9e3041fecdc8f78a5900c3aa51d3d756e73264d6
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-2024-47670
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/ocfs2/xattr.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/b49a786beb11ff740cb9e0c20b999c2a0e1729c2
https://git.kernel.org/stable/c/60c0d36189bad58b1a8e69af8781d90009559ea1
https://git.kernel.org/stable/c/34759b7e4493d7337cbc414c132cef378c492a2c
https://git.kernel.org/stable/c/5bbe51eaf01a5dd6fb3f0dea81791e5dbc6dc6dd
https://git.kernel.org/stable/c/9b32539590a8e6400ac2f6e7cf9cbb8e08711a2f
https://git.kernel.org/stable/c/1f6e167d6753fe3ea493cdc7f7de8d03147a4d39
https://git.kernel.org/stable/c/8e7bef408261746c160853fc27df3139659f5f77
https://git.kernel.org/stable/c/9e3041fecdc8f78a5900c3aa51d3d756e73264d6