CVE-2026-53311

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

fuse: fix uninit-value in fuse_dentry_revalidate()

fuse_dentry_revalidate() may be called with a dentry that didn't had ->d_time initialised. The issue was found with KMSAN, where lookup_open() calls __d_alloc(), followed by d_revalidate(), as shown below:

===================================================== BUG: KMSAN: uninit-value in fuse_dentry_revalidate+0x150/0x13d0 fs/fuse/dir.c:394 fuse_dentry_revalidate+0x150/0x13d0 fs/fuse/dir.c:394 d_revalidate fs/namei.c:1030 [inline] lookup_open fs/namei.c:4405 [inline] open_last_lookups fs/namei.c:4583 [inline] path_openat+0x1614/0x64c0 fs/namei.c:4827 do_file_open+0x2aa/0x680 fs/namei.c:4859 [...]

Uninit was created at: slab_post_alloc_hook mm/slub.c:4466 [inline] slab_alloc_node mm/slub.c:4788 [inline] kmem_cache_alloc_lru_noprof+0x382/0x1280 mm/slub.c:4807 __d_alloc+0x55/0xa00 fs/dcache.c:1740 d_alloc_parallel+0x99/0x2740 fs/dcache.c:2604 lookup_open fs/namei.c:4398 [inline] open_last_lookups fs/namei.c:4583 [inline] path_openat+0x135f/0x64c0 fs/namei.c:4827 do_file_open+0x2aa/0x680 fs/namei.c:4859 [...] =====================================================

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
Patch available.
generic

fuse: fix uninit-value in fuse_dentry_revalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse: fix uninit-value in fuse_dentry_revalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a6baf204610589f8a5b5a1cd69d1fe661d9d3cd
generic

fuse: fix uninit-value in fuse_dentry_revalidate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ac9117ba3deab8a5dd22847355f861686f4bee7

Vendor Advisories for CVE-2026-53311(1)

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

Patch Availability(10)

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

All Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53311?
CVE-2026-53311 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse: fix uninit-value in fusedentryrevalidate() fusedentryrevalidate() may be called with a dentry that didn't had ->dtime initialised. The issue was found with KMSAN, where lookupopen() calls dalloc(), followed by drevalidate(),…
When was CVE-2026-53311 disclosed?
CVE-2026-53311 was first published on June 26, 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-53311 actively exploited?
CVE-2026-53311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53311?
CVE-2026-53311 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53311?
A fix for CVE-2026-53311 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53311 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53311

Explore →

Is Your Infrastructure Affected by CVE-2026-53311?

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