Fix KASAN error in LAG NETDEV_UNREGISTER handler in Kernel
Summary
GSD-2022-1000521: ice: Fix KASAN error in LAG NETDEV_UNREGISTER handler. Affects Kernel versions >= 6a8b357278f5f8b9817147277ab8f12879dce8a8, < faa9bcf700ca1a0d09f92502a6b65d3ce313fb46. 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 is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. The LAG (Link Aggregation Group) NETDEV_UNREGISTER handler is responsible for handling the unregistering of network devices in a LAG. This vulnerability in the Kernel's LAG NETDEV_UNREGISTER handler can lead to a KASAN (Kernel Address Sanitizer) error.
Vulnerability Detail
The vulnerability arises from an issue in the LAG NETDEV_UNREGISTER handler of the Kernel. When unregistering network devices in a LAG, a KASAN error can occur, potentially leading to memory corruption or other security implications. The vulnerability was introduced in version v5.15 of the Linux Kernel and has been fixed in version v5.16.10 by commit faa9bcf700ca1a0d09f92502a6b65d3ce313fb46.
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 Kernel's LAG NETDEV_UNREGISTER handler can lead to a KASAN error, potentially resulting in memory corruption or other security implications. It is crucial to update the Linux Kernel to version v5.16.10 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to memory corruption or other security implications.
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 it will provide real-time alerts for open-source vulnerabilities.
There is no known exploit for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.16.10 or later.
You can refer to the vulnerability details in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1000xxx/GSD-2022-1000521.json) for more information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
