CVE-2026-64457

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

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

virtio_pci: fix vq info pointer lookup via wrong index

Unbinding a virtio balloon device:

echo virtio0 > /sys/bus/virtio/drivers/virtio_balloon/unbind

triggers a NULL pointer dereference. The dmesg says:

BUG: kernel NULL pointer dereference, address: 0000000000000008 [...] RIP: 0010:__list_del_entry_valid_or_report+0x5/0xf0 Call Trace: vp_del_vqs+0x121/0x230 remove_common+0x135/0x150 virtballoon_remove+0xee/0x100 virtio_dev_remove+0x3b/0x80 device_release_driver_internal+0x187/0x2c0 unbind_store+0xb9/0xe0 kernfs_fop_write_iter.llvm.11660790530567441834+0xf6/0x180 vfs_write+0x2a9/0x3b0 ksys_write+0x5c/0xd0 do_syscall_64+0x54/0x230 entry_SYSCALL_64_after_hwframe+0x29/0x31 [...]

The virtio_balloon device registers 5 queues (inflate, deflate, stats, free_page, reporting) but only the first two are unconditional. The stats, free_page and reporting queues are each conditional on their respective feature bits. When any of these features are absent, the corresponding vqs_info entry has name == NULL, creating holes in the array.

The root cause is an indexing mismatch introduced when vq info storage was changed to be passed as an argument. vp_find_vqs_msix() and vp_find_vqs_intx() store the info pointer at vp_dev->vqs[i], where 'i' is the caller's sparse array index. However, the virtqueue itself gets vq->index assigned from queue_idx, a dense index that skips NULL entries. When holes exist, 'i' and queue_idx diverge. Later, vp_del_vqs() looks up info via vp_dev->vqs[vq->index] using the dense index into the sparsely-populated array, and hits NULL.

Fix this by storing info at vp_dev->vqs[queue_idx] instead of vp_dev->vqs[i], so the store index matches the lookup index (vq->index). Apply the fix to both the MSIX and INTX paths.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-64457(1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-14ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

All Vendor Advisories

(3)

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 6× in last 7d / 36× 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.

  1. 2026-09-14 08:13 UTCVendor advisory
  2. 2026-09-14 08:13 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-11 02:40 UTCVendor advisory
  6. 2026-09-11 02:40 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:12 UTCVendor advisory
  9. 2026-09-07 21:12 UTCGHSA enrichment
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 15:31 UTCEPSS rescore
  13. 2026-09-04 12:38 UTCGHSA enrichment
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 03:36 UTCGHSA enrichment
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:42 UTCEPSS rescore
  22. 2026-08-26 22:08 UTCGHSA enrichment
  23. 2026-08-26 14:47 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-23 16:39 UTCGHSA enrichment
Show 47 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 11:11 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 05:43 UTCGHSA enrichment
  9. 2026-08-17 05:25 UTCNVD update
  10. 2026-08-17 05:16 UTCGHSA enrichment
  11. 2026-08-17 05:05 UTCMITRE cvelistV5
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 11:33 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 06:06 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-08 00:38 UTCGHSA enrichment
  21. 2026-08-06 13:47 UTCEPSS rescore
  22. 2026-08-05 19:17 UTCEPSS rescore
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 19:11 UTCGHSA enrichment
  25. 2026-08-04 15:10 UTCEPSS rescore
  26. 2026-08-04 10:39 UTCEPSS rescore
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 02:27 UTCEPSS rescore
  29. 2026-08-01 13:43 UTCEG score recompute
  30. 2026-08-01 13:43 UTCGHSA enrichment
  31. 2026-08-01 04:16 UTCEPSS rescore
  32. 2026-07-30 16:28 UTCEPSS rescore
  33. 2026-07-30 01:30 UTCEPSS rescore
  34. 2026-07-30 01:30 UTCEPSS rescore
  35. 2026-07-29 08:16 UTCEG score recompute
  36. 2026-07-29 08:15 UTCGHSA enrichment
  37. 2026-07-28 15:37 UTCEPSS rescore
  38. 2026-07-27 14:14 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 02:47 UTCEG score recompute
  42. 2026-07-26 02:47 UTCGHSA enrichment
  43. 2026-07-25 14:18 UTCEPSS rescore
  44. 2026-07-25 14:18 UTCEPSS rescore
  45. 2026-07-25 10:39 UTCNVD update
  46. 2026-07-25 09:26 UTCEG score recompute
  47. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64457?
CVE-2026-64457 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: virtio_pci: fix vq info pointer lookup via wrong index Unbinding a virtio balloon device: echo virtio0 > /sys/bus/virtio/drivers/virtio_balloon/unbind triggers a NULL pointer dereference. The dmesg says: BUG: kernel NULL pointer…
When was CVE-2026-64457 disclosed?
CVE-2026-64457 was first published in the National Vulnerability Database on July 25, 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-64457 actively exploited?
CVE-2026-64457 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 92.8% of all scored CVEs.
How do I remediate CVE-2026-64457?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64457, 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-64457

Explore →

Is Your Infrastructure Affected by CVE-2026-64457?

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