CVE-2026-31627: i2c: s3c24xx: check the size of the SMBUS message before using it
i2c: s3c24xx: check the size of the SMBUS message before using it
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.137.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Compensating control
Update the i2c s3c24xx driver to verify that the first byte of each SMBUS message, representing its size, is in the range 0..I2C_SMBUS_BLOCK_MAX before processing it.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-31627?
CVE-2026-31627 is classified as a medium severity vulnerability due to potential impacts on the integrity of SMBUS message processing.
How do I fix CVE-2026-31627?
To fix CVE-2026-31627, update your Linux kernel to a version that includes the patch addressing this SMBUS message size check issue.
What systems are affected by CVE-2026-31627?
CVE-2026-31627 affects various versions of the Linux kernel, specifically in the i2c s3c24xx driver.
What vulnerabilities are similar to CVE-2026-31627?
Similar vulnerabilities may involve improper validation of message sizes or unchecked data processing in kernel drivers.
Can CVE-2026-31627 lead to remote code execution?
CVE-2026-31627 does not directly lead to remote code execution but could allow attackers to manipulate SMBUS communication, potentially impacting system stability.