Fix crash in smtcfb_read() in video: fbdev: sm712fb
Summary
GSD-2022-1002119: video: fbdev: sm712fb: Fix crash in smtcfb_read(). Affects Kernel versions < 72af8810922eb143ed4f116db246789ead2d8543. 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 video: fbdev: sm712fb package is a component of the Linux Kernel, which is responsible for managing the framebuffer devices for certain graphics cards. It provides the necessary drivers and functionality for these devices to work properly. The sm712fb driver specifically handles the Silicon Motion SM712 graphics card. This vulnerability affects the smtcfb_read() function within the sm712fb driver.
Vulnerability Detail
The vulnerability in the smtcfb_read() function of the sm712fb driver can lead to a crash. The exact cause and impact of the crash have not been proven, but it has the potential to disrupt the normal operation of the graphics card and the system as a whole. This vulnerability has been fixed in the Linux Kernel version v5.10.110 by commit 72af8810922eb143ed4f116db246789ead2d8543.
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 mentioned for this vulnerability.
Conclusion
The vulnerability in the smtcfb_read() function of the sm712fb driver has been fixed in the Linux Kernel version v5.10.110. Users are advised to update their Linux Kernel to the latest version to ensure the security and stability of their systems. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is a potential crash in the sm712fb driver, which can disrupt the normal operation of the graphics card and the system.
There is no known exploit for this vulnerability at the moment.
The details of remote exploitation have not been provided, but it is always recommended to keep systems updated to mitigate potential remote attack vectors.
The specific prerequisites, if any, have not been mentioned for this vulnerability.
There is no evidence of active exploitation of this vulnerability at the moment.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
