Bug 2389456 (CVE-2025-38556) - CVE-2025-38556 kernel: HID: core: Harden s32ton() against conversion to 0 bits
Summary: CVE-2025-38556 kernel: HID: core: Harden s32ton() against conversion to 0 bits
Keywords:
Status: NEW
Alias: CVE-2025-38556
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-08-19 18:01 UTC by OSIDB Bzimport
Modified: 2025-09-22 14:09 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:16372 0 None None None 2025-09-22 14:09:01 UTC

Description OSIDB Bzimport 2025-08-19 18:01:36 UTC
In the Linux kernel, the following vulnerability has been resolved:

HID: core: Harden s32ton() against conversion to 0 bits

Testing by the syzbot fuzzer showed that the HID core gets a
shift-out-of-bounds exception when it tries to convert a 32-bit
quantity to a 0-bit quantity.  Ideally this should never occur, but
there are buggy devices and some might have a report field with size
set to zero; we shouldn't reject the report or the device just because
of that.

Instead, harden the s32ton() routine so that it returns a reasonable
result instead of crashing when it is called with the number of bits
set to 0 -- the same as what snto32() does.

Comment 3 errata-xmlrpc 2025-09-22 14:09:00 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:16372 https://access.redhat.com/errata/RHSA-2025:16372


Note You need to log in before you can comment on or make changes to this bug.