Vulnerability in Kernel: net: do not keep the dst cache when uncloning an skb dst and its metadata
Summary
GSD-2022-1000434: net: do not keep the dst cache when uncloning an skb dst and its metadata. Affects Kernel versions >= d71785ffc7e7cae3fbdc4ea8a9d05b7a1c59f7b8, < f1ab1ba32d36bae06fabe41c0ff2edc5b2ce628d. 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 critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between processes, and handles device drivers. The vulnerability in question affects the networking subsystem of the Kernel, specifically the handling of the destination (dst) cache when uncloning a socket buffer (skb) dst and its metadata.
Vulnerability Detail
The vulnerability arises from a flaw in the networking subsystem of the Kernel, where the dst cache is not properly cleared when uncloning an skb dst and its associated metadata. This can lead to a variety of security issues, including potential information disclosure, denial of service, or privilege escalation attacks. The vulnerability was introduced in version 4.6 of the Kernel and has been fixed in version 5.15.24.
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
No specific workaround has been mentioned for this vulnerability.
Conclusion
The vulnerability in the Kernel's networking subsystem can have serious security implications, including information disclosure, denial of service, or privilege escalation. It is crucial to update the Linux Kernel to the fixed version (5.15.24 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 information disclosure, denial of service, or privilege escalation attacks.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert provides real-time monitoring and alerts for open-source vulnerabilities without requiring access to the code or installation.
At the time of this report, no known exploits for this vulnerability have been disclosed.
The recommended mitigation is to update the Linux Kernel to the fixed version (5.15.24 or later).
You can refer to the official Linux Kernel repository and the associated commit (f1ab1ba32d36bae06fabe41c0ff2edc5b2ce628d) for more detailed information about this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
