SardinhaNews

CVE-2026-98432

CriticalBDU

Published: 10/15/2026 · Modified: 11/12/2026

CVSS 3.1ⓘ9.8
EPSSⓘ0.8%
VPR (Tenable)8.9

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: free inet_opt and ireq_opt after an RCU grace period tcp_v4_syn_recv_sock() transfers ownership of ireq->ireq_opt to the child socket (newinet->inet_opt) without copying it. Another cpu can concurrently process a retransmitted SYN for the same request socket, and send a SYNACK from tcp_check_req(). tcp_v4_send_synack() and inet_csk_route_req() read ireq->ireq_opt under rcu_read_lock() only, and ip_build_and_send_pkt() and ip_options_build() then read opt->optlen twice. Note that the SYNACK timer itself is not an issue: it holds a reference on its request socket, and inet_csk_reqsk_queue_drop() calls timer_delete_sync() before the child can be freed. Since commit 079096f103fa ("tcp/dccp: install syn_recv requests into ehash table"), request sockets are processed without holding the listener lock, so nothing prevents the child socket from being freed while the SYNACK is still being built. TCP child sockets do not have SOCK_RCU_FREE, and inet_sock_destruct() frees inet_opt with a plain kfree(), leading to a use-after-free in ip_options_build(). A similar issue exists with request socket migration (net.ipv4.tcp_migrate_req=1, or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program). reqsk_timer_handler() clones the request socket with inet_reqsk_clone(), so that the old request socket and its clone share the same ireq_opt, then reqsk_migrate_reset() clears the pointer in the old one. Another cpu holding a reference on the old request socket can still be using these options (sending a SYNACK, or creating a child in tcp_v4_syn_recv_sock()) when the clone is freed, and tcp_v4_reqsk_destructor() also uses a plain kfree(). Readers already use RCU, and other paths replacing inet_opt (do_ip_setsockopt(), cipso_v4_sock_setattr()...) already use kfree_rcu(). Use kfree_rcu() in inet_sock_destruct() and tcp_v4_reqsk_destructor() as well. IPv6 is not affected by the first issue, because tcp_v6_syn_recv_sock() duplicates the options. tcp_v6_reqsk_destructor() has the same migration issue with ipv6_opt, which is only set by CALIPSO. This will be addressed in a separate patch.

Exploitation

No confirmed-exploitation catalog lists this CVE so far.

Requires: network access · Does not require: authentication, user interaction, special target conditions

How it is exploited

Exploitation method

  • The attacker sends TCP traffic over the network to a listening port on the affected Linux kernel, with no credentials required.
  • A retransmitted SYN for the same request socket is processed concurrently on another CPU, causing tcp_check_req() to send a SYNACK.
  • tcp_v4_send_synack() and inet_csk_route_req() read ireq->ireq_opt only under rcu_read_lock(), while the child socket can be freed.
  • inet_sock_destruct() frees inet_opt with a plain kfree(), and ip_options_build() then reads freed memory (use-after-free).
  • The analogous path occurs with request socket migration (net.ipv4.tcp_migrate_req=1 or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program), where the clone and the original share ireq_opt and tcp_v4_reqsk_destructor() also uses a plain kfree().

Am I affected? (applicability)

  • The Linux kernel in use contains the code version prior to the fix listed in the CVE record.
  • The host exposes TCP services to the network (the vector is AV:N, with no privilege or interaction).
  • There is concurrent processing of a retransmitted SYN for the same request socket, a condition required for the use-after-free in ip_options_build().
  • Request socket migration is enabled (net.ipv4.tcp_migrate_req=1) or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program is in use, for the path via tcp_v4_reqsk_destructor().

Does not require: authentication, user interaction, special target conditions.

Mitigation and detection

✓ Fix available in version b3b027ef0cd322bfa839b9aaf5b27551eea54cf6; 95a8c8fa9f27dce64c40c41c062de7728bf34ab5; 89b5b1eb7d633c33832b7ff2c02e19a144705036; 742f73df544e03744f2981c467d6542fe8172a2a

  • Update the kernel to the vendor fix (commits b3b027ef0cd322bfa839b9aaf5b27551eea54cf6, 95a8c8fa9f27dce64c40c41c062de7728bf34ab5, 89b5b1eb7d633c33832b7ff2c02e19a144705036, 742f73df544e03744f2981c467d6542fe8172a2a).
  • If request socket migration is not needed, disable net.ipv4.tcp_migrate_req and avoid BPF_SK_REUSEPORT_SELECT_OR_MIGRATE programs, eliminating the path via tcp_v4_reqsk_destructor().
  • Restrict exposure of TCP services to the network through segmentation and access control, reducing the surface for the remote traffic required to trigger it.

Impact if exploited

Use-after-free in the kernel during SYNACK processing, with potential for memory corruption and code execution in kernel context from the network.

Confidentiality: highIntegrity: highAvailability: high

Community reports (unverified): exploitation 1 · PoC 38

References and technical detail

The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.

Exploitation probability (EPSS) over time

10/18/202610/26/202610/31/202611/01/202611/04/202611/14/2026

Affected products

  • linux · linux_kernel

Weakness type (CWE)

In the news

Timeline on SardinhaNews

References