Vulnerabilities
- CVSS
- 5.5 Medium
- Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Risk score
- 44.0
- Published
- 2026-05-27
- Status
- Published
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.
A flaw was found in the Linux kernel's ibmasm module. A local root user can exploit a heap over-read vulnerability within the `ibmasm_send_i2o_message()` function. This vulnerability arises from insufficient validation of user-controlled input sizes, allowing the system to read beyond allocated memory. Such an exploit could lead to the disclosure of sensitive kernel heap information and potentially cause the service processor to desynchronize, impacting overall system stability.
Coverage 7
threat-intel
Multiple vulnerabilities have been discovered in the Linux kernel of SUSE. Several of these vulnerabilities allow for privilege escalation, data confidentiality breaches, and data integrity issues. These vulnerabilities…
vulnerability
Multiple vulnerabilities have been discovered in the Linux kernel of Ubuntu. Some of these vulnerabilities allow for privilege escalation, data confidentiality compromise, and data integrity compromise. These vulnerabili…
threat-intel
Multiple vulnerabilities have been discovered in the SUSE Linux kernel. Several of these vulnerabilities can lead to privilege escalation, denial of service, and data confidentiality breaches. The vulnerabilities are bei…
vulnerability
Multiple vulnerabilities have been discovered in the Linux kernel of Ubuntu. Several of these vulnerabilities allow for privilege escalation, data confidentiality breaches, and a security issue not specified by the publi…
vulnerability
Multiple vulnerabilities have been discovered in the Linux kernel of Ubuntu. Some of these vulnerabilities allow for privilege escalation, data confidentiality breaches, and data integrity compromise. These vulnerabiliti…
vulnerability
Multiple vulnerabilities have been discovered in the SUSE Linux kernel. Some of these vulnerabilities allow for data confidentiality and integrity breaches, as well as bypassing security policies and causing denial of se…
threat-intel
Multiple vulnerabilities have been discovered in the Linux kernel of Ubuntu. Some of these vulnerabilities allow for privilege escalation, data confidentiality breaches, and denial of service attacks. The vulnerabilities…
Advisories and references