EST. 2026 — Notes from real server work SYSADMIN · SECURITY · AI · DIRECTADMIN Issue 01
THE SYSADMIN ALMANAC
Home / Security Update / More Ubuntu kernels patch CVE-2026-98432: check now and reboot
Security Update

More Ubuntu kernels patch CVE-2026-98432: check now and reboot

by Ton-Or ·20 Nov 2026·8 min read
More Ubuntu kernels patch CVE-2026-98432: check now and reboot

Ubuntu administrators using the kernel branches in the table should check packages and update entitlements immediately, then schedule maintenance to install the updates, check modules and reboot.

1-minute summary

Symptom / problem
ช่องโหว่ kernel หลายระบบย่อยมีผลต่างกันตาม flavor รวมถึง IPv4 TCP ที่ Ubuntu ระบุว่าอาจนำไปสู่ RCE
Who should read
Ubuntu 24.04, 22.04, 20.04 และ 18.04 เฉพาะแพ็กเกจที่ระบุในประกาศแต่ละฉบับ
Fix in short
อัปเดตตาม USN ให้ตรง release และ flavor ตรวจการ rebuild โมดูลภายนอก แล้วรีบูตและยืนยัน kernel ที่กำลังรัน
Jump to steps

I noticed that Ubuntu had added kernel notices dated 20 Nov. 2026, so I have broken down the package versions by branch for checking against the systems in use. Updating packages inside a container does not change the host's kernel. The earlier details are in Ubuntu kernel roundup for 19 Nov.. This post focuses on packages and checks after rebooting.

9.8CVSS 3.1 for IPv4 TCP
6 USNPages and update versions verified
Pro for some branchesCheck patch access
Reboot requiredCheck the running kernel

Which notices add which packages

This table selects CVEs worth reading alongside each group. The CVE list in a USN covers the entire notice; individual packages may be affected differently. Check the status of the packages you use as well.

Notice Ubuntu / kernel branch CVEs to read alongside it
USN-9183-1 24.04 FIPS CVE-2026-98432, CVE-2026-74350, CVE-2026-99999 and CVE-2026-93221
USN-9173-2 22.04 AWS 6.8 and realtime; 24.04 realtime CVE-2026-93221 in the NFS server
USN-9168-3 22.04 NVIDIA, lowlatency and realtime on the 5.15 branch CVE-2026-99203 in pipe
USN-9167-2 22.04 Tegra / Intel IoT realtime; 20.04 Oracle 5.15 CVE-2026-99203 in pipe
USN-9169-2 20.04 HWE 5.15, lowlatency and Tegra CVE-2026-99203 in pipe
USN-9170-3 18.04 Oracle 5.4 CVE-2026-98432, CVE-2026-99999 and CVE-2026-64564

The USN-9184-1 page still returned 404 when I checked, so I have not included Tegra IGX details or inferred a fixed version from other Tegra branches.

Read high scores alongside the attack conditions

CVE-2026-98432 is a use-after-free in IPv4 TCP handling. One task is still using IP options data after another task has freed the memory. Ubuntu says this could lead to remote code execution and assigns it Critical priority.

CVE-2026-74350 is in OCFS2. Reading a fast symlink from a malformed inode causes a read beyond the buffer boundary. Ubuntu assigns it High priority, while CVSS 3.1 rates it Critical at 9.8, but CVSS 4.0 gives it 7.1 and identifies an availability impact. The filesystem conditions also need to be considered.

The two entries above both have CVSS 3.1 = 9.8 and share the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, according to the Ubuntu pages.

CVE Mechanism / Ubuntu priority CVSS 3.1 and vector
CVE-2026-99999 Incorrect checksum metadata corrupts a network header / High 9.3 — CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVE-2026-64564 SCTP ASCONF uses a transport after its memory has been freed / Critical 9.8 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVE-2026-93221 Concurrent grace period completion in the NFS server causes a double-free / Critical 8.1 — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVE-2026-99203 Incorrect fasync deregistration in pipe leads to use of freed memory / High 7.8 — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The pipe vulnerability requires low local privileges according to the vector. Administrators of machines where users can run code should check this entry too. The NFS vulnerability requires an NFS server service and a race under the conditions described for the vulnerability. Ubuntu says a public exploit named PwnEscape already exists for CVE-2026-99999. A public exploit does not confirm attacks in the wild.

