CVE-2026-64148

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

pds_core: fix error handling in pdsc_devcmd_wait

Fix two cases where pdsc_devcmd_wait() returns stale success from the completion register instead of an error:

  • FW crash: If firmware stops running, the wait loop breaks early with
running=false. The condition "if ((!done || timeout) && running)" is false, so error handling is bypassed and stale status is returned. Check !running first and return -ENXIO.
  • Timeout: If a command times out, err is set to -ETIMEDOUT but then
overwritten by pdsc_err_to_errno(status) which reads stale status. Return -ETIMEDOUT immediately after cleaning up.

Both errors now propagate to pdsc_devcmd_locked() which queues health_work for recovery.

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

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (5)

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

pds_core: fix error handling in pdsc_devcmd_wait - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/784dd2bdc622ed3cc6ef8e113aa1852e252de36f
generic

pds_core: fix error handling in pdsc_devcmd_wait - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/560d559324169fe0583d54c475b5329550a86f71
generic

pds_core: fix error handling in pdsc_devcmd_wait - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3231aff8ab26111c54e630b1a200fc43a729dd14
generic

pds_core: fix error handling in pdsc_devcmd_wait - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2
generic

pds_core: fix error handling in pdsc_devcmd_wait - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e46b6635b03d29807f810c3b415c4755a3f958d

Vendor Advisories for CVE-2026-64148(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-27ubuntu

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)

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 37× in last 7d / 166× 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 199 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64148?
CVE-2026-64148 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: pdscore: fix error handling in pdscdevcmd_wait Fix two cases where pdscdevcmdwait() returns stale success from the completion register instead of an error: 1. FW crash: If firmware stops running, the wait loop breaks early with…
When was CVE-2026-64148 disclosed?
CVE-2026-64148 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-64148 actively exploited?
CVE-2026-64148 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 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64148?
CVE-2026-64148 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64148?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64148, 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-64148

Explore →

Is Your Infrastructure Affected by CVE-2026-64148?

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

Start Free Scan →Browse All CVEs