CVE-2026-45994 json
ibmasm: fix OOB reads in command_file_write due to missing size checks
published 2026-05-27 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-32290
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.86-1
- linux Debian 14 7.0.4-1
debian advisories DEBIAN-CVE-2026-45994
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-27.27
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
ubuntu advisories UBUNTU-CVE-2026-45994
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-51.1
- kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.37.1
- kernel-rt Linux Micro 6.2 6.12.0-160000.37.1
- kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.37.1
suse advisories SUSE-SU-2026:23244-1SUSE-SU-2026:23241-1SUSE-SU-2026:23194-1SUSE-SU-2026:23193-1SUSE-SU-2026:3594-1SUSE-SU-2026:23237-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.37.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.37.1
opensuse advisories openSUSE-SU-2026:21555-1openSUSE-SU-2026:10954-1
- git.kernel.org/stable/c/44ee19422aa82a6847594866de7e5a31e4ef98b3 commit
- git.kernel.org/stable/c/7b8a574da5d7ea99b943f7a3458a17a1d95e8838 commit
- git.kernel.org/stable/c/d50e2019c9d7c433f56d9dff65703eb904aa1fb1 commit
- git.kernel.org/stable/c/a672682d39dd34e2b5ba4feb436723bed65125ff commit
- git.kernel.org/stable/c/aefc1a97da17d8309974690c8a03e439a91ebb1c commit
- git.kernel.org/stable/c/ee5737891464030a189837467df3b81a273718ad commit
- git.kernel.org/stable/c/d0fb4d1dc43f8d5179917a2daaa82680993d4cdf commit
- git.kernel.org/stable/c/0eb09f737428e482a32a2e31e5e223f2b35a71d3 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-45994 updated cvss 5.5
kernel: ibmasm: fix OOB reads in command_file_write due to missing size checks
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/44ee19422aa82a6847594866de7e5a31e4ef98b3
patch
-
git.kernel.org
/stable/c/7b8a574da5d7ea99b943f7a3458a17a1d95e8838
patch
-
git.kernel.org
/stable/c/d50e2019c9d7c433f56d9dff65703eb904aa1fb1
patch
-
git.kernel.org
/stable/c/a672682d39dd34e2b5ba4feb436723bed65125ff
patch
-
git.kernel.org
/stable/c/aefc1a97da17d8309974690c8a03e439a91ebb1c
patch
-
git.kernel.org
/stable/c/ee5737891464030a189837467df3b81a273718ad
patch
-
git.kernel.org
/stable/c/d0fb4d1dc43f8d5179917a2daaa82680993d4cdf
patch
-
git.kernel.org
/stable/c/0eb09f737428e482a32a2e31e5e223f2b35a71d3
patch
Sources
- CVE List CVE-2026-45994
- NVD CVE-2026-45994
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.