[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120910-CVE-2025-40333-4f6a@gregkh>
Date: Tue, 9 Dec 2025 13:10:15 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40333: f2fs: fix infinite loop in __insert_extent_tree()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix infinite loop in __insert_extent_tree()
When we get wrong extent info data, and look up extent_node in rb tree,
it will cause infinite loop (CONFIG_F2FS_CHECK_FS=n). Avoiding this by
return NULL and print some kernel messages in that case.
The Linux kernel CVE team has assigned CVE-2025-40333 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.117 with commit 765f8816d3959ef1f3f7f85e2af748594d091f40
Fixed in 6.12.58 with commit c0b9951bb2668d67eb4817bb23fc109abc08c075
Fixed in 6.17.8 with commit f4c31adcb2a0556f43776d4e51a67de88d7fb9ee
Fixed in 6.18 with commit 23361bd54966b437e1ed3eb1a704572f4b279e58
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-2025-40333
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/extent_cache.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/765f8816d3959ef1f3f7f85e2af748594d091f40
https://git.kernel.org/stable/c/c0b9951bb2668d67eb4817bb23fc109abc08c075
https://git.kernel.org/stable/c/f4c31adcb2a0556f43776d4e51a67de88d7fb9ee
https://git.kernel.org/stable/c/23361bd54966b437e1ed3eb1a704572f4b279e58
Powered by blists - more mailing lists