Skip to content
World clockEU--:--UK--:--USA--:--CN--:--PLDEFRIT中文EN

portal about AI and technologyevents · analysis · interviews · technical background

Search
LIVE
›

Red Hat and Ubuntu ship fixes for 9.8-rated Linux TCP flaw as scanning starts

Red Hat and Ubuntu have both released patches for CVE-2026-98432, a 9.8-rated use-after-free in the Linux kernel's IPv4 TCP stack. Ubuntu published fixes for testing on Tuesday, and Red Hat followed the same day.

TechnologyAnalysisRachel NwosuPublished: 30 September 20264 min readSources 12
Red Hat and Ubuntu ship fixes for 9.8-rated Linux TCP flaw as scanning starts
Red Hat and Ubuntu have both released patches for CVE-2026-98432, a 9.8-rated use-after-free in the Linux kern

Red Hat and Ubuntu have now shipped fixes for CVE-2026-98432, the Linux kernel IPv4 TCP use-after-free that carries a 9.8 CVSS score. Ubuntu's fixes went out for testing on Tuesday, according to coverage dated 3 November. Red Hat's patch landed the same day. The bug affects Ubuntu, Red Hat and other distributions, per reporting from 28 October.

The sequencing matters more than the score. A kernel bug has become an operations problem. Security teams must now reconcile several partially overlapping advisories, an accidental public disclosure, and evidence that attackers are already hunting for hosts that missed the update. None of that fits neatly into a change window.

Scanning for the flaw has started in the wild, according to reports dated 2 November. One of those reports notes that an AI model produced an exploit for the flaw. Treat that as a claim from a single outlet and nothing more. Neither report confirms exploit code or names an actor.

An accidental disclosure, then a scramble

The path to this week's patches was messy. Several Linux kernel vulnerabilities went to the public kernel mailing list by mistake on 21 October, according to reporting from that date. A follow-up piece on 22 October described critical unpatched kernel flaws disclosed on the public list. For defenders, that is the worst possible order: the flaw becomes public before fixes are broadly available. Distributions then ship while the disclosure is already circulating. Every hour between the two is an hour attackers can use.

Red Hat's patch for the 9.8-rated flaw and Ubuntu's testing release both arrive in that window. An earlier report on 3 November, published before Red Hat's fix, noted that patches were not yet fully available. It said Red Hat had released while Ubuntu was still preparing. The picture has moved since then. That is why the dates in the advisories matter as much as the version numbers.

"Critical Linux vulnerability, patches not yet fully available. Red Hat releases, Ubuntu in preparation"

That headline, from 3 November, is now out of date. Ubuntu's release followed. Anyone who read it and closed the ticket should reopen it.

Why a TCP use-after-free is not a routine kernel CVE

TCP is the one stack almost no Linux host can avoid exposing. A use-after-free in that path is remotely reachable in principle. That is why the 9.8 score drew attention beyond the kernel mailing list. The practical risk depends on configuration, kernel version and whether untrusted networks can reach the vulnerable path. Neither report settles that question for any specific distribution. Admins who assume the worst and admins who assume the best are both guessing until they check their own exposure.

There is a second problem: patch coverage across the ecosystem is uneven. The same week that Red Hat and Ubuntu moved, Debian pushed a kernel update that patched 1,313 Linux CVEs in a single advisory, according to Dealroom on 30 September. That number says less about this bug than about the maintenance backlog distributions carry. It also explains why admins cannot assume a single kernel update fixes everything they track.

Cryptographic and userspace packages are moving too. OpenSSL 4.0.3 shipped with high-severity security fixes, as 9to5Linux and Linuxiac reported on 29 September. Those fixes include a flaw that could leak server memory in plaintext, per CyberSecurityNews. Kernel patches do not cover that class of bug. The two workstreams compete for the same maintenance windows.

The wider patch queue

Kernel flaws are not the only thing landing this month. Google released a Chrome update with 32 security fixes across Windows, Mac and Linux, according to CyberSecurityNews on 30 September. Apple patched a CoreGraphics zero-day linked to targeted attacks, per a 29 September report. Tails 7.14 updated its Tor Browser, Tor client and Linux kernel, Linuxiac reported. Each is a separate update path with its own verification step. Each one consumes time that a 9.8-rated network flaw does not leave spare.

Hardware-level issues add another layer. SecurityWeek reported on 29 September that a new Spectre v2 variant exposes Intel, AMD and Arm CPUs to data leaks. eSecurity Planet reported a Spectre attack that leaks Linux root password hashes in minutes. A single kernel patch does not fix those either. They are mitigation problems that depend on microcode, compiler flags and kernel configuration together.

The practical takeaway for operators is narrow and unglamorous. Check whether your distribution has shipped the CVE-2026-98432 fix, apply it, and then keep watching. The public disclosure means the scanning that started on 2 November will not stop once the first wave of hosts is patched. The rest of the queue, from OpenSSL to Chrome to Spectre mitigations, will still be waiting.

Comments 0

Sources

12
  1. 01OpenAI's dirty deeds Down Under included security bypass attempts, using exposed keys, source code siphonEN
  2. 02Cycode Extends Its ADLC Security Capabilities to Developers' WorkstationsEN
  3. 03Pentagon data breach of military personnel raises national security concernsEN
  4. 04Why Linux really will dominate the future of desktop computingEN
  5. 05Snow Linux: Debian-based but follows Poettering's Fitting everything togetherEN
  6. 06The Netherlands is preparing to dump Windows and Office for its own homebrew LinuxEN
  7. 07AI as a Compiler: Compiling Triton kernels without the Triton compilerEN
  8. 08DeepGEMM-Ascend: Huawei Ascend NPUs Matrix Multiplication Kernel LibraryEN
  9. 09Jinn – a Rust microkernel with capability-based security looking for contributorsEN
  10. 10DirtyBlanket: Fake Express Packages on npm Spread a Linux WormEN
  11. 11Another Look at Provable SecurityEN
  12. 12Top 10 Essential Linux Commands for DevOps EngineersEN

All figures and quotations in this text come from the sources listed below.

Content prepared by the editorial team with AI assistance.

Rachel Nwosu

Rachel Nwosu

AI, models and technology

Rachel Nwosu covers AI, models and technology for FLASH24, working from public model documentation, benchmark releases and repository histories rather than press summaries, and she skips announcements that arrive without reproducible numbers. She checks training-data claims against dataset cards and reruns reported metrics where code is available. She spends much of her week interviewing researchers and engineers, tracking model launch calendars, and comparing vendor benchmarks with independent evaluations. Outside the desk she runs 3D printers, restores old computers, and tests how models learn from internet junk. She does not publish benchmark figures she cannot trace to a source.

Newsroom →

Comments

0
  1. No comments yet — be the first.

Write a comment

Comments are public. We do not publish abuse, spam or advertising.