I checked CISA's KEV JSON, and CVE-2026-98432, CVE-2026-74350, CVE-2026-99999, CVE-2026-64564, CVE-2026-93221 and CVE-2026-99203 were not in the KEV edition dated 18 Nov. 2026. The notices I opened did not report attacks in the wild. Absence from KEV does not confirm that no attacks have occurred.

Update versions in the USNs and statuses that still differ

The middle column is the kernel release; the image package name is linux-image- followed by that value. The right column is the package version. These two values are not interchangeable. The table includes the options listed in the USNs; choose the one that matches the machine.

Ubuntu / USN Image kernel release Image package version in the USN
24.04 / 9183-1 6.8.0-151-fips 6.8.0-151.151+fips1
24.04 / 9173-2 6.8.1-1065-realtime 6.8.1-1065.66
22.04 / 9173-2 6.8.0-1070-aws, 6.8.0-1070-aws-64k 6.8.0-1070.76~22.04.1
22.04 / 9173-2 6.8.1-1065-realtime 6.8.1-1065.66~22.04.1
22.04 / 9168-3 5.15.0-1116-nvidia, 5.15.0-1116-nvidia-lowlatency 5.15.0-1116.117
22.04 / 9168-3 5.15.0-199-lowlatency, 5.15.0-199-lowlatency-64k 5.15.0-199.209
22.04 / 9168-3 5.15.0-1120-realtime 5.15.0-1120.129
22.04 / 9167-2 5.15.0-1072-nvidia-tegra, 5.15.0-1072-nvidia-tegra-rt 5.15.0-1072.74
22.04 / 9167-2 5.15.0-1113-intel-iot-realtime 5.15.0-1113.117
20.04 / 9167-2 5.15.0-1118-oracle 5.15.0-1118.124~20.04.1
20.04 / 9169-2 5.15.0-1072-nvidia-tegra, 5.15.0-1072-nvidia-tegra-rt 5.15.0-1072.74~20.04.1
20.04 / 9169-2 5.15.0-199-lowlatency, 5.15.0-199-lowlatency-64k 5.15.0-199.209~20.04.1
20.04 / 9169-2 5.15.0-204-generic, 5.15.0-204-generic-64k, 5.15.0-204-generic-lpae 5.15.0-204.214~20.04.1
18.04 / 9170-3 5.4.0-1167-oracle 5.4.0-1167.177~18.04.1

The versions come from the USN links in the first table. Metapackages use a different set of version numbers, such as 5.15.0.199.164 for linux-image-lowlatency on 22.04 and 5.15.0.1116.116 for linux-image-nvidia. Do not compare these numbers directly with image package versions.

USNs and CVE pages still differ

The USNs list updated packages, but some CVE pages still show Vulnerable / work in progress. For FIPS 24.04, these are CVE-2026-98432, CVE-2026-74350 and CVE-2026-99999, with version 6.8.0-151.151+fips1 listed. For Oracle 5.4 on 18.04, these are CVE-2026-98432, CVE-2026-99999 and CVE-2026-64564, with version 5.4.0-1167.177~18.04.1 listed. Update according to the notices and continue tracking the status. The two pages still differ, so I cannot yet conclude that every CVE has been fixed.

The CVE-2026-93221 page still shows work in progress for AWS 6.8 on 22.04 at 6.8.0-1070.76~22.04.1, as it does for realtime on 24.04 at 6.8.1-1065.66 and realtime 6.8 on 22.04 at 6.8.1-1065.66~22.04.1. FIPS 24.04 is still marked Vulnerable. Read these statuses alongside the USNs and check each branch separately.

