Debian/Ubuntu: kernel CVE-2026-64564 patches, check Java now
Ubuntu kernel and Debian OpenJDK administrators should check packages against the advisories, starting with systems that accept SCTP and KVM hosts that run guests from others, and schedule reboots and Java service restarts
1-minute summary
- Symptom / problem
- kernel มีบั๊กหน่วยความจำใน SCTP และ cache ของ KVM ส่วน OpenJDK มีช่องโหว่ Compiler ที่อาจนำไปสู่ RCE เมื่อเข้าเงื่อนไข
- Who should read
- Ubuntu ตาม release และ kernel flavor ในแต่ละ USN รวมถึง Debian trixie ที่ติดตั้ง OpenJDK 21 หรือ 25 รุ่นที่ยังไม่ได้แก้
- Fix in short
- เทียบ USN กับ CVE tracker และแพ็กเกจในคลัง อัปเดตสายที่ใช้อยู่ ตรวจโมดูลภายนอก แล้วรีบูตและเริ่มบริการ Java ใหม่
I noticed Ubuntu released kernel advisories on 19 Nov. 2026 and Debian had OpenJDK patches, so I put together this list to work through. Before closing out the work, check both the kernel branch and the status of each CVE.
Which advisories to follow this round
This table gives example binary image versions from the USNs and does not cover every flavor. Check the status of each CVE as well, and do not compare metapackage versions directly with image versions.
| Advisory | Example Ubuntu / kernel flavor | Image version in the USN | Access stated in the advisory |
|---|---|---|---|
| USN-9165-1 | 26.10 generic / generic-64k | 7.3.0-11.12 |
Standard |
| USN-9166-1 | 26.04 LTS generic / generic-64k | 7.0.0-44.44 |
Standard |
| USN-9166-1 | 24.04 LTS gcp / gcp-64k | 7.0.0-1018.20~24.04.1 |
Standard |
| USN-9167-1 | 22.04 LTS generic | 5.15.0-204.214 |
Standard |
| USN-9167-1 | 20.04 LTS ibm | 5.15.0-1115.119~20.04.1 |
Ubuntu Pro |
| USN-9168-1 | 22.04 LTS kvm / aws-fips | 5.15.0-1113.118 / 5.15.0-1121.128+fips1 |
kvm standard; FIPS requires Pro |
| USN-9169-1 | 20.04 LTS aws, 5.15 branch | 5.15.0-1121.128~20.04.1 |
Ubuntu Pro |
| USN-9170-1 | 20.04 LTS generic / 18.04 LTS generic, 5.4 branch | 5.4.0-247.267 / 5.4.0-247.267~18.04.1 |
Ubuntu Pro |
| USN-9171-1 | 18.04 LTS kvm | 4.15.0-1182.187 |
Ubuntu Pro |
| USN-9171-1 | 16.04 LTS generic, 4.15 branch | 4.15.0-263.275~16.04.1 |
Pro + Legacy Support |
| USN-9171-1 | 14.04 LTS azure, 4.15 branch | 4.15.0-1210.225~14.04.1 |
Pro + Legacy Support |
| USN-9172-1 | 16.04 LTS generic, 4.4 branch | 4.4.0-293.327 |
Pro + Legacy Support |
| USN-9172-1 | 14.04 LTS generic, 4.4 branch | 4.4.0-293.327~14.04.1 |
Pro + Legacy Support |
If you use another flavor, open the full table, particularly for FIPS, where you need to check the entitlement required for that row. USN-9165-1 fixes bugs in the Cryptographic API, filesystem, key management, io_uring, PID namespace and tracing.
SCTP scores 9.8, and patches extend to older kernels
CVE-2026-64564 is a bug in SCTP ASCONF processing. The address deletion command frees the transport's memory, but a later step still references that memory, causing a use-after-free, according to the Linux CVE record. An attacker must be able to establish an SCTP association and negotiate ADD-IP; check this condition as well. Serving a website over TCP alone does not establish that this condition is met.
Canonical assigns priority Critical and CVSS 3.1 9.8: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. This score assesses a network attack that requires neither an account nor user interaction and has a high impact when the conditions are met.
USN-9170-1 lists this CVE, but the CVE page still marks linux on 20.04 as Vulnerable work in progress in 5.4.0-247.267, and linux-hwe-5.4 on 18.04 is also still work in progress. These two pages disagree, so I am not yet concluding that the versions in the table fix this CVE. Check the packages actually released and continue tracking the status.
For CVE-2026-98432 and CVE-2026-99999, USN-9170-1 through USN-9172-1 list both CVEs with packages for the older releases and flavors in the table, but the trackers for both CVEs still mark linux on 20.04, 18.04 and 16.04 as work in progress. The information still disagrees with the advisories, so systems awaiting patches should be checked again before concluding that all fixes are in place. Read the vulnerability details in the earlier Ubuntu HWE article.
Ubuntu recommends the module disabling method below. Check service dependencies first. Do not force the removal of a module that is in use. This does not fix the other CVEs.
# เฉพาะระบบที่ยืนยันว่าไม่ต้องใช้ SCTP
printf '%s\n' 'install sctp /bin/false' | sudo tee /etc/modprobe.d/disable-sctp.conf
sudo update-initramfs -u
# ถ้าโหลดโมดูลอยู่และไม่มีบริการใช้งานแล้ว
sudo rmmod sctp
KVM scores 8.8: assess the host running the guests
USN-9166-1 through USN-9169-1 reference CVE-2026-99082. The bug is in each vCPU's MMIO cache while in SMM. The code selects a memslot that does not match the address space, potentially using stale cached data. The patch changes this to use the memslot currently in use by the vCPU.
The Linux CVE record describes a test in which an attacker controls the guest kernel and uses nested VMX/EPT to access host memory. The demonstrated case requires those conditions to be met first.
Canonical shows CVSS 3.1 8.8: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H and assigns Ubuntu priority Medium. The same page also shows CVSS 4.0 4.6: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. These two scores assess the required privileges and impact differently, so read them alongside the guest and host conditions.
Different assessors also assign different scores. Red Hat assigns CVSS v3 of 5.6, while Canonical shows 8.8, so scores from different sources should not be used interchangeably.
The tracker still shows linux on 26.04 and 24.04 as work in progress, even though USNs have been issued. The two sources still disagree. KVM hosts using generic must also be checked; this does not affect only the linux-kvm flavor.
Debian OpenJDK: keep CVE lists separate and complete all restarts
DSA-6639-1 for OpenJDK 21 lists CVE-2026-114820 and CVE-2026-114938 through CVE-2026-114946, while DSA-6640-1 for OpenJDK 25 has the same list plus CVE-2026-114947. Do not combine the lists for the two branches and conclude that they are affected in exactly the same way.
| Debian trixie | Fixed version in the security repository |
|---|---|
| openjdk-21 | 21.0.13.1+2-1~deb13u1 |
| openjdk-25 | 25.0.5.1+2-1~deb13u1 |
The one to check urgently is CVE-2026-114938. Canonical assigns priority High, CVSS 8.1, and identifies it as RCE with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The Debian tracker for this CVE states that exploitation is difficult. An attacker must supply data to an API in the affected Compiler component, for example through a web service. Check whether your Java services allow external input to reach that API.
The Canonical page labels the table CVSS v3.0, but the vector specifies 3.1. I use 3.1 from the vector, which agrees with the Debian tracker.
Check the runtime each service actually uses, including those bundled with applications and those inside containers. Running java -version in a shell only tells you about the runtime selected by that shell.
Update sequence: check modules before closing out the work
Start with the inspection commands, selecting packages that match the flavor in use.
cat /etc/os-release
uname -r
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'linux-image-*' 'openjdk-*' 2>/dev/null
apt-mark showhold
# Ubuntu ที่มี Pro client: ตรวจสิทธิ์และบริการที่เปิดไว้
pro status
- Match packages Check release, flavor and architecture against the advisories, tracker and APT
- Prepare the system Back up data, test critical workloads and prepare a recovery path if boot fails
- Install Check held packages and Pro or Legacy entitlements
- Check modules The USNs warn of an ABI change; compile and install external modules to match the new kernel
- Activate the patches Reboot, check the kernel and restart Java services
This Ubuntu 22.04 generic example uses a metapackage to pull in the new image. If you use another flavor, select the package for your existing branch instead.
sudo apt update
apt-cache policy linux-generic
apt -s install --only-upgrade linux-generic
# อ่านผลจำลองก่อน แล้วติดตั้งเมื่อตรงกับสายที่ใช้อยู่
sudo apt install --only-upgrade linux-generic
On Debian, this example updates all OpenJDK 21 and 25 packages with installed status.
sudo apt update
mapfile -t java_packages < <(
dpkg-query -W -f='${binary:Package}\t${db:Status-Status}\n' 'openjdk-21-*' 'openjdk-25-*' 2>/dev/null |
awk '$2 == "installed" {print $1}'
)
if ((${#java_packages[@]})); then
apt-cache policy "${java_packages[@]}"
sudo apt install --only-upgrade "${java_packages[@]}"
fi
Check DKMS for the kernel you will use before rebooting. After booting, check with uname -r. For Java, replace the example unit name with the service you want, then check the runtime of the new process as well.
# ก่อนรีบูต: ตรวจ DKMS ถ้ามี และแก้ข้อผิดพลาดของ kernel เป้าหมายให้ครบ
if command -v dkms >/dev/null 2>&1; then dkms status; fi
# รีบูตในรอบที่เตรียมไว้
sudo reboot
Check the results after the system has booted and you have reconnected. This example unit assumes that MainPID is the JVM itself.
uname -r
systemctl --failed
java -version
# เฉพาะบริการ Java ที่ยังต้องเริ่มใหม่ ชื่อนี้เป็นตัวอย่าง
sudo systemctl restart example-java.service
systemctl status example-java.service --no-pager
java_pid=$(systemctl show --property MainPID --value example-java.service)
sudo readlink "/proc/$java_pid/exe"
The job is not finished if the packages are installed but the system is still running the old kernel or JVM. Confirm the service executable as well. Do not use Livepatch in place of the reboot requirement without checking its coverage.
Check for anomalies and set priorities
CVE-2026-64564, CVE-2026-99082 and CVE-2026-114938 are not yet in the 18 Nov. 2026 KEV edition, according to the JSON in CISA's official repository, which specifies catalogVersion as 2026.11.18. None of the three therefore has a date added or remediation deadline in this KEV edition. Absence from KEV does not mean there have been no attacks and should not be used as a reason to delay patching.
A CVE record describing an exploitation test does not confirm exploitation outside testing. I therefore do not conclude from that information that these three CVEs have been exploited in the wild.
Check for Oops, panic and the kvm_mmu_write_protect_fault warnings mentioned in the CVE record, then compare their timing with unusual guest behavior. These symptoms can have other causes and cannot yet confirm a successful compromise.
sudo journalctl -k --no-pager | grep -Ei 'sctp|kvm_mmu_write_protect_fault|oops|panic|use-after-free'
If you suspect an attack, preserve evidence and follow your incident response procedure. I put systems that accept SCTP and KVM hosts running guests from others near the top of the list, without waiting for the monthly cycle. For Java, urgently check where input enters, update and restart services. Continue following up on entries where the USNs and tracker still disagree.
Sources: Ubuntu USN-9165-1, USN-9166-1, USN-9167-1, USN-9168-1, USN-9169-1, USN-9170-1, USN-9171-1, USN-9172-1, Ubuntu CVE-2026-64564, Ubuntu CVE-2026-99082, Ubuntu CVE-2026-114938, Debian DSA-6639-1, Debian DSA-6640-1, Debian CVE-2026-114938, Ubuntu CVE-2026-98432, Ubuntu CVE-2026-99999, Red Hat CVE-2026-99082, CISA KEV JSON, 18 Nov. 2026 edition and the CVE records linked in the article. Information checked on 19 Nov. 2026. The USN pages and CVE tracker still disagree on the status of some entries. I will return to 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