Ubuntu Azure USN-9160-1 Advises Updating and Rebooting
Administrators running the Azure 7.0 kernel on Ubuntu 24.04 LTS should schedule an update and reboot according to the USN, and check the CVE pages whose statuses still disagree. Debian trixie systems with needrestart installed should receive the regression fix during maintenance.
1-minute summary
- Symptom / problem
- Azure kernel มีช่องโหว่รวมถึง RCE ในการจัดการ IPv4 TCP ส่วน needrestart มีอัปเดตแก้ regression ต่อจากการปิดช่องโหว่ยกระดับสิทธิ์
- Who should read
- Ubuntu 24.04 LTS ที่ใช้ linux-azure-7.0 และ Debian trixie ที่ติดตั้ง needrestart
- Fix in short
- อัปเดต Azure kernel ตาม USN ที่ระบุ 7.0.0-1020.21~24.04.2 ตรวจโมดูลภายนอกแล้วรีบูต และตรวจสถานะ CVE ซ้ำเพราะยังขึ้นว่าอยู่ระหว่างแก้ ส่วน needrestart ให้ใช้ 3.11-1.1~deb13u2 หรือใหม่กว่าสำหรับ trixie
I saw Ubuntu USN-9160-1, dated 19 Nov 2026, for the Azure 7.0 kernel on Ubuntu 24.04 LTS, so I have collected it here with the needrestart update for Debian trixie. The kernel requires a reboot after installation, and the CVE page statuses still disagree with the USN and need another check. For needrestart, there is a regression fix for machines that already installed the initial security patch.
| Advisory | Machines to check | Reference package version |
|---|---|---|
| USN-9160-1 | Ubuntu 24.04 LTS running linux-azure-7.0 |
7.0.0-1020.21~24.04.2 |
| DSA-6637-1 | Debian trixie with needrestart installed, patching the original vulnerability |
3.11-1.1~deb13u1 |
| DSA-6637-2 | Debian trixie with needrestart installed, receiving the follow-up regression fix |
3.11-1.1~deb13u2 |
The package versions come from USN-9160-1 and the Debian Tracker entries for revision -1 and revision -2. Compare the full package versions within the same release and flavor.
Some Ubuntu information still disagrees: the USN lists 7.0.0-1020.21~24.04.2 as the fixed package version, but the CVE-2026-98432 and CVE-2026-99999 pages still show Vulnerable work in progress in 7.0.0-1020.21~24.04.2 for linux-azure-7.0 on Ubuntu 24.04 LTS. I recommend updating according to the USN and checking both pages again before concluding that these two CVEs are resolved.
What patches Ubuntu Azure receives
This advisory covers the linux-azure-7.0 package. If you read the article on the FIPS and Tegra kernels, check the Azure package versions separately.
The vulnerability that needs urgent attention is CVE-2026-98432 in IPv4 TCP connection handling. The kernel may free memory holding IP options while another CPU is still reading that data to construct a SYNACK. This is called a use-after-free: memory is still being used after it has been freed. Ubuntu states that this could allow an attacker to execute code remotely.
The advisory also includes CVE-2026-99999, which concerns validation of checksum_start. If a packet with invalid checksum metadata enters the IPv4 stack, the skb_checksum_help function may corrupt the network header. According to the Linux CVE record, the described attack path originates from a guest or a virtual device on the machine, rather than a packet sent directly to the machine from the internet. This update also fixes vulnerabilities in other parts of the kernel.
Severity and evidence of exploitation
Ubuntu assigns CVE-2026-98432 a Critical priority, a CVSS 3.1 score of 9.8, and the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. This score and vector match the Linux CVE record. They indicate that the vulnerability can be exploited over the network without existing privileges or any user interaction, with high impacts on confidentiality, integrity, and availability. The score does not guarantee successful exploitation on every machine.
For CVE-2026-99999, the Ubuntu page assigns a High priority and says a public exploit named PwnEscape is available. Public exploit code must be distinguished from reports of actual attacks. Ubuntu and the CVE record give it a CVSS 3.1 score of 9.3, while Red Hat gives it 8.8. These two scores assess the privileges required before exploitation differently: the CVE record uses PR:N, while Red Hat uses PR:L.
CVE-2026-98432, CVE-2026-99999, and CVE-2026-124757 are all absent from the 18 Nov 2026 KEV catalog (catalogVersion: 2026.11.18), so this edition has no KEV addition dates or deadlines for any of the three. Absence from KEV does not mean they are safe.
However, the exploitation information for CVE-2026-99999 contains a discrepancy: Red Hat calls it a “KEV active-exploit case,” while the KEV JSON edition I checked has no entry for it. I therefore do not conclude that there are no reports of actual attacks, and I do not use Red Hat's wording as a substitute for an addition date or deadline from CISA.
A successful APT package installation completes only the installation step. After the machine boots again, check both the running kernel and its package version before closing the patching task.
Debian needrestart revision -2 fixes a regression after the original CVE patch
DSA-6637-2, dated 19 Nov 2026, states that the original patch was backported incorrectly, causing problems with notify-send notifications to user sessions over D-Bus. The fixed version for trixie is 3.11-1.1~deb13u2. CVE-2026-124757 refers to DSA-6637-1, dated 18 Nov 2026, whose original fixed version was 3.11-1.1~deb13u1. Revision -2 fixes a regression introduced by the original patch; it does not announce a new CVE number.
needrestart checks for processes still using old libraries and reports what needs to be restarted. The original vulnerability came from insufficient validation of process names and cgroup paths. Local users can control both pieces of information. The researcher on oss-security states that an attacker can make a process appear to belong to a root session and pass its process name to the notify-send hook. Some packages concatenate this name into a shell command, allowing an attacker to execute commands as root.
For trixie version 3.11-1, the reporter made notify-send run as root with a chosen DISPLAY and message, but has not successfully reproduced command execution on trixie. This limitation does not change the Debian Tracker status, which lists it as affected with a fixed package available.
After updating, if the system uses notify-send with D-Bus, test sending a notification to a user session as well, since that is the part affected by this regression.
trixie machines that have received deb13u1 should move forward to deb13u2 or a later version for trixie. If notifications fail, check the package and the active session instead of reverting to a version from before the vulnerability was patched.
Update the right packages and prepare to reboot
Start by checking the release, running kernel, installed packages, and held packages before scheduling maintenance.
cat /etc/os-release
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'linux-image*'
apt-mark showhold
The USN lists the images linux-image-7.0.0-1020-azure and linux-image-7.0.0-1020-azure-64k at version 7.0.0-1020.21~24.04.2. Choose the one matching the existing kernel line. Review the upgrade list before installing, following the Ubuntu guide.
- Check the release and flavor Match the installed packages to the advisory and check held packages.
- Prepare a downtime window Check backups and console access before starting the kernel update.
- Install and check modules Read all APT output and external module build results.
- Reboot and verify Compare the running kernel with the fixed package and test the services in use.
sudo apt update
sudo apt upgrade --simulate
sudo apt upgrade
If APT does not offer a new kernel, check the metapackage for the existing flavor, package repositories, dependencies, and held packages. Do not remove a hold without knowing why it was set.
Ubuntu warns that the ABI has changed, so external kernel modules must be rebuilt and reinstalled. If you use DKMS, check the build results for the target kernel. For modules you manage yourself, follow the vendor's procedure and resolve build errors before rebooting, especially for network and storage modules.
# ใช้ตรวจเมื่อมี DKMS ติดตั้งอยู่
dkms status
# สั่งหลังตรวจแพ็กเกจและโมดูลครบ ในช่วงบำรุงรักษาที่เตรียมไว้
sudo systemctl reboot
For Debian trixie, check that the security repository is enabled, then upgrade the installed needrestart package. --only-upgrade will not install it on machines that do not have this package.
sudo apt update
apt-cache policy needrestart
sudo apt install --only-upgrade needrestart
dpkg-query -W -f='${binary:Package}\t${Version}\n' needrestart
Check after patching, separately from checking for compromise
After Ubuntu boots again, check the package for the running kernel as well, because uname -r does not show the full package revision. The standard azure variant in the USN uses the name 7.0.0-1020-azure; compare the 64k variant against its own listing separately.
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\n' "linux-image-$(uname -r)"
systemctl --failed
sudo journalctl -k -b --no-pager
Test network, storage, and the services the machine is responsible for. If it still boots an old kernel, find the cause, and check the two Azure CVEs whose statuses still disagree before closing the task. needrestart must be at 3.11-1.1~deb13u2 or later for trixie, and notifications should also be tested.
The cited sources do not provide a ready-made IOC list. An Oops or crash in the kernel log is not evidence specific to an attack, and the absence of errors does not confirm that the machine has never been compromised. If you find unexplained root activity, preserve logs and update history for further investigation. Patching does not remove anything that may have been planted earlier.
How I recommend prioritizing these patches
I recommend promptly scheduling an update and reboot for Ubuntu systems running Azure 7.0 that accept network connections, because CVE-2026-98432 could allow remote code execution. Update according to the USN and follow the CVE pages whose statuses still disagree. For Debian trixie, include the needrestart regression fix in the maintenance window, especially on systems with multiple users or notifications after upgrades.
While waiting to install the fixed kernel and reboot, Ubuntu provides a temporary recommendation on the CVE-2026-98432 page to filter IPv4 TCP traffic containing IP options. Choose a method that matches the firewall in use. If containers or guests have separate network namespaces, the rules must be applied in each namespace as well. This reduces network exposure, but local users can still set socket options, so it cannot replace the patch. I recommend reading the limitations and testing the impact on connections before applying the actual rules.
Sources: Ubuntu USN-9160-1, Ubuntu CVE-2026-98432, Ubuntu CVE-2026-99999, Linux CVE record: CVE-2026-98432, Linux CVE record: CVE-2026-99999, Red Hat CVE-2026-99999, Debian DSA-6637-1, Debian DSA-6637-2, Debian DSA-6637-1 Tracker, Debian DSA-6637-2 Tracker, Debian CVE-2026-124757 Tracker, Researcher's report on oss-security, Ubuntu package guide, CISA KEV data. Information current as of 19 Nov 2026; the KEV catalog checked was the 18 Nov 2026 edition. I'll 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