Kernel-memory exhaustion via leaked report descriptor
Published Apr 22, 2026 · Updated Apr 22, 2026
Memory leak in the Linux kernel HID magicmouse driver allows local users to exhaust kernel memory through repeated device initialization. The magicmouse_report_fixup() function returns a newly kmemdup()-allocated report-descriptor buffer even though report_fixup() callers do not take ownership, leaving each allocation unreleased. Exploitation requires local low-privileged access; the resulting resource loss affects availability, with no reported ability to read or modify data.
Summary
What happened
Memory leak in the Linux kernel HID magicmouse driver allows local users to exhaust kernel memory through repeated device initialization. The magicmouse_report_fixup() function returns a newly kmemdup()-allocated report-descriptor buffer even though report_fixup() callers do not take ownership, leaving each allocation unreleased. Exploitation requires local low-privileged access; the resulting resource loss affects availability, with no reported ability to read or modify data.
The record
- CVE
- CVE-2026-31522
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.004
- 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 <136f605e246b4bfe7ac2259471d1ff814aed0084
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <579c4c9857acdc8380fa99803f355f878bd766cb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <79e5dcc95d9abed6f8203cfd529f4ec71f0e505d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7edfe4346b052b708645d0acc0f186425766b785
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <91e8c6e601bdc1ccdf886479b6513c01c7e51c2c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d84c21aabaab517b9aaf9bc1d785922cb9db2f31
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fa95b0146358b49f9858139b67314591fd5871b0
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