The CVE-2026-99203 page also still differs from the USNs for the 5.15 branches in the table. On 22.04, NVIDIA, lowlatency and realtime are still marked Vulnerable, while Tegra and Intel IoT realtime still show work in progress. On 20.04, HWE 5.15, lowlatency and Tegra are still marked Vulnerable, while Oracle 5.15 still shows work in progress. The numbers in the table are the update versions listed in the USNs; they do not yet establish that the CVE pages confirm a fix.

Update the correct branch, then prepare modules before rebooting

The 20.04 and 18.04 packages in the table are listed as requiring Ubuntu Pro. FIPS 24.04 receives updates through FIPS Updates with Ubuntu Pro. The realtime and Intel IoT realtime branches labelled Real-time also require entitlement to that service. Check pro status on machines with Pro Client. If APT shows no candidate, check entitlements and package repositories first.

. /etc/os-release
printf '%s\n' "$PRETTY_NAME"
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\t${Status}\n' 'linux-image-*'
pro status

Check the installed status too, because old kernels may remain in the list. Canonical's documentation recommends fips-updates and warns that enabling FIPS also changes core libraries. Check services according to the system's policy.

  1. Check the branch Match the Ubuntu release, kernel flavor, metapackage and Pro entitlement
  2. Prepare the update Back up data and review the planned package changes before installing
  3. Check modules Rebuild and install external modules for the new ABI, and check the results before rebooting
  4. Reboot and verify Check the running kernel, modules and services in use

Start by updating the package lists, then simulate the upgrade. Check that it includes an image of the same flavor as listed in the USN and that no important packages will be removed unintentionally.

sudo apt update
sudo apt -s full-upgrade

Then install during the maintenance window. Read the full installation output before issuing a reboot. If a required module fails to build, fix that first.

sudo apt full-upgrade
# ตรวจผลติดตั้ง image, headers และโมดูลภายนอกให้เรียบร้อยก่อน
sudo reboot

All 6 USNs warn that the ABI has changed, requiring external kernel modules to be recompiled and reinstalled. The package system and module tools may handle this, but check the results. If using DKMS, run dkms status and check whether it shows installed for the target kernel. For manually installed modules, follow the vendor's instructions.

Check flavorrelease + USNInstall patchCheck new ABI modulesRebootLoad new kernelVerifyuname -rAfter successful package installation, check the running version after reboot
Check packages, modules and the running kernel before closing the update task

What to check after rebooting, and how to check for compromise

uname -r
dpkg-query -W -f='${Package}\t${Version}\n' "linux-image-$(uname -r)"
systemctl --failed
sudo journalctl -k -b -p warning --no-pager

Compare the output of uname -r with the kernel release column, then compare the package version with the right column. If the old version is still running, check the installation results and the kernel selected at boot. Then check web, mail and network services, along with the required modules.

The notices I could read did not provide IOCs for confirming a compromise. A kernel oops or service failure alone does not establish that an attack occurred. If you suspect a compromise, collect logs and evidence before changing the system. Patching does not remove an intruder who may already be on the machine.

Scope of the checks

Version numbers help verify an update, while confirming a compromise requires other evidence. This round of notices does not yet provide a retrospective check that can confirm whether these vulnerabilities have been exploited on a machine.

I recommend that administrators schedule updates and reboots for machines matching the table, especially those accepting connections from external networks, those allowing users to run code, and NFS servers. Check modules before rebooting too. I will continue tracking the entries where the USNs and CVE pages still differ. Administrators should check the results after rebooting before closing the task, even if APT reports a successful update.

Sources: Ubuntu USN-9183-1, USN-9173-2, USN-9168-3, USN-9167-2, USN-9169-2, USN-9170-3, the CVE pages and Canonical documentation linked in the article, and CISA KEV JSON. Information current through 20 Nov. 2026. I will come back and update this later.

Want us to set this up?

Get help with server setup, configuration, migration, or troubleshooting. Save time for the work that matters.

Get a quote

Hit something like this? Stuck somewhere?

Come trade notes on the LinuxThai board

→ Continue on the board

Comments 0

No comments yet — be the first