Memory Corruption Vulnerability in iio: adc: tsc2046
Summary
GSD-2022-1000799: iio: adc: tsc2046: fix memory corruption by preventing array overflow. Affects Kernel versions >= 9374e8f5a38defe90bc65b2decf317c1c62d91dd, < 0cb9b2f73c182d242a640e512f4785c7c504512f. 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 iio: adc: tsc2046 is a driver in the Linux Kernel that provides support for the Texas Instruments TSC2046 touchscreen controller. This driver allows users to interact with touchscreens connected to the system. The vulnerability in this driver can lead to memory corruption, potentially resulting in system instability or unauthorized access to sensitive information.
Vulnerability Detail
The vulnerability in the iio: adc: tsc2046 driver is caused by an array overflow, which can result in memory corruption. An attacker could exploit this vulnerability by sending specially crafted input to the driver, causing it to write beyond the bounds of an array. This could lead to the corruption of adjacent memory regions, potentially affecting the stability of the system or allowing an attacker to execute arbitrary code. The vulnerability was introduced in version v5.14 of the Linux Kernel and has been fixed in version v5.15.26.
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 known workaround for this vulnerability. It is essential to apply the fix by updating the Linux Kernel to the recommended version.
Conclusion
The memory corruption vulnerability in the iio: adc: tsc2046 driver can lead to system instability or unauthorized access to sensitive information. It is crucial to update the Linux Kernel to version v5.15.26 or later to mitigate this vulnerability. No known workarounds are available, and it is recommended to apply the fix as soon as possible. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in memory corruption, potentially leading to system instability or unauthorized access to sensitive information.
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 to the playground, and it will analyze the dependencies and alert you if any vulnerabilities are found.
At the time of this report, there are no known exploits for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate the risk.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. Attackers can send specially crafted input to the vulnerable driver, triggering the array overflow and potentially gaining unauthorized access or causing system instability.
For further support and assistance with vulnerability remediation, you can contact info@devnack.com. Our team of experts will be happy to assist you.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
