CVE-2026-64438

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.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: 8.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:

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov()

The VF2PF interrupt handler queues PF-side response work that stores a raw pointer to per-VF state (struct adf_accel_vf_info). Currently, adf_disable_sriov() destroys per-VF mutexes and frees vf_info without stopping new VF2PF work or waiting for in-flight workers to complete. A concurrently scheduled or already queued worker can then dereference freed memory.

This manifests as a use-after-free when KASAN is enabled:

BUG: KASAN: null-ptr-deref in mutex_lock+0x76/0xe0 Write of size 8 at addr 0000000000000260 by task kworker/24:2/... Workqueue: qat_pf2vf_resp_wq adf_iov_send_resp [intel_qat] Call Trace: kasan_report+0x119/0x140 mutex_lock+0x76/0xe0 adf_gen4_pfvf_send+0xd4/0x1f0 [intel_qat] adf_recv_and_handle_vf2pf_msg+0x290/0x360 [intel_qat] adf_iov_send_resp+0x8c/0xe0 [intel_qat] process_one_work+0x6ac/0xfd0 worker_thread+0x4dd/0xd30 kthread+0x326/0x410 ret_from_fork+0x33b/0x670

Add a PF-local flag, vf2pf_disabled, that gates work queueing, worker processing, and interrupt re-enabling during teardown. Set this flag atomically with the hardware interrupt mask inside adf_disable_all_vf2pf_interrupts(). After masking, synchronize the AE cluster MSI-X interrupt and flush the PF response workqueue before tearing down per-VF locks and state so all in-flight work completes before vf_info is destroyed.

Introduce adf_enable_all_vf2pf_interrupts() to clear the flag and unmask all VF2PF interrupts under the same lock when SR-IOV is re-enabled. This ensures the software flag and hardware state transition atomically on both the enable and disable paths.

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

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e92b28cd74fa433658efeadf21b9d4b01023d7d
generic

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51144032248cc4ea22917370565650670b8b4e9b
generic

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49cd5ac6de8de39a14ead609bb552d372d5602cd
generic

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/446b4d77599cf1a168573f7fb32a4a6aa4f09219
generic

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/277281c10c63791067d24d421f7c43a15faa9096
generic

crypto: qat - fix VF2PF work teardown race in adf_disable_sriov() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/218c2836b3987f3fa1d9eac505462cded0821e4c

Vendor Advisories for CVE-2026-64438(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1—
linux-6.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-64438?
CVE-2026-64438 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix VF2PF work teardown race in adfdisablesriov() The VF2PF interrupt handler queues PF-side response work that stores a raw pointer to per-VF state (struct adfaccelvf_info). Currently, adfdisablesriov() destroys…
When was CVE-2026-64438 disclosed?
CVE-2026-64438 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-64438 actively exploited?
CVE-2026-64438 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 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64438?
CVE-2026-64438 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64438?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64438, 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-64438

Explore →

Is Your Infrastructure Affected by CVE-2026-64438?

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

Start Free Scan →Browse All CVEs