CVE-2025-38112: Linux kernel · net: Fix TOCTOU issue in sk_is_readable()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ff55c85a923e043d59d26b20a673a1b4a219c310 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- 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-05.
- Patch
- Available – fixed in ff55c85a923e043d59d26b20a673a1b4a219c310, c2b26638476baee154920bb587fc94ff1bf04336, 8926a7ef1977a832dd6bf702f1a99303dbf15b15 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2025
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 5 Nov 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
|
Description
In the Linux kernel, the following vulnerability has been resolved: net: Fix TOCTOU issue in sk_is_readable() sk->sk_prot->sock_is_readable is a valid function pointer when sk resides in a sockmap. After the last sk_psock_put() (which usually happens when socket is removed from sockmap), sk->sk_prot gets restored and sk->sk_prot->sock_is_readable becomes NULL. This makes sk_is_readable() racy, if the value of sk->sk_prot is reloaded after the initial check. Which in turn may lead to a null pointer dereference. Ensure the function pointer does not turn NULL after the check.
References
- git.kernel.org/stable/c/c2b26638476baee154920bb587fc94ff1bf04336 (opens in a new tab)
- git.kernel.org/stable/c/6fa68d7eab34d448a61aa24ea31e68b3231ed20d (opens in a new tab)
- git.kernel.org/stable/c/8926a7ef1977a832dd6bf702f1a99303dbf15b15 (opens in a new tab)
- git.kernel.org/stable/c/ff55c85a923e043d59d26b20a673a1b4a219c310 (opens in a new tab)
- git.kernel.org/stable/c/1e0de7582ceccbdbb227d4e0ddf65732f92526da (opens in a new tab)
- git.kernel.org/stable/c/1b367ba2f94251822577daed031d6b9a9e11ba91 (opens in a new tab)
- git.kernel.org/stable/c/2660a544fdc0940bba15f70508a46cf9a6491230 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html (opens in a new tab)