CVE-2026-64251

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-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.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

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:

pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()

pwrseq_debugfs_seq_next() declares 'next' with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped.

Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&pwrseq_sem) and never releases the device reference.

Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI:

  • start(): use get_device() so it returns a referenced pointer.
  • next(): explicitly put_device(curr) to release the previous
device's reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL).
  • stop(): put_device(data) to release the last iterated device's
reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.

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

July 24, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() - kernel/git/stable/linux.git - Linux kernel stable tree

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

pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() - kernel/git/stable/linux.git - Linux kernel stable tree

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

pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73569a44fca2992f0ca4a4c0104069741b9873a0
generic

pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/257595adf9dac15ae1edd9d07753fbc576a7583d

Vendor Advisories for CVE-2026-64251(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (153 versions)7.1.3-1

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-64251?
CVE-2026-64251 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: pwrseq: core: fix use-after-free in pwrseqdebugfsseq_next() pwrseqdebugfsseqnext() declares 'next' with free(putdevice), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This…
When was CVE-2026-64251 disclosed?
CVE-2026-64251 was first published in the National Vulnerability Database on July 24, 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-64251 actively exploited?
CVE-2026-64251 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64251?
CVE-2026-64251 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64251?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64251, 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-64251

Explore →

Is Your Infrastructure Affected by CVE-2026-64251?

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