Kernel memory corruption via unchecked MW indexing
Published May 6, 2026 · Updated May 6, 2026
Out-of-bounds write in the Linux Kernel Switchtec NTB driver allows attackers to corrupt kernel memory during driver initialization. In switchtec_ntb_init_shared(), each LUT position is added to nr_direct_mw and used to write mw_sizes[idx] without first rejecting an index at or above MAX_MWS. Reachability requires Switchtec NTB hardware and a configuration whose direct and LUT windows reach the array limit; public sources do not establish that local users control this configuration.
Summary
What happened
Out-of-bounds write in the Linux Kernel Switchtec NTB driver allows attackers to corrupt kernel memory during driver initialization. In switchtec_ntb_init_shared(), each LUT position is added to nr_direct_mw and used to write mw_sizes[idx] without first rejecting an index at or above MAX_MWS. Reachability requires Switchtec NTB hardware and a configuration whose direct and LUT windows reach the array limit; public sources do not establish that local users control this configuration.
The record
- CVE
- CVE-2026-43241
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0e930420945106151c6eb3d7837b4e6154e9b144
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2346856b74823a2a78109002e479a3d02526a9ce
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <348e1ac9ad983ed7e62de14e1daf47f1695a4ce9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47ce292dd45dc689747c40603222691638919189
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <740945de896021b9a859e71f38f6aea72a6393cf
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <85c9daa1f8319bbb3dfee71dc6a2f969cd3b4c92
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8ba7ad2cc1c7b90570aa347b8ebbe279f1eface
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee02c4f980c91820845dd8e469ec7dc670ab6d9d
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo