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-2026-52948i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl

Description

In the Linux kernel, the following vulnerability has been resolved: i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl While fuzzing with Syzkaller, a persistent `schedule_timeout: wrong timeout value` warning was observed, accompanied by SMBus controller state machine corruption. The I2C_TIMEOUT ioctl accepts a user-provided timeout in multiples of 10 ms. The user argument is checked against INT_MAX, but it is subsequently multiplied by 10 before being passed to msecs_to_jiffies(). A malicious user can pass a large value (e.g., 429496729) that passes the `arg > INT_MAX` check but overflows when multiplied by 10. This results in a truncated 32-bit unsigned value that bypasses the internal `(int)m < 0` check in `msecs_to_jiffies()`. The truncated value is then assigned to `client->adapter->timeout` (a signed 32-bit int), which is reinterpreted as a negative number. When passed to wait_for_completion_timeout(), this negative value undergoes sign extension to a 64-bit unsigned long, triggering the `schedule_timeout` warning and causing premature returns. This leaves the SMBus state machine in an unrecoverable state, constituting a local Denial of Service (DoS). Fix this by bounding the user argument to `INT_MAX / 10`. [wsa: move the comment as well]

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-2026-52948, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < e9ffd5f5050fbb199d270a85614cd27ebed6fbac
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < 0b88ecfbc9dc33b4db8836c37b50cf174e6c0691
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < 943e318eedbeaeea08ece3f5dd44c982f4ed2ef5
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < aa6ef734016912653a909477fb30aeb66c98b3a2
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < ff02add34ffd03449b8115904ebe2ec4fed022d4
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < ffbcf31f032eb454ebfd29309f51366fe57f4ac4
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < 4576621dc6577f21a032acfd16c3ad61907a5ea7
    • affected cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d – < 617eb7c0961a8dfcfc811844a6396e406b2923ea
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .