CVE-2026-53174

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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(medium)
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 PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 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(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

All Vendor Advisories

(8)

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 5× in last 7d / 83× 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.

Showing the most recent 100 of 278 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-30 19:41 UTCEG score recompute
  10. 2026-08-30 19:41 UTCVendor advisory
  11. 2026-08-30 19:41 UTCGHSA enrichment
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 02:54 UTCEG score recompute
  16. 2026-08-28 02:54 UTCVendor advisory
  17. 2026-08-28 02:54 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 00:20 UTCEG score recompute
  22. 2026-08-25 00:20 UTCVendor advisory
  23. 2026-08-25 00:20 UTCGHSA enrichment
  24. 2026-08-24 13:16 UTCEG score recompute
  25. 2026-08-24 13:16 UTCVendor advisory
Show 75 more
  1. 2026-08-24 13:15 UTCGHSA enrichment
  2. 2026-08-23 20:41 UTCVendor advisory
  3. 2026-08-23 20:41 UTCGHSA enrichment
  4. 2026-08-23 09:37 UTCEG score recompute
  5. 2026-08-23 09:37 UTCVendor advisory
  6. 2026-08-23 09:37 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 22:31 UTCVendor advisory
  9. 2026-08-22 22:31 UTCGHSA enrichment
  10. 2026-08-22 10:47 UTCVendor advisory
  11. 2026-08-22 10:47 UTCGHSA enrichment
  12. 2026-08-21 17:26 UTCVendor advisory
  13. 2026-08-21 17:26 UTCGHSA enrichment
  14. 2026-08-21 05:20 UTCEG score recompute
  15. 2026-08-21 05:20 UTCVendor advisory
  16. 2026-08-21 05:20 UTCGHSA enrichment
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 18:15 UTCVendor advisory
  19. 2026-08-20 18:15 UTCGHSA enrichment
  20. 2026-08-20 07:10 UTCEG score recompute
  21. 2026-08-20 07:10 UTCVendor advisory
  22. 2026-08-20 07:10 UTCGHSA enrichment
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 12:40 UTCVendor advisory
  25. 2026-08-19 12:40 UTCGHSA enrichment
  26. 2026-08-19 01:33 UTCEG score recompute
  27. 2026-08-19 01:33 UTCVendor advisory
  28. 2026-08-19 01:33 UTCGHSA enrichment
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-17 06:11 UTCVendor advisory
  32. 2026-08-17 06:11 UTCGHSA enrichment
  33. 2026-08-16 18:27 UTCEG score recompute
  34. 2026-08-16 18:27 UTCVendor advisory
  35. 2026-08-16 18:27 UTCGHSA enrichment
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 06:45 UTCEG score recompute
  38. 2026-08-16 06:45 UTCVendor advisory
  39. 2026-08-16 06:45 UTCGHSA enrichment
  40. 2026-08-16 02:14 UTCEPSS rescore
  41. 2026-08-15 19:41 UTCVendor advisory
  42. 2026-08-15 19:41 UTCGHSA enrichment
  43. 2026-08-15 08:35 UTCEG score recompute
  44. 2026-08-15 08:35 UTCVendor advisory
  45. 2026-08-15 08:35 UTCGHSA enrichment
  46. 2026-08-15 01:30 UTCEPSS rescore
  47. 2026-08-14 21:00 UTCVendor advisory
  48. 2026-08-14 21:00 UTCGHSA enrichment
  49. 2026-08-14 09:56 UTCVendor advisory
  50. 2026-08-14 09:56 UTCGHSA enrichment
  51. 2026-08-13 22:52 UTCEG score recompute
  52. 2026-08-13 22:52 UTCVendor advisory
  53. 2026-08-13 22:51 UTCGHSA enrichment
  54. 2026-08-13 22:00 UTCEPSS rescore
  55. 2026-08-13 11:46 UTCGHSA enrichment
  56. 2026-08-13 00:38 UTCEG score recompute
  57. 2026-08-13 00:38 UTCVendor advisory
  58. 2026-08-13 00:38 UTCGHSA enrichment
  59. 2026-08-12 13:51 UTCEPSS rescore
  60. 2026-08-12 13:34 UTCVendor advisory
  61. 2026-08-12 13:34 UTCGHSA enrichment
  62. 2026-08-12 02:29 UTCVendor advisory
  63. 2026-08-12 02:29 UTCGHSA enrichment
  64. 2026-08-11 15:25 UTCEG score recompute
  65. 2026-08-11 15:25 UTCVendor advisory
  66. 2026-08-11 15:25 UTCGHSA enrichment
  67. 2026-08-11 04:20 UTCVendor advisory
  68. 2026-08-11 04:20 UTCGHSA enrichment
  69. 2026-08-10 17:16 UTCVendor advisory
  70. 2026-08-10 17:16 UTCGHSA enrichment
  71. 2026-08-10 04:40 UTCVendor advisory
  72. 2026-08-10 04:40 UTCGHSA enrichment
  73. 2026-08-09 17:35 UTCVendor advisory
  74. 2026-08-09 17:35 UTCGHSA enrichment
  75. 2026-08-09 06:31 UTCVendor advisory

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53174?
CVE-2026-53174 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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