Vulnerability in Kernel package: llc: only change llc->dev when bind() succeeds
Summary
GSD-2022-1002457: llc: only change llc->dev when bind() succeeds. Affects Kernel versions >= 0f294bc04be87f1c9e1d1a908db9fcc84ce94210, < f25366d9a27585d45dfd475aa1764b8886958aac. 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 functions and providing an interface between hardware and software. It is a fundamental part of the operating system, handling tasks such as memory management, process scheduling, and device drivers. The vulnerability in question affects the llc module within the Kernel package.
Vulnerability Detail
The llc module in the Kernel package has a vulnerability that allows the change of llc->dev even when the bind() function fails. This vulnerability was introduced in version v4.14.274 of the Linux Kernel and was fixed in version v4.14.274 by commit f25366d9a27585d45dfd475aa1764b8886958aac. The impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could potentially lead to unauthorized access, privilege escalation, or denial of service.
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
In conclusion, the Kernel package's llc module has a vulnerability that allows the change of llc->dev even when the bind() function fails. It is recommended to update the Linux Kernel package to version v4.14.274 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but if exploited, it could potentially lead to unauthorized access, privilege escalation, or 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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch is available for this vulnerability. It is recommended to update the Linux Kernel package to version v4.14.274 or later.
The remote exploitability of this vulnerability is not yet determined. Further analysis is required to assess the potential for remote exploitation.
You can find more information about this vulnerability in the GSD-2022-1002457 JSON report available on the Cloud Security Alliance's GSD Database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002457.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
