CVE-2026-43167: Linux kernel · xfrm: always flush state and policy upon NETDEV_UNREGISTER event
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d4df5a7da376e35089b8b601a86ff8a4cf997e2f : update Linux kernel when convenient.
Data as of 30 Oct 2026, 12:49 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in d4df5a7da376e35089b8b601a86ff8a4cf997e2f, a3c8fede034fa27892f87c863cbd5493167d17ed, 59581778792cbaf8ad788f4a21dc663ce986050e +3
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by hashes d4df5a7da376e35089b8b601a86ff8a4cf997e2f, a3c8fede034fa27892f87c863cbd5493167d17ed, 59581778792cbaf8ad788f4a21dc663ce986050e, 166801e49a5b5fc127b8c9e2f110f303cfddfbc3, 8c75c455ecd3bfd2f36abf66edb7021c4fa19ec4, and 4efa91a28576054aae0e6dad9cba8fed8293aef8. Users should update to a fixed kernel version to remediate this issue.
Description
A reference count leak in the Linux kernel's xfrm subsystem was identified and fixed. The issue occurs because the xfrm_dev_unregister() function was implemented as a no-op, failing to release a reference to a network device acquired during xfrm state construction. This leads to a resource leak when the NETDEV_UNREGISTER event is processed. The fix reintroduces proper cleanup by flushing state and policy unconditionally upon device unregistration.
References
- git.kernel.org/stable/c/d4df5a7da376e35089b8b601a86ff8a4cf997e2f (opens in a new tab)
- git.kernel.org/stable/c/166801e49a5b5fc127b8c9e2f110f303cfddfbc3 (opens in a new tab)
- git.kernel.org/stable/c/a3c8fede034fa27892f87c863cbd5493167d17ed (opens in a new tab)
- git.kernel.org/stable/c/59581778792cbaf8ad788f4a21dc663ce986050e (opens in a new tab)
- git.kernel.org/stable/c/8c75c455ecd3bfd2f36abf66edb7021c4fa19ec4 (opens in a new tab)
- git.kernel.org/stable/c/4efa91a28576054aae0e6dad9cba8fed8293aef8 (opens in a new tab)