CVE-2026-46022

misc: ibmasm: fix OOB MMIO read in ibmasm_handle_mouse_interrupt()

HIGH
7.1
CVSS Score
Published: May 27, 2026 at 12:56 PM UTC
Updated: October 15, 2026 at 02:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.13 ≤ v < 5.10.2585.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1756.13 ≤ v < 6.18.276.19 ≤ v < 7.0.46.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.862.6.13278d72ae8803ffcd16070c95fe1d53f4466dc741
Vendor states this is fixed in 07c4f18b303106e6b24492c12b95d48a4b985841 (fixed)
Vendor states this is fixed in 1ca75f6b74ec7f685464e5745ecfcf3a76d284e9 (fixed)
Vendor states this is fixed in 22a16d3eafee92a165c756081587c95850127107 (fixed)
Vendor states this is fixed in 4b6e6ead556734bdc14024c5f837132b1e7a4b84 (fixed)
Vendor states this is fixed in 6f6ecc9153df176e956d0664b56f93080b0a45f0 (fixed)
Vendor states this is fixed in bac8643486f854dd53af9b23aea7dbbd9b7c1865 (fixed)
Vendor states this is fixed in f7e5b4eefd7be3e09f8bd5fee63ed478fd7446ab (fixed)
Vendor states this is fixed in fc7e9a74e32299d7e93e178ca482a0b59ef1595b (fixed)
Vendor states this is fixed in 2.6.13 (unaffected)
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.86 (unaffected)
Vendor states this is fixed in 6.18.27 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.4 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card