CVE-2026-45994In 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 o…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.1 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Weakness (CWE)
- CWE-125
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jun 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 2.6.12.1 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.140; from 6.7 before 6.12.86; from 6.13 before 6.18.27; from 6.19 before 7.0.4; 2.6.12; and 4 more ranges | NVD |
References
- https://git.kernel.org/stable/c/0eb09f737428e482a32a2e31e5e223f2b35a71d3patch
- https://git.kernel.org/stable/c/44ee19422aa82a6847594866de7e5a31e4ef98b3patch
- https://git.kernel.org/stable/c/7b8a574da5d7ea99b943f7a3458a17a1d95e8838patch
- https://git.kernel.org/stable/c/a672682d39dd34e2b5ba4feb436723bed65125ffpatch
- https://git.kernel.org/stable/c/aefc1a97da17d8309974690c8a03e439a91ebb1cpatch
- https://git.kernel.org/stable/c/d0fb4d1dc43f8d5179917a2daaa82680993d4cdfpatch
- https://git.kernel.org/stable/c/d50e2019c9d7c433f56d9dff65703eb904aa1fb1patch
- https://git.kernel.org/stable/c/ee5737891464030a189837467df3b81a273718adpatch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.