CVE-2026-53130

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
3.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 6, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fbc72f5c645155dc2ed3573243ed20f9913e3a54
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/817f16ed62bc58a168417bfb5e859c2a370bab03
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79f84af38c9fef9deb0e02c79eb969b5541c2644
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/754ff1bea3819a90c6f33cccfc1a299ef7609f07
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6561afc38398e3518a29c5eebb975c30468f98a6
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5822a05a841a10794ad818620dd2af490b0705d3
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/131ea3e57fc22936ed0e2c8330f2e36106172f51
generic

fs/omfs: reject s_sys_blocksize smaller than OMFS_DIR_START - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0621c385fda1376e967f37ccd534c26c3e511d14

Vendor Advisories for CVE-2026-53130(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:19 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 04:18 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 15:09 UTCGHSA enrichment
  13. 2026-07-16 02:00 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 12:51 UTCGHSA enrichment
  17. 2026-07-14 23:41 UTCGHSA enrichment
  18. 2026-07-14 10:24 UTCGHSA enrichment
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 21:15 UTCGHSA enrichment
  21. 2026-07-13 08:05 UTCGHSA enrichment
  22. 2026-07-12 18:53 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 05:44 UTCGHSA enrichment
  25. 2026-07-11 16:35 UTCGHSA enrichment
Show 46 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 03:26 UTCGHSA enrichment
  4. 2026-07-10 14:17 UTCGHSA enrichment
  5. 2026-07-10 00:56 UTCGHSA enrichment
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 11:39 UTCGHSA enrichment
  9. 2026-07-08 22:24 UTCGHSA enrichment
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 09:14 UTCGHSA enrichment
  13. 2026-07-07 20:05 UTCGHSA enrichment
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 06:56 UTCGHSA enrichment
  17. 2026-07-06 17:44 UTCGHSA enrichment
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 04:34 UTCGHSA enrichment
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 15:22 UTCGHSA enrichment
  24. 2026-07-05 02:12 UTCGHSA enrichment
  25. 2026-07-04 13:02 UTCGHSA enrichment
  26. 2026-07-04 06:31 UTCEPSS rescore
  27. 2026-07-04 06:31 UTCEPSS rescore
  28. 2026-07-03 23:52 UTCGHSA enrichment
  29. 2026-07-03 10:43 UTCGHSA enrichment
  30. 2026-07-02 21:29 UTCGHSA enrichment
  31. 2026-07-02 08:19 UTCGHSA enrichment
  32. 2026-07-01 19:10 UTCGHSA enrichment
  33. 2026-07-01 06:01 UTCEG score recompute▲ 7.80
  34. 2026-07-01 06:01 UTCGHSA enrichment
  35. 2026-06-30 23:22 UTCEPSS rescore
  36. 2026-06-29 14:06 UTCEPSS rescore
  37. 2026-06-29 14:06 UTCEPSS rescore
  38. 2026-06-28 14:07 UTCEPSS rescore
  39. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  40. 2026-06-28 04:56 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-28 00:04 UTCGHSA enrichment
  43. 2026-06-27 03:08 UTCEPSS rescore
  44. 2026-06-25 13:49 UTCEPSS rescore
  45. 2026-06-24 18:07 UTCEG score recompute
  46. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53130?
CVE-2026-53130 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/omfs: reject ssysblocksize smaller than OMFSDIRSTART omfsfillsuper() rejects oversized ssysblocksize values (> PAGE_SIZE), but it does not reject values smaller than OMFSDIRSTART (0x1b8 = 440). Later, omfsmakeempty() uses…
When was CVE-2026-53130 disclosed?
CVE-2026-53130 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53130 actively exploited?
CVE-2026-53130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53130?
CVE-2026-53130 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53130, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53130

Explore →

Is Your Infrastructure Affected by CVE-2026-53130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs