CVE-2026-53303
f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show()
Vexday Risk Score
3Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS —EPSS 0.2%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
26 Jun 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
In the Linux kernel, the following vulnerability has been resolved:
f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show()
In f2fs_sbi_show(), the extension_list, extension_count and
hot_ext_count are read without holding sbi->sb_lock. If a concurrent
sysfs store modifies the extension list via f2fs_update_extension_list(),
the show path may read inconsistent count and array contents, potentially
leading to out-of-bounds access or displaying stale data.
Fix this by holding sb_lock around the entire extension list read
and format operation.
Affected products
Linux · LinuxWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://git.kernel.org/stable/c/4b3a1bf4c2ffd4c9595d900ead78c9035894a025https://git.kernel.org/stable/c/5909bedbed38c558bee7cb6758ceedf9bc3a9194https://git.kernel.org/stable/c/cea15f66b7b68b2c50943a6660e0692c6635e4ebhttps://git.kernel.org/stable/c/d0e877810baf613b018fd9747440b9d4d9db1428https://git.kernel.org/stable/c/d3ff0c121bbaef026df6248ab7ef6f0b068b0647https://git.kernel.org/stable/c/ea3ab43a1f3cf2c7cecd75c8be1ee99a5e94a92e