HID: haptic: don't write an uninitialized value to unhandled usages
- 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? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.52, 7.2.6
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: HID: haptic: don't write an uninitialized value to unhandled usages fill_effect_buf() initializes value only for the four haptic usages handled by its switch, but writes it to field->value[] for every usage. An unhandled usage can therefore receive either an uninitialized value or one left over from the previous usage. hid_output_report() then serializes that value into the effect's report buffer. Skip unhandled usages instead. This also matches switch_mode(), which only updates fields it recognizes. Found with Clang's -Wconditional-uninitialized.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 344ff358495706abc7aac1e0c59a5bb16b350307 · fixed in 324cc98b71f0d3dee7367ef3c669fd80747e71b6; From 344ff358495706abc7aac1e0c59a5bb16b350307 · fixed in 2d92c250815cba6bffd64f0125fac7afe4fa6ce0; From 344ff358495706abc7aac1e0c59a5bb16b350307 · fixed in 3efb7f6491526f5012f9ec94769e9ed832feeef8
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6