Memory Corruption Vulnerability in i2c: ismt
Summary
GSD-2022-1003193: i2c: ismt: prevent memory corruption in ismt_access(). Affects Kernel versions >= 5e9a97b1f4491b8b65874901ad084348fcaba327, < fc2f9ee7568609adb68b1f55f0a4c182b09a47e7. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The i2c: ismt package is a component of the Linux Kernel, which is responsible for managing the Inter-Integrated Circuit (I2C) bus. The I2C bus is a widely used communication protocol for connecting low-speed peripherals to microcontrollers and other embedded systems. The i2c: ismt package provides support for Intel's Integrated Sensor Hub (ISH) devices, which utilize the I2C bus for communication. This vulnerability affects versions of the Linux Kernel from v5.11 to v5.17.12.
Vulnerability Detail
The vulnerability in the i2c: ismt package, identified as GSD-2022-1003193, allows for memory corruption in the ismt_access() function. This vulnerability can be exploited by an attacker to manipulate memory contents, potentially leading to arbitrary code execution or system instability. The vulnerability was introduced in version v5.11 of the Linux Kernel and has been fixed in version v5.17.13.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround available for this vulnerability. It is strongly advised to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
The memory corruption vulnerability in the i2c: ismt package can have serious security implications, potentially leading to arbitrary code execution or system instability. It is crucial to update the Linux Kernel to version v5.17.13 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially allow an attacker to execute arbitrary code or cause system instability by manipulating memory contents.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any known vulnerabilities.
At the time of this report, there are no known public exploits for this vulnerability. However, it is always recommended to apply security patches as soon as they become available.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to untrusted networks or if the attacker has already gained access to the system through other means.
For more details about this vulnerability, including the technical aspects and the fix, you can refer to the official GitHub repository of the Cloud Security Alliance's GSD Database (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
