HID: core: clamp report_size in s32ton() to avoid undefined shift
Summary
| CVE | CVE-2026-31624 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-24 15:16:41 UTC |
| Updated | 2026-04-24 17:51:40 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 58386f00af710922cafb0fb69211497beddfaa95 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 8a8333237f1f5caab8d4c3d2c2e7578c4263a97f git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 ea363a34086ddb4231adc581a7f36c39ec154bfc git |
Not specified |
| CNA |
Linux |
Linux |
affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 97014719bb8fccb1ffcbbc299e84b1f11b114195 git |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.83 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.24 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.14 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.1 7.0.* semver |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/ea363a34086ddb4231adc581a7f36c39ec154bfc |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8a8333237f1f5caab8d4c3d2c2e7578c4263a97f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/58386f00af710922cafb0fb69211497beddfaa95 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/97014719bb8fccb1ffcbbc299e84b1f11b114195 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.