External risk intelligence

Linux kernel flaw can let attackers crash systems or take control

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-23450

An external attacker can exploit a security flaw in the Linux kernel by sending specially timed network requests. This can crash the system and cause a complete outage, disrupting business operations on affected servers.

2Halo Surface Signal

Use After Free

Linux Kernel

5.15.174 to before 5.15.2035.18 to before 6.1.1676.2 to before 6.6.1306.7 to before 6.12.786.13 to before 6.18.206.19 to before 6.19.107.0

External exposure likelihood

Halo Surface Signal score for CVE-2026-23450

The vulnerability lies within the Linux kernel's Shared Memory Communications (SMC) protocol, a specialized networking subsystem designed for high-performance, intra-datacenter RDMA and shared memory traffic. It is network-reachable but typically used in private cluster environments or enterprise mainframes. Public internet-facing exposure is rare and requires specific hardware and configurations.

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability in the Linux kernel could allow an attacker to cause a system crash. The issue arises from how the networking component handles concurrent operations, potentially leading to either a NULL pointer dereference or a use-after-free condition. These problems can halt the system, disrupting services.

  • System crashes affect service availability.
  • The bug is in a networking component.
  • It impacts the Linux kernel.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this NULL dereference and use-after-free vulnerability by triggering a race condition during the TCP connection establishment in the Linux kernel. This allows for a denial of service by causing a kernel panic.

  • Network access required.
  • Targets TCP connection setup.
  • Race condition is the key.

Live Threat

Current exploitation, exposure, and threat context

This Linux kernel vulnerability involves a race condition in the SMC protocol, potentially leading to NULL dereference or use-after-free. While the complexity of the SMC subsystem and its typical deployment in specialized, private environments suggest limited immediate public exploitation, the severity of a kernel crash in a network-facing component cannot be entirely dismissed. Attackers generally prefer vulnerabilities that grant easy remote code execution or widespread access, which this may not directly provide.

  • Exploitation requires specific network configurations.
  • Kernel-level crashes are impactful but complex to weaponize.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize patching Linux kernel versions to fix the NULL dereference and use-after-free in `smc_tcp_syn_recv_sock`. If patching is delayed, investigate traffic using the SMC protocol for signs of exploitation.

  • Patch affected Linux kernels.
  • Monitor SMC protocol traffic for anomalies.
  • Isolate systems using SMC if exploitation is detected.

Frequently asked questions

What is the vulnerability in the Linux kernel related to the net/smc component?

A NULL pointer dereference and use-after-free vulnerability exists in the `smc_tcp_syn_recv_sock()` function within the Linux kernel's net/smc component. This flaw can lead to system instability and crashes.

How does the NULL dereference and use-after-free vulnerability in the Linux kernel occur?

The vulnerability arises from a race condition during the TCP connection establishment where the `smc_sock` can be freed concurrently while still being accessed. This can result in a NULL pointer dereference or a use-after-free error.

What is the impact of the race condition in the Linux kernel's net/smc component?

The race condition can cause a kernel panic, leading to a denial of service. This means the affected system will crash and become unavailable.

What is the relevance of the Linux kernel vulnerability involving `smc_tcp_syn_recv_sock()`?

This vulnerability is relevant because it can be exploited over the network to cause a denial-of-service by crashing the Linux kernel. While typically used in private cluster environments, its network-reachable nature makes it a concern.

What actions should be taken to address the Linux kernel vulnerability?

The primary remediation is to patch affected Linux kernel versions to resolve the NULL dereference and use-after-free issues. Monitoring traffic for the SMC protocol for signs of exploitation is also advised if patching is delayed.

References