Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38556HID: core: Harden s32ton() against conversion to 0 bits

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38556, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected dde5845a529ff753364a6d1aea61180946270bfa – < 6cdf6c708717c5c6897d0800a1793e83757c7491
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < eeeaba737919bdce9885e2a00ac2912f61a3684d
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < 3c86548a20d7bc2861aa4de044991a327bebad1a
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < 810189546cb6c8f36443ed091d91f1f5d2fc2ec7
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < d3b504146c111548ab60b6ef7aad00bfb1db05a2
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < 8b4a94b1510f6a46ec48494b52ee8f67eb4fc836
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < 865ad8469fa24de1559f247d9426ab01e5ce3a56
    • affected dde5845a529ff753364a6d1aea61180946270bfa – < a6b87bfc2ab5bccb7ad953693c85d9062aef3fdd
  • Linux · Linux

    • affected 2.6.20
    • unaffected < 2.6.20
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.119 – ≤ 6.6.*
    • unaffected 6.12.46 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38556 badge
[![CVE-2025-38556](https://cveledger.app/badge/CVE-2025-38556.svg)](https://cveledger.app/cve/CVE-2025-38556)

Record last updated .