Vulnerability in Linux
CVE-2026-63812
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix incorrect FI_NO_EXTENT handling in __destroy_extent_node()
When __destroy_extent_node() sets the inode flag FI_NO_EXTENT, it does
not reset the length of the largest extent to 0 and update the inode
folio. Since modifications to the extent tree are disallowed afterward,
the cached largest extent may become stale. This can trigger the
following error in xfstests generic/388:
F2FS-fs (dm-0): sanity_check_extent_cache: inode (ino=1761) extent info [220057, 57, 6] is incorrect, run fsck to fix
In the f2fs_drop_inode path, __destroy_extent_node() does not need to
guarantee that et->node_cnt is 0, because concurrency with writeback
is expected in this path, and writeback may update the extent cache.
This patch reverts commit ed78aeebef05 ("f2fs: fix node_cnt race between
extent node destroy and writeback"), and remove the unnecessary zero
check of et->node_cnt.
Vulnerability class: Dirty Pipe (CVE-2022-0847)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.001, 2.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Linux — versions ed78aeebef05212ef7dca93bd931e4eff67c113f, 7.1, 42dd1c91f993431d0b399502479d00e6ad1bca71
- Linux Kernel
Weakness classification (CWE)
References
- git.kernel.org/stable/c/1f70ddb28a3c71df124da5fa4040c808116d6bb9 (Patch)
- git.kernel.org/stable/c/20190e498057997532c7f186d081011f18e0a462 (Patch)
- git.kernel.org/stable/c/58a5deb220bcac4c73bf58954c0845644c997487 (Patch)
- git.kernel.org/stable/c/7e4d8f98be63f98856a5176b9188dada6e7ba9ee (Patch)
- git.kernel.org/stable/c/edf12cbeeeabe799bd2ee21fdb5c336cce6fbad7 (Patch)