Local denial of service via HID buffer leak
Published Apr 22, 2026 · Updated Apr 22, 2026
Memory leak in the ASUS HID driver in Linux Kernel allows local users to exhaust kernel memory through repeated device initialization. The asus_report_fixup() function returns a newly allocated kmemdup() buffer to a caller that does not take ownership, so each affected initialization permanently retains the allocation. Exploitation requires local low-privileged access and an affected ASUS HID path; the documented security impact is loss of availability, while the accompanying descriptor over-read is described as harmless.
Summary
What happened
Memory leak in the ASUS HID driver in Linux Kernel allows local users to exhaust kernel memory through repeated device initialization. The asus_report_fixup() function returns a newly allocated kmemdup() buffer to a caller that does not take ownership, so each affected initialization permanently retains the allocation. Exploitation requires local low-privileged access and an affected ASUS HID path; the documented security impact is loss of availability, while the accompanying descriptor over-read is described as harmless.
The record
- CVE
- CVE-2026-31524
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 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 <2bad24c17742fc88973d6aea526ce1353f5334a3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2e4fe6b15c2f390c023b20d728b1a3fe7ea4f973
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <726765b43deb2b4723869d673cc5fc6f7a3b2059
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7a6d6e4d8af044f94fa97e97af5ff2771e1fbebd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <84724ac4821a160d47b84289adf139023027bdbb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a41cc7c1668e44ff2c2d36f9a6353253ffc43e3c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ede95cfcab8064d9a08813fbd7ed42cea8843dcf
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f20f17cffbe34fb330267e0f8084f5565f807444
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