Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-46022misc: ibmasm: fix OOB MMIO read in ibmasm_handle_mouse_interrupt()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46022, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < 6f6ecc9153df176e956d0664b56f93080b0a45f0
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < bac8643486f854dd53af9b23aea7dbbd9b7c1865
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < f7e5b4eefd7be3e09f8bd5fee63ed478fd7446ab
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < fc7e9a74e32299d7e93e178ca482a0b59ef1595b
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < 07c4f18b303106e6b24492c12b95d48a4b985841
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < 22a16d3eafee92a165c756081587c95850127107
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < 1ca75f6b74ec7f685464e5745ecfcf3a76d284e9
    • affected 278d72ae8803ffcd16070c95fe1d53f4466dc741 – < 4b6e6ead556734bdc14024c5f837132b1e7a4b84
  • Linux · Linux

    • affected 2.6.13
    • unaffected < 2.6.13
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46022 badge
[![CVE-2026-46022](https://cveledger.app/badge/CVE-2026-46022.svg)](https://cveledger.app/cve/CVE-2026-46022)

Record last updated .