Skip to content

CVE-2026-99288

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 ? try_fill_recv+0x39/0x7b0 napi_complete_done+0x74/0x170 virtnet_poll+0x445/0x600 __napi_poll+0x27/0x1e0 net_rx_action+0x2fe/0x3b0 handle_softirqs+0xc2/0x2c0 __irq_exit_rcu+0x74/0xd0 common_interrupt+0x7f/0x90 </IRQ> ... Kernel panic - not syncing: Fatal exception in interrupt After taking a reference, check whether the nulls node is unhashed in both IPv4 and IPv6 established lookups. If it is unhashed or the tuple no longer matches, drop the reference and restart the lookup. Lookups racing with the TIME_WAIT hashdance, or with a request being replaced by its child, now restart and find the new socket instead of returning the old one. Request sockets that were never inserted into ehash can have a nonzero refcount, and a stale lookup can hold a transient reference. Therefore, when SYN cookie, Fast Open, and request migration paths fail after setting a nonzero refcount, release the references held by those paths with reqsk_put() instead of freeing the request directly.

How scary is it?

updated 21 Nov 2026
  • Not known

    Works without logging in

    No CVSS 3.x or 4.0 vector in the data we hold.

  • Not known

    Reachable over the network

    No CVSS 3.x or 4.0 vector in the data we hold.

  • Yes

    Proof-of-concept code is public1

    5 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Low signal

Not scored yet, and no sign of attacks that we know of.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Linux in an affected version>= 079096f103faca2dd87342cca6f23d4b34da8871 and < d69100340b4cae08d40f898f1b601032403f6be6 / >= 079096f103faca2dd87342cca6f23d4b34da8871 and < 8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd / >= 079096f103faca2dd87342cca6f23d4b34da8871 and < eb8a2d156f2c1d862fffdfd1b3432bfbcd939879 (+2 more)

    >= 079096f103faca2dd87342cca6f23d4b34da8871 and < d69100340b4cae08d40f898f1b601032403f6be6 >= 079096f103faca2dd87342cca6f23d4b34da8871 and < 8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd >= 079096f103faca2dd87342cca6f23d4b34da8871 and < eb8a2d156f2c1d862fffdfd1b3432bfbcd939879 >= 079096f103faca2dd87342cca6f23d4b34da8871 and < 4e2b3ef19e0e04adca38442f07dd6bc93c712bf1 4.4

    Vendor says fixed in: < 4.4, >= 6.12.117 and <= 6.12.*, >= 6.18.63 and <= 6.18.*, >= 7.3.4 and <= 7.3.*, >= 7.4-rc2 and <= *.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 3

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release< 4.4 / >= 6.12.117 and <= 6.12.* / >= 6.18.63 and <= 6.18.* / >= 7.3.4 and <= 7.3.* (+1 more)

    Linux: < 4.4, >= 6.12.117 and <= 6.12.*, >= 6.18.63 and <= 6.18.*, >= 7.3.4 and <= 7.3.*, >= 7.4-rc2 and <= *

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 3

CVSS
Not scored yetNVD has not published a score
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.59%chance of exploitation in the next 30 daystop 51% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in < 4.4, >= 6.12.117 and <= 6.12.*, >= 6.18.63 and <= 6.18.*per the vendor; 2 more listed below
Published
10 Nov 2026analysed here 16 Nov 2026

Do first. Upgrade to a fixed release: < 4.4, >= 6.12.117 and <= 6.12.*, >= 6.18.63 and <= 6.18.*, >= 7.3.4 and <= 7.3.* (and 1 more below).

NVD hasn't published a CVSS score for this CVE yet. Severity and the CVSS vector appear here once it is scored upstream.

Summary

Triage

Can a WAF block it?
Unknown. See why

Executive summary (AI-written)

CVE-2026-99288 is a vulnerability in the Linux kernel that poses a risk of system crashes due to improper handling of socket references during established TCP lookups. When certain conditions are met, this vulnerability can lead to a kernel panic, preventing the affected system from functioning correctly. Organizations utilizing Linux-based systems, especially those relying on TCP networking, should be particularly cautious, as this could lead to service outages or degraded performance, impacting business operations.

Technical analysis (AI-written)

The vulnerability CVE-2026-99288 arises from inconsistencies in the Linux kernel's handling of TCP established lookups. Specifically, during the ehash lookups which are designed to be lockless, the kernel inadvertently allows sockets that have not been hashed to be referenced. This occurs when an old request socket address is reused for a new socket with the same tuple, without validating its hashed status. If this leads to an attempt to dereference a null listener due to a lack of validation, it results in a kernel NULL pointer dereference, triggering a crash. The PoC suggests exploitation via SYN cookie requests can reproduce the crash, demonstrating that this vulnerability can be leveraged under specific network conditions. Attackers could craft scenarios that lead to a system crash, exploiting the kernel’s failure to distinguish between the old and new socket states. This signals that the vulnerability presents a moderate complexity level for exploitation, as it requires articulated synchronization of socket operations in a networking context. Mitigation strategies should focus on code alterations in the functions `__inet_lookup_established()` and `__inet6_lookup_established()`. These should be modified to include checks that confirm whether a socket address is hashed before it is returned, and if any discrepancies are found, the lookup should restart rather than returning stale socket references. Further, during transitions involving SYN cookies or request migration paths, it is critical to manage reference counts accurately to prevent stale lookups that can lead to kernel panics. Technical recommendations involve updating the kernel to appropriately handle these edge-cases where socket references are concerned. Given the kernel's pivotal role in system stability and security, developers must prioritize patching this vulnerability once suitable fixes are made available. Continuous monitoring for updates concerning this CVE is advised, as a patch has not yet been released. Additionally, organizations should implement robust error handling and monitoring systems that log connection anomalies to catch symptoms related to this type of vulnerability early.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
Linux>= 079096f103faca2dd87342cca6f23d4b34da8871 and < d69100340b4cae08d40f898f1b601032403f6be6>= 079096f103faca2dd87342cca6f23d4b34da8871 and < 8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd>= 079096f103faca2dd87342cca6f23d4b34da8871 and < eb8a2d156f2c1d862fffdfd1b3432bfbcd939879>= 079096f103faca2dd87342cca6f23d4b34da8871 and < 4e2b3ef19e0e04adca38442f07dd6bc93c712bf14.4Vendor says fixed in: < 4.4, >= 6.12.117 and <= 6.12.*, >= 6.18.63 and <= 6.18.*, >= 7.3.4 and <= 7.3.*, >= 7.4-rc2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Unknown. The official CVE record has no attack vector yet and its weakness type is not one we classify, so we cannot tell. No tracked WAF vendor has published a rule for this CVE.

Also consider: patch

Based on what is published so far, which is too little to decide. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 5 GitHub proofs of concept

GitHub proofs of concept

and 1 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 10 Nov 2026Published
  2. 16 Nov 2026First proof-of-concept repository on GitHub (unvetted)5 days later
  3. 16 Nov 2026CVE record last updatedsame day later
  4. 16 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-99288 being exploited?

Not confirmed. CVE-2026-99288 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.59% probability of exploitation in the next 30 days.

How severe is CVE-2026-99288?

No severity score has been published for CVE-2026-99288 yet. Since April 2026 the NVD enriches only prioritised CVEs, so an unscored record means nobody has assessed it — not that the flaw is minor. Judge it from the vendor advisory and whether you run the affected software.

Is there a patch for CVE-2026-99288?

Not known from our data. No patch reference has been recorded for CVE-2026-99288, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

5 references in the CVE record, grouped by the tags the record gives them.

Other links (5)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.