CVE Intelligence
Medium Memory corruption

CVE-2026-52948 — i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl

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]

Published Jun 24, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.13%
ahead of 2% of scored CVEs · Oct 14, 2026
Affects
Linux
Linux and 1 more
CVSS base
5.5
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 2.6.29≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < 617eb7c0961a8dfcfc811844a6396e406b2923ea≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < 4576621dc6577f21a032acfd16c3ad61907a5ea7≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < ffbcf31f032eb454ebfd29309f51366fe57f4ac4≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < ff02add34ffd03449b8115904ebe2ec4fed022d4≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < aa6ef734016912653a909477fb30aeb66c98b3a2≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < 943e318eedbeaeea08ece3f5dd44c982f4ed2ef5≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < 0b88ecfbc9dc33b4db8836c37b50cf174e6c0691
and 1 more ≥ cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d and < e9ffd5f5050fbb199d270a85614cd27ebed6fbac
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel version 7.1-rc1version 7.1-rc2≥ 2.6.29.1 and < 5.10.259version 2.6.29-rc8version 2.6.29-rc7version 2.6.29≥ 6.19 and < 7.0.13≥ 6.13 and < 6.18.36
and 4 more ≥ 6.7 and < 6.12.94≥ 6.2 and < 6.6.143≥ 5.16 and < 6.1.176≥ 5.11 and < 5.15.210
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.5 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-190 · Integer Overflow or Wraparound

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.13%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Analyzed → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jun 24, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

Linux
every CVE for this vendor
Memory corruption
same class
CWE-190
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 12h
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 12h
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-52948 is "i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.