CVE-2026-46022·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: misc: ibmasm: fix OOB MMIO read in ibmasm_handle_mouse_interrupt() ibmasm_handle_mouse_interrupt() performs an out-of-bounds MMIO read when the queue reader or writer index from hardware exceeds REMOTE_QUEUE_SIZE (60). A compromised service processor can trigger this by writing an out-of-range value to the reader or writer MMIO register before asserting an interrupt. Since writer is re-read from hardware on every loop iteration, it can also be set to an out-of-range value after the loop has already started. The root cause is that get_queue_reader() and get_queue_writer() return raw readl() values that are passed directly into get_queue_entry(), which computes: queue_begin + reader * sizeof(struct remote_input) with no bounds check. This unchecked MMIO address is then passed to memcpy_fromio(), reading 8 bytes from unintended device registers. For sufficiently large values the address falls outside the PCI BAR mapping entirely, triggering a machine check exception. Fix by checking both indices against REMOTE_QUEUE_SIZE at the top of the loop body, before any call to get_queue_entry(). On an out-of-range value, reset the reader register to 0 via set_queue_reader() before breaking, so that normal queue operation can resume if the corrupted hardware state is transient.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.4
- 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.17% — higher than 6% 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-46022 scores 7.1 on CVSS, so a successful attack would be serious — but at 0.17%, 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.
Affected versions
From: 6.19
Until: 7.0.4
Fixed in: 7.0.4
How to fix this CVE
Update your Linux kernel to version 7.0.4 or later to patch an out-of-bounds memory read vulnerability in the IBM ASM driver. This fix adds boundary validation to prevent hardware-triggered MMIO reads beyond allocated queue memory. Apply kernel updates through your distribution's package manager and reboot to activate the patched kernel.
sudo dnf update kernel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Run `uname -r` to check your current kernel version; if it is between 6.19 and 7.0.3 inclusive, your system is vulnerable
- Verify if ibmasm driver is loaded by running `lsmod | grep ibmasm`; if the module is present, the vulnerable code path is active
- Search kernel logs with `sudo dmesg | grep -i 'ibmasm\|machine check'` or `sudo journalctl -k | grep -i 'ibmasm\|machine check'` for signs of OOB memory access or machine check exceptions
- After patching, confirm the fix with `uname -r` to ensure kernel version is 7.0.4 or higher, then reload or verify the ibmasm module is functioning without errors
FAQ
What is CVE-2026-46022?
CVE-2026-46022 is a high-severity out-of-bounds MMIO read vulnerability in the Linux kernel's IBM ASM driver that occurs when hardware-provided queue indices exceed safe bounds, potentially allowing a compromised service processor to trigger memory access violations.
Is CVE-2026-46022 being actively exploited?
No, according to CISA's Known Exploited Vulnerabilities catalog, CVE-2026-46022 is not currently being actively exploited in the wild, and no public exploits are available.
What versions of Kernel are affected by CVE-2026-46022?
Linux kernel versions 6.19 through 7.0.3 are vulnerable; version 7.0.4 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-46022?
Run `uname -r` to view your kernel version; if the output shows a version between 6.19 and 7.0.3, your system is vulnerable. Additionally, check if the ibmasm driver is loaded with `lsmod | grep ibmasm`.
Does Defensia detect CVE-2026-46022?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Linux kernel is installed on a monitored server, CVE-2026-46022 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/07c4f18b303106e6b24492c12b95d48a4b985841
- https://git.kernel.org/stable/c/1ca75f6b74ec7f685464e5745ecfcf3a76d284e9
- https://git.kernel.org/stable/c/22a16d3eafee92a165c756081587c95850127107
- https://git.kernel.org/stable/c/4b6e6ead556734bdc14024c5f837132b1e7a4b84
- https://git.kernel.org/stable/c/6f6ecc9153df176e956d0664b56f93080b0a45f0
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-46022. Free for 1 server.
Get started free