Ubuntu kernel CVE-2026-98432 patch: check flavor before reboot
Ubuntu administrators running kernels covered by these notices should check packages and update entitlements, then schedule a reboot. Prioritize machines exposing network services and hosts with multiple users.
1-minute summary
- Symptom / problem
- kernel มีช่องโหว่หลายส่วน รวม IPv4 TCP และ SCTP รายการแพตช์ใน USN กับสถานะบางหน้า CVE ยังไม่ตรงกัน
- Who should read
- Oracle บน Ubuntu 16.04 และ 24.04, AWS FIPS บน 20.04, FIPS/GCP FIPS บน 22.04 และ flavor ที่ระบุใน USN-9173-1 บน 22.04/24.04
- Fix in short
- เลือกแพ็กเกจให้ตรง release และ kernel flavor ใน USN ตรวจสิทธิ์ Ubuntu Pro และ FIPS Updates จากนั้นอัปเดต ตรวจโมดูลภายนอก และรีบูต เช็ก kernel ที่รันจริง แล้วตาม CVE ที่ยังไม่ขึ้น Fixed
I saw Ubuntu publish kernel notices on 19 Nov. 2026 adding Oracle and AWS FIPS, so I have combined them with the Ubuntu 22.04/24.04 updates in one post. Before updating, match the packages to your system release and kernel branch, and check how you receive patches.
Which branches get patches in this batch
| Notice | Ubuntu / kernels covered | What to check |
|---|---|---|
| USN-9171-2 | 16.04 Oracle | References CVE-2026-98432 and CVE-2026-99999; requires Pro with Legacy Support |
| USN-9170-2 | 20.04 AWS FIPS | References the two entries above and CVE-2026-64564; delivered through FIPS Updates |
| USN-9173-1 | 22.04/24.04, multiple flavors | Check the release table and the warning for CVE-2026-93221 |
| USN-9175-1 | 24.04 Oracle, 6.8 branch | Do not substitute the Oracle version number for 22.04 |
| USN-9168-2 | 22.04 FIPS / GCP FIPS | The image and metapackage use different version formats |
Earlier details are in the Ubuntu kernel roundup, NVIDIA/Tegra and NFS and Ubuntu Azure and Debian. In this post, I focus on packages and checks after updating.
Severity and statuses that still need tracking
CVE-2026-98432 is a use-after-free in IPv4 TCP. Ubuntu says it could lead to remote code execution and assigns it Critical priority.
CVE-2026-99999 results from incorrect checksum metadata that corrupts network header data. Ubuntu assigns it High priority and lists the attack vector as Local. The PwnEscape report describes a guest-to-host escape test in the researchers' lab. This does not confirm exploitation of production systems.
The scores and vectors below come from Ubuntu's page for each CVE. The attack conditions differ between these two vulnerabilities.
| CVE | CVSS 3.1 / vector | CVSS 4.0 / vector |
|---|---|---|
| CVE-2026-98432 | 9.8 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
9.2 — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CVE-2026-99999 | 9.3 — CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
6.9 — CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N |
AWS FIPS also references CVE-2026-64564, a use-after-free in SCTP.
I checked the KEV JSON in CISA's official repository. CVE-2026-98432, CVE-2026-99999, CVE-2026-64564 and CVE-2026-93221 are not in the 18 Nov. 2026 KEV catalog, so there is no KEV addition date or CISA deadline for these four entries. Absence from KEV does not mean there is no exploitation in the wild.
The USNs list updated packages for Oracle 16.04 and AWS FIPS 20.04, but the CVE-2026-98432 and CVE-2026-99999 pages still show Vulnerable — work in progress for these two branches. CVE-2026-64564 on AWS FIPS 20.04 also shows the same status. Update according to the USNs and keep tracking the status.
CVE-2026-93221 is a race condition that causes a double-free in the NFS server. This entry appears in the References for USN-9173-1 and USN-9175-1, but the CVE page still lists these statuses:
| Ubuntu / package | Status on the CVE page |
|---|---|
24.04 / linux |
Vulnerable — work in progress in 6.8.0-151.151 |
24.04 / linux-oracle |
Vulnerable — work in progress |
22.04 / linux-oracle-6.8 |
Vulnerable — work in progress in 6.8.0-1068.72~22.04.1 |
22.04 / linux-fips |
Vulnerable |
The statuses still disagree with the notices, so I cannot yet conclude that every branch is fully patched.
Package versions listed in the notices
The table lists updated versions according to the USNs.
| Ubuntu / USN | Image package | Package version |
|---|---|---|
| 16.04 / 9171-2 | linux-image-4.15.0-1162-oracle |
4.15.0-1162.173~16.04.1 |
| 20.04 / 9170-2 | linux-image-5.4.0-1169-aws-fips |
5.4.0-1169.180+fips1 |
| 22.04 / 9168-2 | linux-image-5.15.0-204-fips |
5.15.0-204.214+fips1 |
| 22.04 / 9168-2 | linux-image-5.15.0-1122-gcp-fips |
5.15.0-1122.132+fips1 |
| 22.04 / 9173-1 | linux-image-6.8.0-1068-oracle |
6.8.0-1068.72~22.04.1 |
| 22.04 / 9173-1 | linux-image-6.8.0-1070-ibm |
6.8.0-1070.71~22.04.1 |
| 22.04 / 9173-1 | linux-image-6.8.0-1074-gcp |
6.8.0-1074.82~22.04.1 |
| 24.04 / 9173-1 | linux-image-6.8.0-151-generic |
6.8.0-151.151 |
| 24.04 / 9173-1 | linux-image-6.8.0-1070-aws |
6.8.0-1070.76 |
| 24.04 / 9173-1 | linux-image-6.8.0-1070-aws-fips |
6.8.0-1070.76+fips1 |
| 24.04 / 9173-1 | linux-image-6.8.0-1074-gcp |
6.8.0-1074.82 |
| 24.04 / 9173-1 | linux-image-6.8.0-1070-ibm |
6.8.0-1070.71 |
| 24.04 / 9173-1 | linux-image-6.8.0-1069-gke |
6.8.0-1069.78 |
| 24.04 / 9173-1 | linux-image-6.8.0-1054-gkeop |
6.8.0-1054.58 |
| 24.04 / 9173-1 | linux-image-6.8.0-1011-vmware |
6.8.0-1011.11 |
| 24.04 / 9175-1 | linux-image-6.8.0-1068-oracle |
6.8.0-1068.72 |
Image packages ending in -64k use the same version as the row for the same branch in the table. This applies to Oracle/GCP on 22.04 and generic/AWS/GCP/GKE/Oracle on 24.04.
The metapackages listed in the notices are:
| Ubuntu / kernel branch | metapackage | Version |
|---|---|---|
| 16.04 / Oracle | linux-image-oracle |
4.15.0.1162.173~16.04.1 |
| 20.04 / AWS FIPS | linux-image-aws-fips or linux-image-aws-fips-5.4 |
5.4.0.1169.116 |
| 22.04 / FIPS | linux-image-fips or linux-image-fips-5.15 |
5.15.0.204.118 |
| 22.04 / GCP FIPS | linux-image-gcp-fips or linux-image-gcp-fips-5.15 |
5.15.0.1122.111 |
| 24.04 / Oracle (USN-9175-1) | linux-image-oracle-6.8 |
6.8.0-1068.72 |
Oracle 16.04 requires Ubuntu Pro with the Legacy Support add-on. AWS FIPS 20.04, FIPS/GCP FIPS 22.04 and AWS FIPS 24.04 in the notices receive FIPS Updates through Ubuntu Pro. Check that the required repositories are enabled before concluding that no patch is available.
Follow the update through to the running kernel
Check the release, kernel and installed packages:
cat /etc/os-release
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\t${db:Status-Status}\n' 'linux-image-*'
# ถ้าเครื่องมี Ubuntu Pro Client ให้ตรวจบริการที่เปิดอยู่ด้วย
pro status
- Match the release, flavor, image and metapackage to the USN, then check patch entitlements
- Prepare a maintenance window Check backups, console access and external modules
- Update Read the package changes and check module builds before rebooting
- Verify Check the running kernel, services and CVEs still marked Vulnerable
According to the APT manual, dist-upgrade can remove packages. Run a simulation and read the list before proceeding:
sudo apt-get update
apt-get -s dist-upgrade
sudo apt-get dist-upgrade
If you previously removed the metapackage, reinstall the one matching your kernel branch to receive future versions. The FIPS guide recommends fips-updates. Enabling this service also changes cryptographic packages, so check your system requirements first.
The notices warn of an ABI change that requires external modules to be recompiled and reinstalled. Check DKMS and manually installed modules before rebooting:
# ใช้เมื่อมี DKMS ติดตั้งอยู่ และตรวจว่ารองรับ kernel ใหม่แล้ว
dkms status
sudo reboot
After booting, check the kernel release with uname -r, then use dpkg-query to inspect the image package version for the running kernel. These two version formats differ:
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\n' "linux-image-$(uname -r)"
systemctl --failed
sudo journalctl -k -b -p warning
Check symptoms and evidence separately
The referenced Ubuntu pages do not provide a set of IOCs for detecting compromise. If you find a kernel oops or an unexpected service outage, collect logs and investigate the cause. Finding no errors does not confirm that the system is secure.
Ubuntu recommends a temporary mitigation for CVE-2026-98432 that drops IPv4 TCP packets containing IPv4 header options. These differ from TCP options, and the rules must cover the relevant network namespaces as well. This measure still does not block local processes that set IPv4 socket options themselves, so it cannot replace a kernel update.
For CVE-2026-64564, disable SCTP if it is not needed. Check the impact described on the CVE page first. These two measures do not cover the full set of vulnerabilities.
How I would prioritize the work
I would prioritize scheduling updates for machines accepting external TCP traffic and hosts with multiple users. For NFS servers, restrict access and keep tracking CVE-2026-93221 for the flavor in use.
Sources: Ubuntu USN-9171-2, USN-9170-2, USN-9173-1, USN-9175-1, USN-9168-2, Ubuntu CVE-2026-98432, CVE-2026-99999, CVE-2026-93221, CVE-2026-64564, FIPS guide, APT, DKMS, PwnEscape and CISA KEV JSON, 18 Nov. 2026 edition. Information current as of 19 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.
Hit something like this? Stuck somewhere?
Come trade notes on the LinuxThai board



Comments 0
No comments yet — be the first