HID: core: clamp report_size in s32ton() to avoid undefined shift
- 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 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, and 3 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
Summary
In the Linux kernel, the following vulnerability has been resolved: HID: core: clamp report_size in s32ton() to avoid undefined shift s32ton() shifts by n-1 where n is the field's report_size, a value that comes directly from a HID device. The HID parser bounds report_size only to <= 256, so a broken HID device can supply a report descriptor with a wide field that triggers shift exponents up to 256 on a 32-bit type when an output report is built via hid_output_field() or hid_set_field(). Commit ec61b41918587 ("HID: core: fix shift-out-of-bounds in hid_report_raw_event") added the same n > 32 clamp to the function snto32(), but s32ton() was never given the same fix as I guess syzbot hadn't figured out how to fuzz a device the same way. Fix this up by just clamping the max value of n, just like snto32() does.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 76ad02854a30c394e0c076e6e6bed0a388573a94; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in eb415ddaf25e09ddb8fe5736a70c9de2e6462534; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 0ab048dbdb1daacf17d52e9252297eb6e1298e49; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 932ae5309e53561197aa7d1606c7cf63af10e24f; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 58386f00af710922cafb0fb69211497beddfaa95; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 8a8333237f1f5caab8d4c3d2c2e7578c4263a97f; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in ea363a34086ddb4231adc581a7f36c39ec154bfc; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 97014719bb8fccb1ffcbbc299e84b1f11b114195; From dde5845a529ff753364a6d1aea61180946270bfa · fixed in 69c02ffde6ed4d535fa4e693a9e572729cad3d0d
- Linux Linux
2.6.20
- KernelLinux
From 2.6.20 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.136; From 6.7.0 · fixed in 6.12.83; From 6.13.0 · fixed in 6.18.24; From 6.19.0 · fixed in 6.19.14; From 6.20.0 · fixed in 7.0.1
References 9
git.kernel.org
- stable/c/76ad02854a30c394e0c076e6e6bed0a388573a94
- stable/c/eb415ddaf25e09ddb8fe5736a70c9de2e6462534
- stable/c/0ab048dbdb1daacf17d52e9252297eb6e1298e49
- stable/c/932ae5309e53561197aa7d1606c7cf63af10e24f
- stable/c/58386f00af710922cafb0fb69211497beddfaa95
- stable/c/8a8333237f1f5caab8d4c3d2c2e7578c4263a97f
- stable/c/ea363a34086ddb4231adc581a7f36c39ec154bfc
- stable/c/97014719bb8fccb1ffcbbc299e84b1f11b114195
- stable/c/69c02ffde6ed4d535fa4e693a9e572729cad3d0d