CVE-2026-43007

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

accel/qaic: Handle DBC deactivation if the owner went away

When a DBC is released, the device sends a QAIC_TRANS_DEACTIVATE_FROM_DEV transaction to the host over the QAIC_CONTROL MHI channel. QAIC handles this by calling decode_deactivate() to release the resources allocated for that DBC. Since that handling is done in the qaic_manage_ioctl() context, if the user goes away before receiving and handling the deactivation, the host will be out-of-sync with the DBCs available for use, and the DBC resources will not be freed unless the device is removed. If another user loads and requests to activate a network, then the device assigns the same DBC to that network, QAIC will "indefinitely" wait for dbc->in_use = false, leading the user process to hang.

As a solution to this, handle QAIC_TRANS_DEACTIVATE_FROM_DEV transactions that are received after the user has gone away.

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
3%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (5)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

accel/qaic: Handle DBC deactivation if the owner went away - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/qaic: Handle DBC deactivation if the owner went away - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel/qaic: Handle DBC deactivation if the owner went away - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2feec5ae5df785658924ab6bd91280dc3926507c
generic

accel/qaic: Handle DBC deactivation if the owner went away - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2dd67966f39a2abf8ccb4865031c722e40e01b7f
generic

accel/qaic: Handle DBC deactivation if the owner went away - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08021f2d4a557d6491e3bcc288e96425f50aa3cf

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.6.134—osv

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.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(13)

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 / 28× 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 202 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43007?
CVE-2026-43007 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Handle DBC deactivation if the owner went away When a DBC is released, the device sends a QAICTRANSDEACTIVATEFROMDEV transaction to the host over the QAIC_CONTROL MHI channel. QAIC handles this by calling…
When was CVE-2026-43007 disclosed?
CVE-2026-43007 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43007 actively exploited?
CVE-2026-43007 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43007?
CVE-2026-43007 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43007, 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-43007

Explore →

Is Your Infrastructure Affected by CVE-2026-43007?

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

Start Free Scan →Browse All CVEs