CVE-2026-46064 ibmasm: fix heap over-read in ibmasm_send_i2o_message()
A local root user can trigger a heap over-read in the ibmasm driver, leaking kernel memory to the service processor.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-46064?
CVE-2026-46064 is a high-severity vulnerability in Linux kernel, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
ibmasm: fix heap over-read in ibmasm_send_i2o_message()
The ibmasm_send_i2o_message() function uses get_dot_command_size() to compute the byte count for memcpy_toio(), but this value is derived from user-controlled fields in the dot_command_header (command_size: u8, data_size: u16) and is never validated against the actual allocation size. A root user can write a small buffer with inflated header fields, causing memcpy_toio() to read up to ~65 KB past the end of the allocation into adjacent kernel heap, which is then forwarded to the service processor over MMIO.
Silently clamping the copy size is not sufficient: if the header fields claim a larger size than the buffer, the SP receives a dot command whose own header is inconsistent with the I2O message length, which can cause the SP to desynchronize. Reject such commands outright by returning failure.
Validate command_size before calling get_mfa_inbound() to avoid leaking an I2O message frame: reading INBOUND_QUEUE_PORT dequeues a hardware frame from the controller's free pool, and returning without a corresponding set_mfa_inbound() call would permanently exhaust it.
Additionally, clamp command_size to I2O_COMMAND_SIZE before the memcpy_toio() so the MMIO write stays within the I2O message frame, consistent with the clamping already performed by outgoing_message_size() for the header field.
Weakness: CWE-125
Which versions are affected by CVE-2026-46064?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2026-46064?
Apply the vendor's patch.
Is CVE-2026-46064 being exploited?
There is no known exploitation of CVE-2026-46064 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-88634, BELL-CVE-2026-46064, DEBIAN-CVE-2026-46064, GHSA-4p2m-h7j8-hhxj, ROOT-OS-DEBIAN-11-CVE-2026-46064, ROOT-OS-DEBIAN-12-CVE-2026-46064 and 3 more.