CVE-2026-98276: net: lock the socket in sock_gettstamp()
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
In the Linux kernel, the following vulnerability has been resolved: net: lock the socket in sock_gettstamp() sk->sk_flags must only be changed while holding the socket lock, because sock_set_flag() and sock_reset_flag() use non atomic operations (__set_bit() and __clear_bit()). sock_gettstamp() is one of the last places where a bit of sk->sk_flags is changed from a syscall without owning the socket lock, through sock_enable_timestamp(sk, SOCK_TIMESTAMP). sk_set_memalloc() and sk_clear_memalloc() also change sk->sk_flags without the socket lock, but their callers (nbd, iscsi_tcp, nvme-tcp, sunrpc, wireguard) need a careful audit, this will be addressed in a separate patch. Jungwoo Lee and Wongi Lee reported an UDP socket use-after-free caused by this bug: a SIOCGSTAMPNS_NEW ioctl racing with bind() can cancel the SOCK_RCU_FREE bit that udp_lib_get_port() just set, because both threads perform a read-modify-write on the same word. CPU 0 (bind) CPU 1 (SIOCGSTAMPNS_NEW) -------------------------------- ---------------------------- read sk_flags = F read sk_flags = F compute F | BIT(SOCK_RCU_FREE) compute F | BIT(SOCK_TIMESTAMP) store F | BIT(SOCK_RCU_FREE) sk_add_node_rcu(sk, ...) store F | BIT(SOCK_TIMESTAMP) After the lost update, SOCK_RCU_FREE is clear while the socket is visible to lockless UDP receive lookups. sk_destruct() then frees the socket immediately instead of waiting for a RCU grace period, while the receive path still holds a reference-less pointer to it: BUG: KASAN: slab-use-after-free in ipv4_pktinfo_prepare+0x30/0x410 Read of size 8 at addr ffff888008806610 by task exploit/207 CPU: 0 UID: 1000 PID: 207 Comm: exploit Not tainted 6.12.95+ #1 ipv4_pktinfo_prepare+0x30/0x410 udp_queue_rcv_one_skb+0x51c/0x1180 udp_unicast_rcv_skb+0x109/0x350 ip_protocol_deliver_rcu+0x14b/0x310 ip_local_deliver_finish+0x29d/0x390 ip_local_deliver+0x24d/0x2a0 Only grab the socket lock when SOCK_TIMESTAMP has to be set, to keep the common case lockless.
Description quoted from the CVE record (assigned by Linux, published 2026-10-06).
How it can be exploited
Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 code repository naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 7 references on Exploit Observer
Live scores
- EPSS
- 0.001
low predicted chance of attack - VEDAS
- 0.971
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Linux | from 1da177e4c3f4 before 18899e2e4023 (git commit) from 1da177e4c3f4 before 88c804847dd8 (git commit) from 1da177e4c3f4 before 3b12d3967e96 (git commit) from 1da177e4c3f4 before 17b2a1eb97fd (git commit) from 1da177e4c3f4 before 1f73253add83 (git commit) from 1da177e4c3f4 before d9f96bc2d822 (git commit) from 1da177e4c3f4 before 899650bbf985 (git commit) from 1da177e4c3f4 before 9ed55f3dbef4 (git commit) | Not stated |
| Linux | version 2.6.12 | 0 is not affected (up to 2.6.12); 5.10.271 is not affected; 5.15.222 is not affected; 6.1.189 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Other references
- https://git.kernel.org/stable/c/18899e2e4023369a8f7739c2255a59a9748d8d17
- https://git.kernel.org/stable/c/88c804847dd87dc613b771b392ccecdb94725032
- https://git.kernel.org/stable/c/3b12d3967e96f1b7b977d9fc352ae29a1b299a82
- https://git.kernel.org/stable/c/17b2a1eb97fdb2a2cbaeab3b146b26797ea9311f
- https://git.kernel.org/stable/c/1f73253add8365d0dad0a4f421acaa8c21d20cef
- https://git.kernel.org/stable/c/d9f96bc2d822501f84d1caa6275a2c6b316ca2c4
- https://git.kernel.org/stable/c/899650bbf985b7bfd2a7b808357df9b16e6d6959
- https://git.kernel.org/stable/c/9ed55f3dbef4f4adfe65eb03b0c35c53229a8490
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners