misc: ibmasm: fix OOB MMIO read in ibmasm_handle_mouse_interrupt()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in 6f6ecc9153df176e956d0664b56f93080b0a45f0; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in bac8643486f854dd53af9b23aea7dbbd9b7c1865; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in f7e5b4eefd7be3e09f8bd5fee63ed478fd7446ab; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in fc7e9a74e32299d7e93e178ca482a0b59ef1595b; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in 07c4f18b303106e6b24492c12b95d48a4b985841; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in 22a16d3eafee92a165c756081587c95850127107; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in 1ca75f6b74ec7f685464e5745ecfcf3a76d284e9; From 278d72ae8803ffcd16070c95fe1d53f4466dc741 · fixed in 4b6e6ead556734bdc14024c5f837132b1e7a4b84
- Linux Linux
2.6.13
- KernelLinux
From 2.6.13 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.86; From 6.13.0 · fixed in 6.18.27; From 6.19.0 · fixed in 7.0.4
References 8
git.kernel.org
- stable/c/6f6ecc9153df176e956d0664b56f93080b0a45f0
- stable/c/bac8643486f854dd53af9b23aea7dbbd9b7c1865
- stable/c/f7e5b4eefd7be3e09f8bd5fee63ed478fd7446ab
- stable/c/fc7e9a74e32299d7e93e178ca482a0b59ef1595b
- stable/c/07c4f18b303106e6b24492c12b95d48a4b985841
- stable/c/22a16d3eafee92a165c756081587c95850127107
- stable/c/1ca75f6b74ec7f685464e5745ecfcf3a76d284e9
- stable/c/4b6e6ead556734bdc14024c5f837132b1e7a4b84