Remote kernel-memory disclosure via zero-length ATOMIC_WRITE
Published May 28, 2026 · Updated May 28, 2026
Out-of-bounds read in Linux Kernel allows remote attackers to disclose kernel memory via a zero-length Soft-RoCE ATOMIC_WRITE request. check_rkey() accepts a request whose packet length and RETH length are both zero, after which atomic_write_reply() unconditionally reads eight bytes past the logical payload and copies them to the initiator's memory region. Exposure requires an active RDMA_RXE responder and a usable remote key; each repeatable probe returns four bytes of adjacent kernel tailroom while leaving target integrity and availability unchanged.
Summary
What happened
Out-of-bounds read in Linux Kernel allows remote attackers to disclose kernel memory via a zero-length Soft-RoCE ATOMIC_WRITE request. check_rkey() accepts a request whose packet length and RETH length are both zero, after which atomic_write_reply() unconditionally reads eight bytes past the logical payload and copies them to the initiator's memory region. Exposure requires an active RDMA_RXE responder and a usable remote key; each repeatable probe returns four bytes of adjacent kernel tailroom while leaving target integrity and availability unchanged.
The record
- CVE
- CVE-2026-46114
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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=034e285f8b99062a0cf29112e1232154a6a44aa5 <105bf79a23b85cf3a761d18a4f3e10ce88526bc1
- Affected versionversion=034e285f8b99062a0cf29112e1232154a6a44aa5 <1114c87aa6f195cf07da55a27b2122ae26557b26
- Affected versionversion=034e285f8b99062a0cf29112e1232154a6a44aa5 <539cabb7b2d8ba70f55bba91db55faef11c2a6d7
- Affected versionversion=034e285f8b99062a0cf29112e1232154a6a44aa5 <7ec1ed4747f5f99f8b797bb438c5efd36079fad5
- Affected versionversion=034e285f8b99062a0cf29112e1232154a6a44aa5 <d415fce3fcde6d7aeea6c25362a395b905811452
- Affected versionversion=6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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