Answer in brief
CVE-2026-53130 records a High severity (CVSS 7.8) vulnerability in fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53130 records a High severity (CVSS 7.8) vulnerability in fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <fbc72f5c645155dc2ed3573243ed20f9913e3a54 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <5822a05a841a10794ad818620dd2af490b0705d3 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <754ff1bea3819a90c6f33cccfc1a299ef7609f07 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <131ea3e57fc22936ed0e2c8330f2e36106172f51 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <79f84af38c9fef9deb0e02c79eb969b5541c2644 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <6561afc38398e3518a29c5eebb975c30468f98a6 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <817f16ed62bc58a168417bfb5e859c2a370bab03 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <0621c385fda1376e967f37ccd534c26c3e511d14 | fbc72f5c645155dc2ed3573243ed20f9913e3a54, 5822a05a841a10794ad818620dd2af490b0705d3, 754ff1bea3819a90c6f33cccfc1a299ef7609f07, 131ea3e57fc22936ed0e2c8330f2e36106172f51, 79f84af38c9fef9deb0e02c79eb969b5541c2644, 6561afc38398e3518a29c5eebb975c30468f98a6, 817f16ed62bc58a168417bfb5e859c2a370bab03, 0621c385fda1376e967f37ccd534c26c3e511d14 |
| Linux/Linuxgeneric | 2.6.27 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <fbc72f5c645155dc2ed3573243ed20f9913e3a54 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <5822a05a841a10794ad818620dd2af490b0705d3 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <754ff1bea3819a90c6f33cccfc1a299ef7609f07 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <131ea3e57fc22936ed0e2c8330f2e36106172f51 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <79f84af38c9fef9deb0e02c79eb969b5541c2644 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <6561afc38398e3518a29c5eebb975c30468f98a6 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <817f16ed62bc58a168417bfb5e859c2a370bab03 || >=a3ab7155ea21aadc8a4d5687e91b3d876973185e <0621c385fda1376e967f37ccd534c26c3e511d14 | fbc72f5c645155dc2ed3573243ed20f9913e3a54, 5822a05a841a10794ad818620dd2af490b0705d3, 754ff1bea3819a90c6f33cccfc1a299ef7609f07, 131ea3e57fc22936ed0e2c8330f2e36106172f51, 79f84af38c9fef9deb0e02c79eb969b5541c2644, 6561afc38398e3518a29c5eebb975c30468f98a6, 817f16ed62bc58a168417bfb5e859c2a370bab03, 0621c385fda1376e967f37ccd534c26c3e511d14 |
| Linux/Linuxgeneric | 2.6.27 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.