Skip to content
VulniPulse
High 2 vendors · 2 advisories

CVE-2026-99288: inet: reject unhashed sockets during established lookups

CVE-2026-99288 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
7.5 (NetApp), 7.5 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · base score 7.5, scored by LinuxAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: high.
Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
EPSS
0.25% chance of exploitation in the next 30 days (16th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
Vendor advisories
2 from NetApp, Red Hat
Assigned by
Linux (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-99288; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

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.

Text from the CVE.org record (Linux).

How do I fix CVE-2026-99288?

  • ## 1. Disable SYN cookies This blocks the path where a request socket is reconstructed through a SYN cookie. sudo sysctl -w net.ipv4.tcp_syncookies=0 This setting is managed per network namespace. It has to be applied to "each" container that uses a separate network namespace. Disabling it lowers the protection against SYN floods. ## 2. Serialize to a single RX queue This vulnerability requires different RX contexts to race concurrently. Reducing the RX queues of the interface where external packets come in to one and disabling RPS and RFS can block the race. (Red Hat)

Vendor advisories for CVE-2026-99288

NetApp

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-99288] Linux Kernel Vulnerability in NetApp Products

    NTAP-20261118-0006Source published Source updated

    Linux kernel versions 4.4 prior to 6.12.117, 6.18.63, 7.3.4 and 7.4-rc2 are susceptible to a vulnerability which when successfully exploited could allow a remote attacker to trigger a NULL pointer dereference and kernel crash, resulting in a Denial of Service (DoS). Successful exploitation of this vulnerability could lead to disclosure of sensitive information, addition or modification of data or Denial of Service (DoS). Affected products: Active IQ Unified Manager for VMware vSphere, E-Series SANtricity OS Controller Software, NetApp Console Agent OVA, ONTAP Select Deploy administration utility, ONTAP tools for VMware vSphere 10. NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no…

    Affected products in this advisory
    • Active IQ Unified Manager for VMware vSphere
    • E-Series SANtricity OS Controller Software
    • NetApp Console Agent OVA
    • ONTAP Select Deploy administration utility

    1 more entries in the full advisory.

    Source-reported affected versions
    • 6.12.117
    • 6.18.63
    • 7.3.4
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-99288] Denial of Service via race condition in TCP socket lookup

    CVE-2026-99288Source published Source updated

    Denial of Service via race condition in TCP socket lookup. Red Hat rates this important (CVSS 7.5). Weakness: CWE-476. Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat package: kernel-rt.

    Related products — impact not confirmed
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 8
    • Red Hat Enterprise Linux 9
    • Red Hat package: kernel-rt
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    • ## 1. Disable SYN cookies This blocks the path where a request socket is reconstructed through a SYN cookie. sudo sysctl -w net.ipv4.tcp_syncookies=0 This setting is managed per network namespace. It has to be applied to "each" container that uses a separate network namespace. Disabling it lowers the protection against SYN floods. ## 2. Serialize to a single RX queue This vulnerability requires different RX contexts to race concurrently. Reducing the RX queues of the interface where external packets come in to one and disabling RPS and RFS can block the race.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about NetApp