Vulnerability in Kernel package: drm/i915/reset
Summary
GSD-2022-1004502: drm/i915/reset: Fix error_state_read ptr + offset use. Affects Kernel versions >= 0e39037b3165567660b0e03f67534da5269a0465, < f4c5eba87675a07a6c28cdaca7366aeb4258ec78. 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 Kernel package is a critical component of the Linux operating system, responsible for managing the system's core functionality. It includes various drivers for hardware devices, including the drm/i915/reset driver, which is specifically designed for Intel integrated graphics. This driver handles the reset functionality for the graphics subsystem. However, a vulnerability has been discovered in the drm/i915/reset driver that could potentially be exploited by attackers.
Vulnerability Detail
The vulnerability in the drm/i915/reset driver arises from an error in the handling of pointers and offsets. Specifically, there is a flaw in the error_state_read function that leads to incorrect usage of the ptr + offset expression. This vulnerability could be leveraged by an attacker to manipulate memory and potentially execute arbitrary code or cause a denial of service. The impact and attack plausibility of this vulnerability have not yet been proven, but it is crucial to address it to ensure the security and stability of the system.
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 →
Conclusion
In conclusion, the vulnerability in the drm/i915/reset driver of the Kernel package poses a potential security risk. It is crucial to update the Linux Kernel to version v5.15.49 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
The impact of this vulnerability is not yet proven, but it could potentially allow attackers to manipulate memory and execute arbitrary code or cause a denial of service.
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 Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
At the moment, there are no known workarounds for this vulnerability. It is recommended to update the Linux Kernel to the latest version as soon as possible.
Yes, this vulnerability was introduced in Linux Kernel version v5.0 by commit 0e39037b3165567660b0e03f67534da5269a0465. It is fixed in version v5.15.49 by commit f4c5eba87675a07a6c28cdaca7366aeb4258ec78.
You can find more information about this vulnerability in the GSD-2022-1004502 JSON file available on the Cloud Security Alliance's GSD Database GitHub repository (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004502.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
