[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022655-CVE-2022-49425-05aa@gregkh>
Date: Wed, 26 Feb 2025 03:11:39 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49425: f2fs: fix dereference of stale list iterator after loop body
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix dereference of stale list iterator after loop body
The list iterator variable will be a bogus pointer if no break was hit.
Dereferencing it (cur->page in this case) could load an out-of-bounds/undefined
value making it unsafe to use that in the comparision to determine if the
specific element was found.
Since 'cur->page' *can* be out-ouf-bounds it cannot be guaranteed that
by chance (or intention of an attacker) it matches the value of 'page'
even though the correct element was not found.
This is fixed by using a separate list iterator variable for the loop
and only setting the original variable if a suitable element was found.
Then determing if the element was found is simply checking if the
variable is set.
The Linux kernel CVE team has assigned CVE-2022-49425 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 4.19.247 with commit 385edd3ce5b4b1e9d31f474a5e35a39779ec1110
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 5.4.198 with commit 5e47a7add3dda7f236548c5ec3017776dc2a729f
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 5.10.121 with commit 51d584704d18e60fa473823654f35611c777b291
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 5.15.46 with commit 45b2b7d7108ae1e25a5036cab04ab9273e792332
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 5.17.14 with commit b26e1c777890e4b938136deb8ec07a29f33862e4
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 5.18.3 with commit ed7efc472c00986dcd6903ab6ed165c7fa167674
Issue introduced in 4.12 with commit 8c242db9b8c01b252290e23827163787f07e01d1 and fixed in 5.19 with commit 2aaf51dd39afb6d01d13f1e6fe20b684733b37d5
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-2022-49425
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/f2fs/segment.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/385edd3ce5b4b1e9d31f474a5e35a39779ec1110
https://git.kernel.org/stable/c/5e47a7add3dda7f236548c5ec3017776dc2a729f
https://git.kernel.org/stable/c/51d584704d18e60fa473823654f35611c777b291
https://git.kernel.org/stable/c/45b2b7d7108ae1e25a5036cab04ab9273e792332
https://git.kernel.org/stable/c/b26e1c777890e4b938136deb8ec07a29f33862e4
https://git.kernel.org/stable/c/ed7efc472c00986dcd6903ab6ed165c7fa167674
https://git.kernel.org/stable/c/2aaf51dd39afb6d01d13f1e6fe20b684733b37d5
Powered by blists - more mailing lists