CVE-2026-45994: ibmasm: fix OOB reads in command_file_write due to missing size checks
In the Linux kernel, the following vulnerability has been resolved:
ibmasm: fix OOB reads in command_file_write due to missing size checks
The command_file_write() handler allocates a kernel buffer of exactly
count bytes and copies user data into it, but does not validate the
buffer against the dot command protocol before passing it to
get_dot_command_size() and get_dot_command_timeout().
Since both the allocation size (count) and the header fields (command_size,
data_size) are independently user-controlled, an attacker can cause
get_dot_command_size() to return a value exceeding the allocation,
triggering OOB reads in get_dot_command_timeout() and an out-of-bounds
memcpy_toio() that leaks kernel heap memory to the service processor.
Fix with two guards: reject writes smaller than sizeof(struct
dot_command_header) before allocation, then after copying user data
reject commands where the buffer is smaller than the total size declared
by the header (sizeof(header) + command_size + data_size). This ensures
all subsequent header and payload field accesses stay within the buffer.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in the ibmasm command write path. A malformed command can make the kernel read beyond a user-supplied buffer and copy unintended kernel heap data to the service processor. Business risk depends on whether affected systems run the ibmasm driver and expose its command interface.
Executive priority
Treat this as a targeted kernel update item, not a confirmed emergency. Move faster for infrastructure where ibmasm is used or where untrusted local users can reach the host. Severity is not scored in the sources.
Technical view
command_file_write() allocated count bytes, copied user data, then trusted dot-command header sizes without verifying the buffer covered the declared header, command, and data lengths. The fix rejects too-small writes and rejects buffers smaller than sizeof(header) plus command_size plus data_size before timeout parsing or memcpy_toio().
Likely exposure
Exposure is likely limited to Linux systems with affected kernel versions and the ibmasm driver path in use. The provided sources do not define required privileges, device-node permissions, remote reachability, or whether the driver is loaded by default.
Exploitation context
The source bundle says KEV is false and provides no cited evidence of active exploitation. The described impact is out-of-bounds reads and potential kernel heap memory leakage to the service processor, not arbitrary code execution.
Researcher notes
The useful boundary is reachability of command_file_write() and whether user-controlled count and header sizes can pass into dot-command parsing. The public bundle does not provide exploit status, privilege requirements, CWE mapping, or distribution-specific fixed package versions.
Mitigation direction
Check vendor or distribution kernel advisories for fixed packages containing the referenced stable commits.
Prioritize systems using the ibmasm driver or IBM service processor management features.
Apply kernel updates through normal distribution channels after compatibility testing.
Restrict access to the ibmasm command interface according to vendor guidance.
If no update is available, ask the vendor for supported mitigation options.
Validation and detection
Inventory kernels and confirm whether affected versions listed in the CVE bundle are present.
Check whether the ibmasm driver is installed, loaded, or required on each system.
Verify patched kernels include one of the referenced stable fix commits or downstream equivalents.
Review device permissions and operational access controls for the ibmasm command interface.
Confirm no compensating control is treated as a permanent replacement for patching.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-45994 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.