Technical impact
The vulnerability arises from a race condition in the f2fs filesystem’s page‑cache handling during garbage‑collection. When a tail‑end folio is evicted and its page‑cache references are removed, a concurrent split operation can free the folio while its LRU links remain in the kernel’s list. If folio_isolate_lru clears the PG_lru flag before the final reference is released, the kernel’s LRU list becomes corrupted, leading to a list_del failure and a kernel panic. This aligns with CWEs 362 and 367 and results in a denial‑of‑service.
Affected Systems
Any Linux system that includes the f2fs filesystem code before the revert of commit 9609dd704725a40cd63d915f2ab6c44248a44598 is vulnerable. The issue is present in the mainline Linux kernel and therefore applies to all distributions that ship the kernel without the revert. Systems using a kernel that already incorporates the revert are considered safe; all others should be treated as at risk.
Risk and Exploitability
The CVSS score of 7.8 indicates moderate to high severity. The EPSS score is below 1%, and the vulnerability is not listed in the CISA KEV catalog, implying a low current exploitation probability. Exploitation requires an f2fs partition to be nearly full, meaning a local or elevated‑privilege attacker can trigger the crash by filling the filesystem. The flaw causes a denial of service but does not provide direct confidentiality or integrity compromise, and no publicly available exploit code is documented.
Ubuntu USN