CVE-2026-99767: Linux kernel · xfrm4: use a full socket for local errors
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e465b8f50337d0fb3b9753be6cb9fcac79800046 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:19 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 e465b8f50337d0fb3b9753be6cb9fcac79800046, 21ba931b2eec642b1c440e0b6eccc2d80f945060, 5def91015ba7b59de62a81384572da7281b8a033
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 e465b8f50337d0fb3b9753be6cb9fcac79800046, 21ba931b2eec642b1c440e0b6eccc2d80f945060 or 5def91015ba7b59de62a81384572da7281b8a033.
Affected software
| Product | 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 e465b8f50337d0fb3b9753be6cb9fcac79800046, 21ba931b2eec642b1c440e0b6eccc2d80f945060, and 5def91015ba7b59de62a81384572da7281b8a033. Users and administrators should update affected Linux kernel versions to these fixed versions or later to remediate this vulnerability.
Description
A vulnerability in the Linux kernel's xfrm4 component involves improper handling of socket types during local error processing. Specifically, the function xfrm4_local_error() uses skb->sk without ensuring it is a full socket, leading to potential out-of-bounds reads when processing TCP SYN-ACK packets owned by request sockets. This flaw was fixed by resolving the socket owner to a full socket before accessing socket state or reporting errors.