CVE-2026-53174

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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

A fix is available — apply it.

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

ovl: keep err zero after successful ovl_cache_get()

ovl_iterate_merged() stores PTR_ERR(cache) in err before checking IS_ERR(cache). On success err holds the truncated cache pointer and can be returned as a bogus non-zero error.

The syzbot reproducer reaches this through overlay-on-overlay readdir:

getdents64 iterate_dir(outer overlay file) ovl_iterate_merged() ovl_cache_get() ovl_dir_read_merged() ovl_dir_read() iterate_dir(inner overlay file) ovl_iterate_merged()

Only compute PTR_ERR(cache) on the error path.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (2)

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

ovl: keep err zero after successful ovl_cache_get() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ovl: keep err zero after successful ovl_cache_get() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1711b6ed6953cee5940ca4c3a6e77f1b3798cee2

Vendor Advisories for CVE-2026-53174(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-06ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 46× in last 7d / 66× 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-07 06:53 UTCEG score recompute
  2. 2026-07-07 06:53 UTCGHSA enrichment
  3. 2026-07-06 19:48 UTCEG score recompute
  4. 2026-07-06 19:48 UTCVendor advisory
  5. 2026-07-06 19:47 UTCGHSA enrichment
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 08:13 UTCEG score recompute
  9. 2026-07-06 08:13 UTCGHSA enrichment
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 21:09 UTCEG score recompute
  13. 2026-07-05 21:09 UTCVendor advisory
  14. 2026-07-05 21:09 UTCGHSA enrichment
  15. 2026-07-05 10:02 UTCEG score recompute
  16. 2026-07-05 10:02 UTCVendor advisory
  17. 2026-07-05 10:02 UTCGHSA enrichment
  18. 2026-07-04 22:56 UTCEG score recompute
  19. 2026-07-04 22:56 UTCVendor advisory
  20. 2026-07-04 22:56 UTCGHSA enrichment
  21. 2026-07-04 11:51 UTCEG score recompute
  22. 2026-07-04 11:51 UTCVendor advisory
  23. 2026-07-04 11:51 UTCGHSA enrichment
  24. 2026-07-04 00:45 UTCEG score recompute
  25. 2026-07-04 00:45 UTCVendor advisory
Show 41 more
  1. 2026-07-04 00:45 UTCGHSA enrichment
  2. 2026-07-03 13:36 UTCEG score recompute
  3. 2026-07-03 13:36 UTCVendor advisory
  4. 2026-07-03 13:35 UTCGHSA enrichment
  5. 2026-07-03 02:30 UTCEG score recompute
  6. 2026-07-03 02:30 UTCVendor advisory
  7. 2026-07-03 02:30 UTCGHSA enrichment
  8. 2026-07-02 15:26 UTCEG score recompute
  9. 2026-07-02 15:26 UTCVendor advisory
  10. 2026-07-02 15:26 UTCGHSA enrichment
  11. 2026-07-02 04:21 UTCEG score recompute
  12. 2026-07-02 04:21 UTCVendor advisory
  13. 2026-07-02 04:21 UTCGHSA enrichment
  14. 2026-07-01 17:16 UTCEG score recompute
  15. 2026-07-01 17:16 UTCVendor advisory
  16. 2026-07-01 17:16 UTCGHSA enrichment
  17. 2026-07-01 06:12 UTCEG score recompute
  18. 2026-07-01 06:12 UTCGHSA enrichment
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 19:06 UTCEG score recompute
  21. 2026-06-30 19:06 UTCGHSA enrichment
  22. 2026-06-30 08:00 UTCEG score recompute
  23. 2026-06-30 08:00 UTCGHSA enrichment
  24. 2026-06-29 20:55 UTCEG score recompute
  25. 2026-06-29 20:55 UTCGHSA enrichment
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-29 14:06 UTCEPSS rescore
  28. 2026-06-29 09:51 UTCEG score recompute
  29. 2026-06-29 09:51 UTCGHSA enrichment
  30. 2026-06-28 22:46 UTCEG score recompute
  31. 2026-06-28 22:46 UTCGHSA enrichment
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 11:41 UTCEG score recompute▲ 7.80
  34. 2026-06-28 11:41 UTCGHSA enrichment
  35. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-27 03:08 UTCEPSS rescore
  39. 2026-06-25 13:49 UTCEPSS rescore
  40. 2026-06-25 10:07 UTCEG score recompute
  41. 2026-06-25 10:07 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53174?
CVE-2026-53174 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ovl: keep err zero after successful ovlcacheget() ovliteratemerged() stores PTR_ERR(cache) in err before checking IS_ERR(cache). On success err holds the truncated cache pointer and can be returned as a bogus non-zero error. The…
When was CVE-2026-53174 disclosed?
CVE-2026-53174 was first published in the National Vulnerability Database on June 25, 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-53174 actively exploited?
CVE-2026-53174 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53174?
CVE-2026-53174 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53174?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53174, 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-53174

Explore →

Is Your Infrastructure Affected by CVE-2026-53174?

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

Start Free Scan →Browse All CVEs