CVE-2026-99288: inet: reject unhashed sockets during established lookups
Fixed in Debian 12/13 · Affected: Linux · Exploitation: not established
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.13 (13 Nov)
- In CISA KEV: not seen
- Exploited (reported): not seen
- Scanning observed: not seen
- Proof of concept public: not seen
- Not establishedNothing in the sources we check
Higher than 4% of scored CVEs
Not scored yet. NVD has not published a CVSS score.
DescriptionNVD
In the Linux kernel, the following vulnerability has been resolved: inet: reject unhashed sockets during established lookups TCP established ehash lookups are lockless. The socket caches involved use SLAB_TYPESAFE_BY_RCU, so memory can be reused before an RCU reader that retained its old address has finished. After a tuple match, __inet_lookup_established() and __inet6_lookup_established() acquire a reference and repeat the tuple check. They do not check whether the new object is hashed. If the address is reused for a socket with the same tuple, the lookup can acquire a reference to the new object and return it while its nulls node is unhashed. A PoC that drives reuse with a SYN cookie request socket reproduced the crash. The new request socket is unhashed and has a NULL rsk_listener. A lookup that had loaded the address of the old request socket acquired the reference published by tcp_get_cookie_sock() and returned the new object. tcp_v4_rcv() then read sk_state through the NULL listener. The resulting crash was: BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page ... Oops: Oops: 0000 [#1] SMP NOPTI CPU: 4 UID: 0 PID: 0 Comm: swapper/4 Not tainted 7.3.0-00591-g0e135910deec #1 PREEMPT(lazy) ... RIP: 0010:tcp_v4_rcv+0x44e/0x1280 ... R10: 0000000000000001 R11: 00000000024ca8c0 R12: 0000000000000000 ... CR2: 0000000000000012 CR3: 0000000103d50004 CR4: 0000000000770ef0 ... Call Trace: <IRQ> ? raw_local_deliver+0xae/0x240 ip_protocol_deliver_rcu+0x2d/0x180 ip_local_deliver_finish+0x84/0x100 ip_sublist_rcv_finish+0x5f/0x70 ip_sublist_rcv+0x12a/0x1d0 ip_list_rcv+0xfd/0x130 __netif_receive_skb_list_core+0x223/0x250 netif_receive_skb_list_internal+0x1d2/0x2c0 ?
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Linux
- Published
- November 2026
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- Red Hat Enterprise Linux 10Affected, no fix releasedchecked 16 Nov 03:30 UTC
- Red Hat Enterprise Linux 9Affected, no fix releasedchecked 16 Nov 03:30 UTC
- Red Hat Enterprise Linux 8Affected, no fix releasedchecked 16 Nov 03:30 UTC
- Ubuntu 26.04Under investigationchecked 16 Nov 03:30 UTC
- Ubuntu 24.04Under investigationchecked 16 Nov 03:30 UTC
- Ubuntu 22.04Under investigationchecked 16 Nov 03:30 UTC
- Debian 13Fixed in linux 6.12.117-1 (DSA-6628-1)checked 16 Nov 03:30 UTC
- Debian 12Fixed in linux 6.1.192-1 (DLA-4906-1)checked 16 Nov 03:30 UTC
What changed
Debian status tracked since 16 Nov 2026. Red Hat status tracked since 16 Nov 2026. Ubuntu status tracked since 16 Nov 2026.
- Seen in Debian’s tracker on 16 Nov: Debian 12 fixed in linux 6.1.192-1 (DLA-4906-1) Debian
- Seen in Debian’s tracker on 16 Nov: Debian 13 fixed in linux 6.12.117-1 (DSA-6628-1) Debian
- Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 6 as not affected Red Hat
- Red Hat’s tracker lists RHEL 7 as not affected Red Hat
- Red Hat’s tracker lists RHEL 8 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
- Ubuntu’s tracker lists Ubuntu 16.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 18.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 20.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 22.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 24.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 26.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu stonking as under investigation Ubuntu
Coverage1 article · 1 outlet
First in our coverage: SecurityOnline, 16 Nov.
- Linux Kernel Flaw Enables Pre-Login Remote Server CrashesSecurityOnline · first in our coverage
New articles also arrive in the RSS feed.