Article
CVE-2026-98432: Ubuntu Kernel Status and Host Triage
Check CVE-2026-98432 Ubuntu kernel status, separate upstream fixes from package updates, and build a host triage record before closing the patch ticket.
Quick links
Press Enter to search, Esc to close
Vulnerability
A Linux kernel use-after-free in TCP and IPv4 option handling.
In short
CVE-2026-98432 is a Linux kernel use-after-free in TCP and IPv4 option handling. A network peer can reach the affected path before application login. The Linux CNA rates it 9.8 Critical under CVSS 3.1. Ubuntu package status must be checked separately from upstream branch fixes.
CVE-2026-98432 concerns TCP and IPv4 option memory in the Linux kernel. A child socket can own the same option data that another CPU is still reading while it builds a SYNACK. Freeing the child can leave that reader with a stale pointer.
The Linux CNA describes a network peer reaching this path before application authentication. Its CVSS explanation identifies possible kernel memory disclosure, memory corruption, and crashes. The published score describes the flaw's potential impact; it does not prove exploitation in the wild.
A second case involves request-socket migration. Disabling net.ipv4.tcp_migrate_req alone is not a complete fix because the first path does not need migration. The upstream change defers memory freeing until an RCU grace period has passed.
The patch says IPv6 is not affected by the first path because that path copies options. It separately notes a related CALIPSO migration issue for another patch. That distinction must not become a claim that every IPv6 path is safe.
The upstream fix changes inet_sock_destruct() and tcp_v4_reqsk_destructor(). The CVE record names net/ipv4/af_inet.c and net/ipv4/tcp_ipv4.c as affected files. Do not infer host safety from the application version alone; the relevant code runs in the host kernel.
The Linux CNA lists branch-specific fixed versions 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, and 7.3. Read each against its own branch rather than using one number as a universal threshold.
At the October 29, 2026 check, Ubuntu's generic linux source-package rows for 26.10, 26.04 LTS, 24.04 LTS, and 22.04 LTS remained vulnerable with fixes in progress. The listed work targets were 7.3.0-10.10, 7.0.0-43.43, 6.8.0-149.149, and 5.15.0-203.213, respectively. Those are not released-fix claims.
The same source package was marked vulnerable on Ubuntu 20.04, 18.04, and 16.04. Cloud, hardware-enablement, OEM, and real-time kernels have their own rows. Check the exact package and release before deciding its status.
Debian's tracker separately lists linux 6.1.190-1 fixed for bookworm security and 6.12.113-1 fixed for trixie security. Those distribution revisions do not certify an Ubuntu package.
For the current Ubuntu matrix and host checks, use our Ubuntu kernel status and triage report. Our vulnerability management glossary explains how to keep package evidence with the risk record. The patch management entry covers rollout and verification.
This CVE was absent from the fetched CISA KEV catalog dated October 28, checked October 29. Exploitation status remains unknown for this profile; KEV absence is not proof that attacks cannot occur.
Linux CNA publishes CVE-2026-98432.
The Linux CNA record receives its latest recorded update.
Ubuntu records the latest update shown on its CVE entry.
This profile checks Ubuntu package status; selected generic kernel rows still show fixes in progress.
Collect the Ubuntu release, running kernel, and installed kernel-image package. Find the exact kernel flavor in the vendor tracker. A generic kernel row does not cover every cloud or hardware-enablement build.
Distinguish an available fixed package from a vulnerable work-in-progress row. Use supported vendor updates. Do not cherry-pick a mainline commit into a production kernel merely because the upstream fix exists.
Review which listening services must be reachable and narrow access through normal network controls where practical. This reduces exposure; it is not a vendor-certified fix or proof that all attack paths are blocked.
After the approved kernel rollout and any required reboot, record the running kernel again. Confirm the matching vendor row says fixed. Keep the check time and evidence with the patch ticket.
It affects Linux kernel TCP and IPv4 option lifetime handling. The CNA lists upstream branch fixes, while each distribution tracks its own packages. Match the exact kernel package and release.
Exploitation status is unknown for this profile. Public technical descriptions and a high CVSS score are not an incident report. Absence from the checked CISA KEV catalog does not prove that attacks cannot occur.
No. Ubuntu defines that status as an affected package whose fix is being worked on. A fixed status identifies an available corrected package. Check the current row before deployment.
Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.