i2c: dev: prevent integer overflow in I2C_TIMEOUT ioctl
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in e9ffd5f5050fbb199d270a85614cd27ebed6fbac; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in 0b88ecfbc9dc33b4db8836c37b50cf174e6c0691; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in 943e318eedbeaeea08ece3f5dd44c982f4ed2ef5; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in aa6ef734016912653a909477fb30aeb66c98b3a2; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in ff02add34ffd03449b8115904ebe2ec4fed022d4; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in ffbcf31f032eb454ebfd29309f51366fe57f4ac4; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in 4576621dc6577f21a032acfd16c3ad61907a5ea7; From cd97f39b7cdf1c8a9c9f52865eec795b7f0c811d · fixed in 617eb7c0961a8dfcfc811844a6396e406b2923ea
- Linux Linux
2.6.29
- KernelLinux
From 2.6.29 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.94; From 6.13.0 · fixed in 6.18.36; From 6.19.0 · fixed in 7.0.13
References 8
git.kernel.org
- stable/c/e9ffd5f5050fbb199d270a85614cd27ebed6fbac
- stable/c/0b88ecfbc9dc33b4db8836c37b50cf174e6c0691
- stable/c/943e318eedbeaeea08ece3f5dd44c982f4ed2ef5
- stable/c/aa6ef734016912653a909477fb30aeb66c98b3a2
- stable/c/ff02add34ffd03449b8115904ebe2ec4fed022d4
- stable/c/ffbcf31f032eb454ebfd29309f51366fe57f4ac4
- stable/c/4576621dc6577f21a032acfd16c3ad61907a5ea7
- stable/c/617eb7c0961a8dfcfc811844a6396e406b2923ea