CVE-2026-45994

ibmasm: fix OOB reads in command_file_write due to missing size checks

HIGH
7.1
CVSS Score
Published: May 27, 2026 at 12:55 PM UTC
Updated: June 17, 2026 at 10:52 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2582.6.12 ≤ v < 5.15.2092.6.12 ≤ v < 6.1.1752.6.12 ≤ v < 6.12.862.6.12 ≤ v < 6.18.272.6.12 ≤ v < 6.6.1402.6.12 ≤ v < 7.0.42.6.12 ≤ v < 7.12.6.12.1 ≤ v < 5.10.2585.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1756.13 ≤ v < 6.18.276.19 ≤ v < 7.0.46.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.861da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.122.6.12 rc22.6.12 rc32.6.12 rc42.6.12 rc5
Vendor states this is fixed in 0eb09f737428e482a32a2e31e5e223f2b35a71d3 (fixed)
Vendor states this is fixed in 44ee19422aa82a6847594866de7e5a31e4ef98b3 (fixed)
Vendor states this is fixed in 7b8a574da5d7ea99b943f7a3458a17a1d95e8838 (fixed)
Vendor states this is fixed in a672682d39dd34e2b5ba4feb436723bed65125ff (fixed)
Vendor states this is fixed in aefc1a97da17d8309974690c8a03e439a91ebb1c (fixed)
Vendor states this is fixed in d0fb4d1dc43f8d5179917a2daaa82680993d4cdf (fixed)
Vendor states this is fixed in d50e2019c9d7c433f56d9dff65703eb904aa1fb1 (fixed)
Vendor states this is fixed in ee5737891464030a189837467df3b81a273718ad (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.86 (unaffected)
Vendor states this is fixed in 6.18.27 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.4 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card