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.

Score
CVSS 3.1 7.5 High
Status
Received - 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Published
2026-11-10
Last modified
2026-11-20
Weaknesses
CWE-362

Affected products

References


Your early warning system for new security vulnerabilities


Open BETA

Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?

Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?

As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.

100+ new CVEs per day

Most CVEs are irrelevant to your infrastructure

Time-to-exploit < 5 days

Attackers are exploiting vulnerabilities faster than ever before

Manual research is time-consuming

Vendor websites, RSS feeds, and blogs need to be searched daily

Vulnerability scanners are lagging behind

Plugin development isn't progressing fast enough to identify risks in a timely manner

CVE Alarm provides you with immediate notifications of relevant security vulnerabilities

CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.

Real-time notification

Direct email notification without delay

Product-based filters

Only CVEs that actually affect your infrastructure

Custom criteria

Filter by CVSS-Score, exposure, products, and vendors

Team-oriented & multi-tenant capable

Assign products or alerts to specific teams or customers

More time to act

Administrators can review and install updates faster

Time savings

No more manually reviewing the flood of new CVE information

Three steps for better patch planning

With CVE Alarm you will easily receive relevant security alerts for your infrastructure.

Subscribe To
Products

Select the IT products you use. From Apache to VMware – all critical assets are monitored.

Define
Criteria

Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.

Get
Notified

Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.

Be faster
than the attackers

With CVE information, you have more time for patch planning and can close security gaps before they are exploited.

Designed for the target group companies and service providers

Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.

Companies with their own IT infrastructure

Medium-sized to large companies that need to proactively monitor their vulnerabilities

Administrators

IT professionals responsible for infrastructure security and maintenance

Security teams and cybersecurity experts

Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures

Chief Information Security Officers (CISOs) & IT managers

Decision-makers who need an overview of critical vulnerabilities

Security service providers

Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs

From experience to innovation. About us and CVE Alarm.

CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.

AVABIS GmbH – Who are we?
We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.

CVE Alarm – How did the idea come about?
In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.

This made us realize that the real problem is not a lack of information, but rather an overabundance of it.

This led to the idea of ​​developing a product that enables companies to manage this information overload and maintain control over their IT security.

Developed and operated in Germany
Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.

Get in contact with our team

Do you have questions about CVE Alarm or would you like a personal consultation?
We're happy to help.

Please use our contact form.