Menu

Star on GitHub · 3.2k

CVE-2026-46064

7.1 · HIGH

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 c…

Published May 27, 2026CWE-125EPSS 0.17%

Overview

CVE-2026-46064 is a high-severity vulnerability. It was published on May 27, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 l

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-46064?

CVE-2026-46064 is a high-severity vulnerability. It was published on May 27, 2026 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2026-46064?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-46064?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-46064?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-46064 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all