CVE-2026-53130: fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START

Published Jun 24, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

fs/omfs: reject ssysblocksize smaller than OMFSDIRSTART

omfsfillsuper() rejects oversized ssysblocksize values (> PAGESIZE), but it does not reject values smaller than OMFSDIRSTART (0x1b8 = 440).

Later, omfsmakeempty() uses

sbi->ssysblocksize - OMFSDIRSTART

as the length argument to memset(). Since ssysblocksize is u32, a crafted filesystem image with ssysblocksize < OMFSDIRSTART causes an unsigned underflow there, wrapping to a value near 2^32. That drives a ~4 GiB memset() from bh->bdata + OMFSDIRSTART and overwrites kernel memory far beyond the backing block buffer.

Add the corresponding lower-bound check alongside the existing upper-bound check in omfsfillsuper(), so that malformed images are rejected during superblock validation before any filesystem data is processed.

Affected Software

8 affected components
Linux Linux kernel (omfs filesystem)
Linux Linux kernel>=2.6.27<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In omfs_fill_super(), add/ensure a lower-bound check to reject malformed filesystem images where s_sys_blocksize is smaller than OMFS_DIR_START (0x1b8 = 440), in addition to the existing upper-bound check (> PAGE_SIZE), so memset() cannot be driven by an unsigned underflow.

    Linux kernel omfs filesystem (fs/omfs) s_sys_blocksize lower-bound validation in omfs_fill_super() = Reject if s_sys_blocksize < OMFS_DIR_START (0x1b8 = 440)

Event History

Jun 24, 2026
CVE Published
via MITRE·04:30 PM
Data Sourced
via MITRE·04:30 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53130?

CVE-2026-53130 has a risk rating of 80, indicating a high severity level.

2

How do I fix CVE-2026-53130?

To fix CVE-2026-53130, you should apply the latest Linux kernel updates that address the vulnerability.

3

What systems are affected by CVE-2026-53130?

CVE-2026-53130 affects the Linux kernel, specifically instances using the OMFS filesystem.

4

What issue does CVE-2026-53130 address?

CVE-2026-53130 addresses the improper rejection of s_sys_blocksize values smaller than OMFS_DIR_START.

5

When was CVE-2026-53130 published?

CVE-2026-53130 was published on June 24, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203