Skip to content
nulltapE-reader edition

← All e-reader articles

3 min read

Linux TCP Flaw Exposes Servers to Kernel Memory Corruption

A Linux IPv4 TCP race can corrupt kernel memory. Apply the vendor-fixed kernel; compare the booted kernel version from `uname -r` with the vendor’s `CVE-2026-98432` notice.

Read on the standard site

Network port and exposed circuit board inside a rack server, with a brief orange signal crossing the card.

A listening Linux server can run into a kernel use-after-free while handling IPv4 TCP options during a connection handshake. The Linux CVE record describes CVE-2026-98432 as a race between a retransmitted SYN and the lifetime of options shared by a request socket and a child socket. Prioritize IPv4 TCP listeners reachable by untrusted peers; the record rates the flaw 9.8 and describes possible kernel memory disclosure, corruption and crashes.

Fortinet’s advisory, updated November 7 with virtual-patch package information, rates the potential impact as unauthorized code execution. Fortinet marks known exploitation “No.” Its assessment of affected Fortinet products remains under investigation, so owners of those appliances should check the product-specific advisory before assigning them an affected build.

Options outlive the socket

A TCP listener keeps a request socket while a connection is being established. In the Linux CVE account, tcp_v4_syn_recv_sock() hands the request’s IPv4 options to a child socket without copying them. Another CPU can build a SYNACK for a retransmitted request and read those same options under an RCU read lock. If the child is freed during that work, inet_sock_destruct() releases its options with kfree(); ip_options_build() can then read freed memory.

The Linux-assigned CVE record describes a second lifetime race during request-socket migration. A cloned request and its original briefly share options; a concurrent reader can still be using them when the clone is freed. The migration path involves net.ipv4.tcp_migrate_req=1 or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program. Disabling that setting alone addresses only the migration path, while the child-socket race remains relevant to IPv4 TCP listeners. IPv6 duplicates options in the first path; the record separately notes an IPv6 CALIPSO migration issue slated for another patch.

The Linux record says, “Use kfree_rcu() in inet_sock_destruct() and tcp_v4_reqsk_destructor() as well.” That change defers release until readers leave their RCU critical sections. Its CVSS scenarios describe a peer-induced race that can expose kernel heap data or corrupt memory.

Match the running kernel to the fix

The Linux affected-version record, also carried by NIST, lists upstream first-fixed releases 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3 for their respective lines. Identify the kernel actually running on IPv4 TCP servers with uname -r, then map that distribution build to its vendor’s fix or backport for CVE-2026-98432. Install the corrected kernel and boot it; after the maintenance window, compare uname -r with the vendor’s fixed build. A distribution’s version string can differ from upstream even when the fix was backported.

Inventory reachable IPv4 TCP listeners on those hosts and limit unnecessary network reachability to them while updates are scheduled. Review whether request migration is enabled with sysctl net.ipv4.tcp_migrate_req and whether reuseport migration programs are attached to identify hosts with the additional migration race. Fortinet names virtual patch Linux.Kernel.tcp_v4_syn_recv_sock.Use.After.Free. in FMWP database update 26.113. Where that control is deployed, verify the installed database update and protection state in the product; it is separate from checking the running Linux kernel.

Confirm the patched kernel is running

For exposed Linux listeners, schedule the vendor-supplied kernel fix. After boot, run uname -r and record the running build beside the vendor’s fixed build for CVE-2026-98432. Restrict unneeded IPv4 TCP listener access in the meantime. A confirmed fixed booted kernel addresses both described IPv4 lifetimes; a migration sysctl change covers only one. Fortinet product owners should follow the ongoing product-impact assessment and check FMWP update 26.113 where its virtual patch applies.

Record the kernel version output from uname -r, the vendor’s fixed-build notice and the firewall rule or service-listener setting that limits IPv4 TCP access. Confirm the intended listener access rule is still in force after reboot.

Primary sources