Kernel-memory disclosure via unsanitized GPIO offset
Published Aug 26, 2024 · Updated May 11, 2026
Out-of-bounds read in affected Linux kernels allows local users to disclose kernel memory through a crafted GPIO ioctl offset. gpio_device_get_desc() checks the userspace offset but then uses it directly to index gdev->descs, allowing speculative execution to read past the descriptor array. Ability to issue GPIO ioctls is required, and the published impact is information disclosure without reported integrity or availability effects.
Summary
What happened
Out-of-bounds read in affected Linux kernels allows local users to disclose kernel memory through a crafted GPIO ioctl offset. gpio_device_get_desc() checks the userspace offset but then uses it directly to index gdev->descs, allowing speculative execution to read past the descriptor array. Ability to issue GPIO ioctls is required, and the published impact is information disclosure without reported integrity or availability effects.
The record
- CVE
- CVE-2024-44931
- Published
- Aug 26, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2024CVE 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=4.6
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <18504710442671b02d00e6db9804a0ad26c5a479
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <1b955f786a4bcde8c0ccb2b7d519def2acb6f3cc
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <672c19165fc96dfad531a5458e0b3cdab414aae4
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <9ae2d8e75b741dbcb0da374753f972410e83b5f3
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <9d682e89c44bd5819b01f3fbb45a8e3681a4b6d0
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <c65ab97efcd438cb4e9f299400f2ea55251f3a67
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <d776c0486b03a5c4afca65b8ff44573592bf93bb
- Affected versionversion=521a2ad6f862a28e2e43cb3e254a26bf0f9452e9 <d795848ecce24a75dfd46481aee066ae6fe39775
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.
Weakness, pattern, technique
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