CVE-2026-99786: Linux kernel · xfrm: retry inexact policy lookup after node reinsertion
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f10bd6c317cef7aa15e185e514513e8548f9ce77 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:07 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f10bd6c317cef7aa15e185e514513e8548f9ce77, 868f63c8bfafa9b827168c9126f85264c39c02ec, 50d8f2c52093320c70676e9f8af686ff6740abd0 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 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 19 Nov 2026.
What to do
Upgrade Linux kernel to f10bd6c317cef7aa15e185e514513e8548f9ce77, 868f63c8bfafa9b827168c9126f85264c39c02ec, 50d8f2c52093320c70676e9f8af686ff6740abd0 or 6f66839895b7e9c2673df5bd9dd8d5a82033c825.
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– |
AI-suggested
A fix is available and has been applied in specific Linux kernel commits. Users and administrators should update to a Linux kernel version that includes the fix identified by commits f10bd6c317cef7aa15e185e514513e8548f9ce77, 868f63c8bfafa9b827168c9126f85264c39c02ec, 50d8f2c52093320c70676e9f8af686ff6740abd0, or 6f66839895b7e9c2673df5bd9dd8d5a82033c825. No other mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's xfrm subsystem causes incorrect IPsec policy lookups due to concurrent modifications of inexact policy tree nodes. This can lead to returning incorrect IPsec policy results during lookups. The issue arises from a race condition where a policy insertion merges tree nodes while a lookup is in progress, causing inconsistent views of policy lists. The flaw has been fixed by adding validation and retry logic around the inexact policy tree traversal to ensure consistency.
References
- git.kernel.org/stable/c/f10bd6c317cef7aa15e185e514513e8548f9ce77 (opens in a new tab)
- git.kernel.org/stable/c/6f66839895b7e9c2673df5bd9dd8d5a82033c825 (opens in a new tab)
- git.kernel.org/stable/c/50d8f2c52093320c70676e9f8af686ff6740abd0 (opens in a new tab)
- git.kernel.org/stable/c/868f63c8bfafa9b827168c9126f85264c39c02ec (opens in a new tab)