CVE-2026-98469·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Fix AArch32 DBGBXVR<n> handling The consolidation of the breakpoint and watchpoint register accessors switched DBGBXVR<n> from trap_bvr() to trap_dbg_wb_reg(). The latter selects backing storage with demux_wb_reg(), which only handles Op2 values 4 through 7. Since DBGBXVR<n> uses Op2 1, an AArch32 guest access hits KVM_BUG_ON() and marks the VM dead. DBGBXVR<n> aliases DBGBVR<n>_EL1[63:32], and its AA32(HI) descriptor already selects the upper half. Map Op2 1 to dbg_bvr[] alongside Op2 4, restoring the pre-regression behavior.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.18.55, 7.2.9, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.20% — higher than 9% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-98469 scores 7.1 on CVSS, so a successful attack would be serious — but at 0.20%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched version to resolve this KVM virtualization issue affecting ARM64 systems. Users should upgrade to kernel 6.18.55, 7.2.9, or 7.3+ depending on their current branch, or install their distribution's patched kernel package. This fix restores proper handling of AArch32 breakpoint register access in KVM guests, preventing VM crashes.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and compare against fixed versions 6.18.55, 7.2.9, or 7.3+
- Step 2: Verify if KVM is running on ARM64 hardware using `lsmod | grep kvm` and `uname -m` to confirm ARM64 architecture
- Step 3: Search kernel logs for KVM panics with `sudo dmesg | grep -i 'kvm.*bug\|vm dead\|dbgbxvr'` to detect if this bug was triggered
- Step 4: After patching, confirm the new kernel is running with `uname -r` and reboot if necessary with `sudo reboot`
FAQ
What is CVE-2026-98469?
This vulnerability is a kernel panic in KVM's ARM64 hypervisor that occurs when an AArch32 guest accesses the DBGBXVR (Debug Breakpoint Extended Value Register). The kernel incorrectly routes the register access, triggering a fatal bug check and crashing the virtual machine.
Is CVE-2026-98469 being actively exploited?
No, this vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog and no public exploits are available. However, any guest with kernel debugging capabilities could trigger it intentionally or accidentally.
What versions of Kernel are affected by CVE-2026-98469?
All kernel versions prior to 6.18.55 (6.18 branch), 7.2.9 (7.2 branch), and 7.3+ (mainline) are affected. The bug was introduced during consolidation of breakpoint/watchpoint register handlers.
How do I check if my server is vulnerable to CVE-2026-98469?
Run `uname -r` to get your kernel version, then compare it: if you're on 6.18.x check if < 6.18.55, on 7.2.x check if < 7.2.9, or on 7.3+ you're safe. Also confirm ARM64 with `uname -m` and KVM is in use with `lsmod | grep kvm`.
Does Defensia detect CVE-2026-98469?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98469 will appear in your dashboard with remediation steps specific to your kernel branch.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98469. Free for 1 server.
Get started free