HID: core: zero-initialize the report buffer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 3.11, 3.12, 4.19.324, 5.4.286, 5.10.230, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: active
- Automatable: no
- Technical impact: partial
Summary
The Linux kernel's HID (Human Interface Device) core subsystem, which handles input devices such as keyboards, mice, and game controllers, is affected. The report buffer it allocates was not zero-initialized, so a specially crafted device report could potentially expose leftover kernel memory contents.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA SSVC assessment
Exploitation: active · Automatable: no · Technical impact: partial
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Linux Linux
From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in e7ea60184e1e88a3c9e437b3265cbb6439aa7e26; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in 3f9e88f2672c4635960570ee9741778d4135ecf5; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in d7dc68d82ab3fcfc3f65322465da3d7031d4ab46; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in 05ade5d4337867929e7ef664e7ac8e0c734f1aaf; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in 1884ab3d22536a5c14b17c78c2ce76d1734e8b0b; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in 9d9f5c75c0c7f31766ec27d90f7a6ac673193191; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in 492015e6249fbcd42138b49de3c588d826dd9648; From 27ce405039bfe6d3f4143415c638f56a3df77dca · fixed in 177f25d1292c7e16e1199b39c85480f7f8815552; From 3.10.16 · fixed in 3.11; From 3.11.5 · fixed in 3.12
- Linux Linux
3.12
- KernelLinux
From 3.12.0 · fixed in 4.19.324; From 4.20.0 · fixed in 5.4.286; From 5.5.0 · fixed in 5.10.230; From 5.11.0 · fixed in 5.15.172; From 5.16.0 · fixed in 6.1.117; From 6.2.0 · fixed in 6.6.61; From 6.7.0 · fixed in 6.11.8
- :linux_kernel:Android
From :0 · fixed in :2025-03-05
References 8
git.kernel.org
- stable/c/e7ea60184e1e88a3c9e437b3265cbb6439aa7e26
- stable/c/3f9e88f2672c4635960570ee9741778d4135ecf5
- stable/c/d7dc68d82ab3fcfc3f65322465da3d7031d4ab46
- stable/c/05ade5d4337867929e7ef664e7ac8e0c734f1aaf
- stable/c/1884ab3d22536a5c14b17c78c2ce76d1734e8b0b
- stable/c/9d9f5c75c0c7f31766ec27d90f7a6ac673193191
- stable/c/492015e6249fbcd42138b49de3c588d826dd9648
- stable/c/177f25d1292c7e16e1199b39c85480f7f8815552