blob: 2d670ca16399a7a8e9ecb6589dddf813738ca64f [file] [log] [blame]
From bippy-1.1.0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-50272: filemap: Fix bounds checking in filemap_read()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
filemap: Fix bounds checking in filemap_read()
If the caller supplies an iocb->ki_pos value that is close to the
filesystem upper limit, and an iterator with a count that causes us to
overflow that limit, then filemap_read() enters an infinite loop.
This behaviour was discovered when testing xfstests generic/525 with the
"localio" optimisation for loopback NFS mounts.
The Linux kernel CVE team has assigned CVE-2024-50272 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.9 with commit c2a9737f45e27d8263ff9643f994bda9bac0b944 and fixed in 5.15.181 with commit 6cc52df69e8464811f9f6fc12f7aaa78451eb0b8
Issue introduced in 4.9 with commit c2a9737f45e27d8263ff9643f994bda9bac0b944 and fixed in 6.1.117 with commit 26530b757c81f1389fb33ae0357500150933161b
Issue introduced in 4.9 with commit c2a9737f45e27d8263ff9643f994bda9bac0b944 and fixed in 6.6.61 with commit a2746ab3bbc9c6408da5cd072653ec8c24749235
Issue introduced in 4.9 with commit c2a9737f45e27d8263ff9643f994bda9bac0b944 and fixed in 6.11.8 with commit 6450e73f4c86d481ac2e22e1bc848d346e140826
Issue introduced in 4.9 with commit c2a9737f45e27d8263ff9643f994bda9bac0b944 and fixed in 6.12 with commit ace149e0830c380ddfce7e466fe860ca502fe4ee
Issue introduced in 3.16.40 with commit 272830350bb1bb5bb39395966ea63b9864b135d1
Issue introduced in 4.7.10 with commit fbc7b803831e5c8a42c1f3427a17e55a814d6b3c
Issue introduced in 4.8.4 with commit 3d549dcfbbb0ecdaa571431a27ee5da9f2466716
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-50272
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:
mm/filemap.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/6cc52df69e8464811f9f6fc12f7aaa78451eb0b8
https://git.kernel.org/stable/c/26530b757c81f1389fb33ae0357500150933161b
https://git.kernel.org/stable/c/a2746ab3bbc9c6408da5cd072653ec8c24749235
https://git.kernel.org/stable/c/6450e73f4c86d481ac2e22e1bc848d346e140826
https://git.kernel.org/stable/c/ace149e0830c380ddfce7e466fe860ca502fe4ee