CVE Tools

CVE-2026-98432

ipv4: free inet_opt and ireq_opt after an RCU grace period

No known exploitation. EPSS puts it in the 39th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 079096f103faca2dd87342cca6f23d4b34da8871, < b3b027ef0cd322bfa839b9aaf5b27551eea54cf6Upgrade to: b3b027ef0cd322bfa839b9aaf5b27551eea54cf6Affected: ≥ 079096f103faca2dd87342cca6f23d4b34da8871, < 95a8c8fa9f27dce64c40c41c062de7728bf34ab5Upgrade to: 95a8c8fa9f27dce64c40c41c062de7728bf34ab5Affected: ≥ 079096f103faca2dd87342cca6f23d4b34da8871, < 89b5b1eb7d633c33832b7ff2c02e19a144705036Upgrade to: 89b5b1eb7d633c33832b7ff2c02e19a144705036Affected: ≥ 079096f103faca2dd87342cca6f23d4b34da8871, < 742f73df544e03744f2981c467d6542fe8172a2aUpgrade to: 742f73df544e03744f2981c467d6542fe8172a2a + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Ask your IT provider or hosting company whether your servers run a Linux kernel affected by this issue (most Linux-based servers, cloud VMs, and some network appliances use this kernel).
  2. Check whether you manage your own servers directly or rely on a cloud provider/managed hosting — if it's managed, the provider is responsible for patching.
  3. Update to a kernel build that includes the fix (patched commits are already merged upstream; your Linux distribution will issue an update, e.g. via apt upgrade on Debian/Ubuntu or yum update on RHEL-based systems).
  4. Reboot servers after the kernel update is applied, since kernel patches require a restart to take effect.
  5. Confirm with IT that the update was applied across all servers, including backups and failover systems.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

This is a flaw deep inside the Linux operating system's networking code that could in theory let an attacker crash or take over a server, but there's no sign anyone is actually exploiting it yet, so it's worth fixing on your schedule rather than dropping everything.

Use-after-free in the Linux kernel IPv4 stack (tcp_v4_syn_recv_sock / reqsk migration path) where ireq_opt/inet_opt IP options are freed with a plain kfree() while another CPU still reads them under RCU during concurrent SYN-ACK processing, fixed by switching to kfree_rcu().

If you're affected

  • Server crash / downtime
  • Potential full server takeover
  • Operational disruption
  • Data exposure if exploited

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS39th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 39th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained, driven by wide press coverage.

Lifecycle

8 events over 15 days, from the signal feeds we watch.

  1. Record updatedrecord updated
  2. Record updated
  3. OpenVAS check added
  4. Record updated
  5. Publishedrecord updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.