Quick answers
- Is CVE-2026-98432 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98432 being exploited in the wild.
- How severe is CVE-2026-98432?
- High severity, published 15 October 2026.
- Which products and versions are affected?
- Linux Kernel versions before the fix.
- Is there a fix for CVE-2026-98432?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-98432 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-98432?
- Check whether you run Amazon AWS, Google Cloud Platform or Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in tcp_v4_syn_recv_sock() and related functions where inet_opt and ireq_opt structures are freed without respecting RCU grace periods. Concurrent SYN retransmissions can cause one CPU to free the option structure while another CPU is still reading it in ip_options_build(). The fix involves converting plain kfree() calls to kfree_rcu() in inet_sock_destruct() and tcp_v4_reqsk_destructor() to ensure proper synchronization. The issue affects TCP child socket creation and request socket migration paths.
Affected products
- Linux Linux kernel versions before the fix
Timeline
- 2026-10-15: disclosed