Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43007: accel/qaic: Handle DBC deactivation if the owner went away

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 08021f2d4a557d6491e3bcc288e96425f50aa3cf, 2dd67966f39a2abf8ccb4865031c722e40e01b7f, 2feec5ae5df785658924ab6bd91280dc3926507c.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 08021f2d4a557d6491e3bcc288e96425f50aa3cf, 2dd67966f39a2abf8ccb4865031c722e40e01b7f, 2feec5ae5df785658924ab6bd91280dc3926507c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 1, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43007

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.4 and later · before 6.6.134
  • linux linux kernel6.7 and later · before 6.12.81
  • linux linux kernel6.13 and later · before 6.18.22
  • linux linux kernel6.19 and later · before 6.19.12
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.4affected
    • 129776ac2e38231fa9c02ce20e116c99de291666 and later · before 2dd67966f39a2abf8ccb4865031c722e40e01b7faffected · git
    • 129776ac2e38231fa9c02ce20e116c99de291666 and later · before 08021f2d4a557d6491e3bcc288e96425f50aa3cfaffected · git
    • 129776ac2e38231fa9c02ce20e116c99de291666 and later · before f403094d9075d7c565a3d81002b781c325cb3c07affected · git
    • 129776ac2e38231fa9c02ce20e116c99de291666 and later · before ee0180e77e6c8482644569632065411de844c515affected · git
    • 129776ac2e38231fa9c02ce20e116c99de291666 and later · before 2feec5ae5df785658924ab6bd91280dc3926507caffected · git
    • before 6.4not affected · semver
    • 6.6.134 and later · up to and including 6.6.*not affected · semver
    • 6.12.81 and later · up to and including 6.12.*not affected · semver
    • 6.18.22 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.12-16.19.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43005May 1, 2026 · hwmon: (tps53679) Fix array access with zero-length block read
    28Monitor
  • ← EarlierCVE-2026-43006May 1, 2026 · io_uring/rsrc: reject zero-length fixed buffer import
    28Monitor
  • Later →CVE-2026-43008May 1, 2026 · gpio: qixis-fpga: Fix error handling for devm_regmap_init_mmio()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08021f2d4a557d6491e3bcc288e96425f50aa3cfVendor (CNA)
Linux Linux2dd67966f39a2abf8ccb4865031c722e40e01b7fVendor (CNA)
Linux Linux2feec5ae5df785658924ab6bd91280dc3926507cVendor (CNA)
Linux Linuxee0180e77e6c8482644569632065411de844c515Vendor (CNA)
Linux Linuxf403094d9075d7c565a3d81002b781c325cb3c07Vendor (CNA)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-430110 days apartnet/x25: Fix potential double free of skb
    39Monitor
  • CVE-2026-316087 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()
    39Monitor
  • CVE-2026-316097 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
    39Monitor
  • CVE-2026-434147 days apartscsi: qla2xxx: Completely fix fcport double free
    39Monitor
  • CVE-2026-5299354 days aparttipc: fix double-free in tipc_buf_append()
    39Monitor
  • CVE-2026-6388879 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()
    39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records