VulnerabilityPublished 27 May 2026Updated 6 Nov 2026

CVE-2026-46047: Linux kernel · net: qrtr: ns: Fix use-after-free in driver remove()

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f96779e916576e81430ebb326baff6e433fef8ae : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in f96779e916576e81430ebb326baff6e433fef8ae, dff081c3602f2fd810f69ef47945a226980dd05d, db3c60ec772de30acae92d560dfcc5258e58dbe8 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < f96779e916576e81430ebb326baff6e433fef8ae	Fixed in f96779e916576e81430ebb326baff6e433fef8ae
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < dff081c3602f2fd810f69ef47945a226980dd05d	Fixed in dff081c3602f2fd810f69ef47945a226980dd05d
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < db3c60ec772de30acae92d560dfcc5258e58dbe8	Fixed in db3c60ec772de30acae92d560dfcc5258e58dbe8
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 65168712c216584ff482a7d1a67589f2079b2634	Fixed in 65168712c216584ff482a7d1a67589f2079b2634
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 7809fea20c9404bfcfa6112ec08d1fe1d3520beb	Fixed in 7809fea20c9404bfcfa6112ec08d1fe1d3520beb
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 4ae0bd51bf7079e9c2a06b5de0ae04ba70d10167	Fixed in 4ae0bd51bf7079e9c2a06b5de0ae04ba70d10167

Description

In the Linux kernel, the following vulnerability has been resolved: net: qrtr: ns: Fix use-after-free in driver remove() In the remove callback, if a packet arrives after destroy_workqueue() is called, but before sock_release(), the qrtr_ns_data_ready() callback will try to queue the work, causing use-after-free issue. Fix this issue by saving the default 'sk_data_ready' callback during qrtr_ns_init() and use it to replace the qrtr_ns_data_ready() callback at the start of remove(). This ensures that even if a packet arrives after destroy_workqueue(), the work struct will not be dereferenced. Note that it is also required to ensure that the RX threads are completed before destroying the workqueue, because the threads could be using the qrtr_ns_data_ready() callback.

References

Community reviews

Loading reviews…