CVE-2026-64147

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

pds_core: fix debugfs_lookup dentry leak and error handling

debugfs_lookup() returns a dentry with an elevated reference count that must be released with dput(). The current code discards the returned dentry without calling dput(), causing a reference leak on every firmware reset recovery.

Additionally, when CONFIG_DEBUG_FS is disabled, debugfs_lookup() returns ERR_PTR(-ENODEV), not NULL. The current check passes for error pointers and would call dput() on an invalid pointer, causing a crash.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

pds_core: fix debugfs_lookup dentry leak and error handling - kernel/git/stable/linux.git - Linux kernel stable tree

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

pds_core: fix debugfs_lookup dentry leak and error handling - kernel/git/stable/linux.git - Linux kernel stable tree

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

pds_core: fix debugfs_lookup dentry leak and error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91d13e92b983e6c6d7631012c2e20ae8057de9f2
generic

pds_core: fix debugfs_lookup dentry leak and error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60ef1675b652e912f3eb064767af4432393291fd
generic

pds_core: fix debugfs_lookup dentry leak and error handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26e19622c485e53c3fdb299e822068a0542ddf0c

Vendor Advisories for CVE-2026-64147(1)

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

Patch Availability(5)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

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

All Vendor Advisories

(5)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-64147?
CVE-2026-64147 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: pdscore: fix debugfslookup dentry leak and error handling debugfs_lookup() returns a dentry with an elevated reference count that must be released with dput(). The current code discards the returned dentry without calling dput(),…
When was CVE-2026-64147 disclosed?
CVE-2026-64147 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64147 actively exploited?
CVE-2026-64147 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64147?
CVE-2026-64147 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64147, 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-64147

Explore →

Is Your Infrastructure Affected by CVE-2026-64147?

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