Kernel-memory disclosure via speculative ioctl table indexing
Published Feb 26, 2025 · Updated May 11, 2026
Information disclosure in Linux kernel device-mapper ioctl handling allows local users to read kernel memory through speculative execution. The lookup_ioctl function bounds-checks a user-derived cmd value, then indexes the _ioctls table without constraining speculative execution. Exploitation requires local access and the ability to issue device-mapper ioctls; the bounded consequence is disclosure of kernel-memory contents to user space.
Summary
What happened
Information disclosure in Linux kernel device-mapper ioctl handling allows local users to read kernel memory through speculative execution. The lookup_ioctl function bounds-checks a user-derived cmd value, then indexes the _ioctls table without constraining speculative execution. Exploitation requires local access and the ability to issue device-mapper ioctls; the bounded consequence is disclosure of kernel-memory contents to user space.
The record
- CVE
- CVE-2022-49122
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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 <02cc46f397eb3691c56affbd5073e54f7a82ac32
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0320bac5801b31407200227173205d017488f140
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <44e6cb3ab177faae840bb2c1ebda9a2539876184
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <58880025e3362024f6d8ea01cb0c7a5df6c84ba6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <71c8df33fd777c7628f6fbc09b14e84806c55914
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <76c94651005f58885facf9c973007f5ea01ab01f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7ae2c5b89da3cfaf856df880af27d3bb32a74b3d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cd9c88da171a62c4b0f1c70e50c75845969fbc18
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dd86064417de828ff2102ddc6049c829bf7585b4
- Affected versionversion=2.6.12
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.
Weakness, pattern, technique
No sourced classifications are available.
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