UBUNTU-CVE-2026-46022 (CVE-2026-46022)

Vulnerability from osv_ubuntu – Published: 2026-05-27 14:17 – Updated: 2026-11-19 03:59 – Source website
VLAI
Details

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.

References
https://ubuntu.com/security/CVE-2026-46022 REPORT
https://www.cve.org/CVERecord?id=CVE-2026-46022 REPORT
https://git.kernel.org/linus/4b6e6ead556734bdc140… REPORT
https://ubuntu.com/security/notices/USN-8488-1 ADVISORY
https://ubuntu.com/security/notices/USN-8489-1 ADVISORY
https://ubuntu.com/security/notices/USN-8488-2 ADVISORY
https://ubuntu.com/security/notices/USN-8507-1 ADVISORY
https://ubuntu.com/security/notices/USN-8569-1 ADVISORY
https://ubuntu.com/security/notices/USN-8567-1 ADVISORY
https://ubuntu.com/security/notices/USN-8574-1 ADVISORY
https://ubuntu.com/security/notices/USN-8575-1 ADVISORY
https://ubuntu.com/security/notices/USN-8576-1 ADVISORY
https://ubuntu.com/security/notices/USN-8574-2 ADVISORY
https://ubuntu.com/security/notices/USN-8595-1 ADVISORY
https://ubuntu.com/security/notices/USN-8596-1 ADVISORY
https://ubuntu.com/security/notices/USN-8575-2 ADVISORY
https://ubuntu.com/security/notices/USN-8576-2 ADVISORY
https://ubuntu.com/security/notices/USN-8597-1 ADVISORY
https://ubuntu.com/security/notices/USN-8603-1 ADVISORY
https://ubuntu.com/security/notices/USN-8595-2 ADVISORY
https://ubuntu.com/security/notices/USN-8606-1 ADVISORY
https://ubuntu.com/security/notices/USN-8607-1 ADVISORY
https://ubuntu.com/security/notices/USN-8608-1 ADVISORY
https://ubuntu.com/security/notices/USN-8609-1 ADVISORY
https://ubuntu.com/security/notices/USN-8575-3 ADVISORY
https://ubuntu.com/security/notices/USN-8610-1 ADVISORY
https://ubuntu.com/security/notices/USN-8574-3 ADVISORY
https://ubuntu.com/security/notices/USN-8595-3 ADVISORY
https://ubuntu.com/security/notices/USN-8619-1 ADVISORY
https://ubuntu.com/security/notices/USN-8620-1 ADVISORY
https://ubuntu.com/security/notices/USN-8620-2 ADVISORY
https://ubuntu.com/security/notices/USN-8620-3 ADVISORY
https://ubuntu.com/security/notices/USN-8620-4 ADVISORY
https://ubuntu.com/security/notices/USN-8665-1 ADVISORY
https://ubuntu.com/security/notices/USN-8668-1 ADVISORY
https://ubuntu.com/security/notices/USN-8668-2 ADVISORY

Loading 1.0 MB of JSON…



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.