Heimdall Security Logo

CVE-2026-52948

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : <=6.1.*, <2.6.29, <=7.0.*, <=6.12.*, 6.12.94, <943e318eedbeaeea08ece3f5dd44c982f4ed2ef5, 0, <4576621dc6577f21a032acfd16c3ad61907a5ea7, <ffbcf31f032eb454ebfd29309f51366fe57f4ac4, 6.1.176, 5.15.210, 2.6.29, <=5.10.*, <=6.6.*, 7.0.13, <aa6ef734016912653a909477fb30aeb66c98b3a2, 6.18.36, cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d, <ff02add34ffd03449b8115904ebe2ec4fed022d4, 7.1, <0b88ecfbc9dc33b4db8836c37b50cf174e6c0691, <=6.18.*, <617eb7c0961a8dfcfc811844a6396e406b2923ea, <=*, <=5.15.*, <e9ffd5f5050fbb199d270a85614cd27ebed6fbac, 6.6.143, 5.10.259

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]

Gravité et risque d'exploitation

CVE-2026-52948 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <2.6.29, <=7.0.*, <=6.12.*, 6.12.94, <943e318eedbeaeea08ece3f5dd44c982f4ed2ef5, 0, <4576621dc6577f21a032acfd16c3ad61907a5ea7, <ffbcf31f032eb454ebfd29309f51366fe57f4ac4, 6.1.176, 5.15.210, 2.6.29, <=5.10.*, <=6.6.*, 7.0.13, <aa6ef734016912653a909477fb30aeb66c98b3a2, 6.18.36, cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d, <ff02add34ffd03449b8115904ebe2ec4fed022d4, 7.1, <0b88ecfbc9dc33b4db8836c37b50cf174e6c0691, <=6.18.*, <617eb7c0961a8dfcfc811844a6396e406b2923ea, <=*, <=5.15.*, <e9ffd5f5050fbb199d270a85614cd27ebed6fbac, 6.6.143, 5.10.259) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE