CVE-2026-43007accel/qaic: Handle DBC deactivation if the owner went away
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 10 days later
· 10 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 129776ac2e38231fa9c02ce20e116c99de291666 – < 2dd67966f39a2abf8ccb4865031c722e40e01b7f
- affected 129776ac2e38231fa9c02ce20e116c99de291666 – < 08021f2d4a557d6491e3bcc288e96425f50aa3cf
- affected 129776ac2e38231fa9c02ce20e116c99de291666 – < f403094d9075d7c565a3d81002b781c325cb3c07
- affected 129776ac2e38231fa9c02ce20e116c99de291666 – < ee0180e77e6c8482644569632065411de844c515
- affected 129776ac2e38231fa9c02ce20e116c99de291666 – < 2feec5ae5df785658924ab6bd91280dc3926507c
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.134 – ≤ 6.6.*
- unaffected 6.12.81 – ≤ 6.12.*
- unaffected 6.18.22 – ≤ 6.18.*
- unaffected 6.19.12 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References5
- https://git.kernel.org/stable/c/2dd67966f39a2abf8ccb4865031c722e40e01b7f (opens in a new tab)
- https://git.kernel.org/stable/c/08021f2d4a557d6491e3bcc288e96425f50aa3cf (opens in a new tab)
- https://git.kernel.org/stable/c/f403094d9075d7c565a3d81002b781c325cb3c07 (opens in a new tab)
- https://git.kernel.org/stable/c/ee0180e77e6c8482644569632065411de844c515 (opens in a new tab)
- https://git.kernel.org/stable/c/2feec5ae5df785658924ab6bd91280dc3926507c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-26606 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43007)Record last updated .