CVE-2026-53130 json
fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START
published 4mo ago modified 3mo ago also EUVD-2026-38998
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START
omfs_fill_super() rejects oversized s_sys_blocksize values (> PAGE_SIZE), but it does not reject values smaller than OMFS_DIR_START (0x1b8 = 440).
Later, omfs_make_empty() uses
sbi->s_sys_blocksize - OMFS_DIR_START
as the length argument to memset(). Since s_sys_blocksize is u32, a crafted filesystem image with s_sys_blocksize < OMFS_DIR_START causes an unsigned underflow there, wrapping to a value near 2^32. That drives a ~4 GiB memset() from bh->b_data + OMFS_DIR_START and overwrites kernel memory far beyond the backing block buffer.
Add the corresponding lower-bound check alongside the existing upper-bound check in omfs_fill_super(), so that malformed images are rejected during superblock validation before any filesystem data is processed.
Patch / fix
- Linux Linux 5.10.258, 5.15.209, 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-53130
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- 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 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
ubuntu advisories UBUNTU-CVE-2026-53130
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/fbc72f5c645155dc2ed3573243ed20f9913e3a54 commit
- git.kernel.org/stable/c/5822a05a841a10794ad818620dd2af490b0705d3 commit
- git.kernel.org/stable/c/754ff1bea3819a90c6f33cccfc1a299ef7609f07 commit
- git.kernel.org/stable/c/131ea3e57fc22936ed0e2c8330f2e36106172f51 commit
- git.kernel.org/stable/c/79f84af38c9fef9deb0e02c79eb969b5541c2644 commit
- git.kernel.org/stable/c/6561afc38398e3518a29c5eebb975c30468f98a6 commit
- git.kernel.org/stable/c/817f16ed62bc58a168417bfb5e859c2a370bab03 commit
- git.kernel.org/stable/c/0621c385fda1376e967f37ccd534c26c3e511d14 commit
Is CVE-2026-53130 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-53130 updated cvss 7.8
kernel: Linux kernel OMFS: Arbitrary code execution via crafted filesystem image
-
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.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-191 Integer Underflow (Wrap or Wraparound)
- Technology feeds
References
-
git.kernel.org
/stable/c/fbc72f5c645155dc2ed3573243ed20f9913e3a54
patch
-
git.kernel.org
/stable/c/5822a05a841a10794ad818620dd2af490b0705d3
patch
-
git.kernel.org
/stable/c/754ff1bea3819a90c6f33cccfc1a299ef7609f07
patch
-
git.kernel.org
/stable/c/131ea3e57fc22936ed0e2c8330f2e36106172f51
patch
-
git.kernel.org
/stable/c/79f84af38c9fef9deb0e02c79eb969b5541c2644
patch
-
git.kernel.org
/stable/c/6561afc38398e3518a29c5eebb975c30468f98a6
patch
-
git.kernel.org
/stable/c/817f16ed62bc58a168417bfb5e859c2a370bab03
patch
-
git.kernel.org
/stable/c/0621c385fda1376e967f37ccd534c26c3e511d14
patch
Sources
- CVE List CVE-2026-53130
- NVD CVE-2026-53130
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.