CVE-2026-53303 json
f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show()
published 4mo ago modified 4mo ago also EUVD-2026-39838
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.10-1
debian advisories DEBIAN-CVE-2026-53303
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
- linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
ubuntu advisories UBUNTU-CVE-2026-53303
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/d3ff0c121bbaef026df6248ab7ef6f0b068b0647 commit
- git.kernel.org/stable/c/cea15f66b7b68b2c50943a6660e0692c6635e4eb commit
- git.kernel.org/stable/c/4b3a1bf4c2ffd4c9595d900ead78c9035894a025 commit
- git.kernel.org/stable/c/d0e877810baf613b018fd9747440b9d4d9db1428 commit
- git.kernel.org/stable/c/ea3ab43a1f3cf2c7cecd75c8be1ee99a5e94a92e commit
- git.kernel.org/stable/c/5909bedbed38c558bee7cb6758ceedf9bc3a9194 commit
Is CVE-2026-53303 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53303 updated
kernel: f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/d3ff0c121bbaef026df6248ab7ef6f0b068b0647
patch
-
git.kernel.org
/stable/c/cea15f66b7b68b2c50943a6660e0692c6635e4eb
patch
-
git.kernel.org
/stable/c/4b3a1bf4c2ffd4c9595d900ead78c9035894a025
patch
-
git.kernel.org
/stable/c/d0e877810baf613b018fd9747440b9d4d9db1428
patch
-
git.kernel.org
/stable/c/ea3ab43a1f3cf2c7cecd75c8be1ee99a5e94a92e
patch
-
git.kernel.org
/stable/c/5909bedbed38c558bee7cb6758ceedf9bc3a9194
patch
Sources
- CVE List CVE-2026-53303
- NVD CVE-2026-53303
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.