Vulnerability in Kernel: tunnels: do not assume mac header is set in skb_tunnel_check_pmtu()
Summary
GSD-2022-1004437: tunnels: do not assume mac header is set in skb_tunnel_check_pmtu(). Affects Kernel versions >= 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 674a641e5b67e16ba3112eacd680ff87b38539de. 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 functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and ensures the security and stability of the system. The vulnerability in question affects the Kernel's handling of tunnels and specifically the function skb_tunnel_check_pmtu().
Vulnerability Detail
The vulnerability arises from an incorrect assumption made in the skb_tunnel_check_pmtu() function within the Kernel. It assumes that the MAC (Media Access Control) header is always set, which may not be the case in certain scenarios. This can lead to potential security vulnerabilities, although the exact impact and attack plausibility have not been proven. The vulnerability was introduced in version v5.9 of the Linux Kernel and has been fixed in version v5.15.53.
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 handling of tunnels can potentially introduce security vulnerabilities in affected systems. It is crucial to update the Linux Kernel to version v5.15.53 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 exact impact of this vulnerability is not yet proven. However, it has the potential to introduce security vulnerabilities in systems running the affected versions of the Linux Kernel.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch has been released to fix this vulnerability. It is recommended to update the Linux Kernel to version v5.15.53 or later to apply the patch.
The recommended approach is to update the Kernel to the fixed version. However, if updating is not immediately feasible, it is important to ensure other security measures are in place, such as network segmentation, access controls, and monitoring for any suspicious activity.
You can refer to the vulnerability details in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004437.json) for more information about this vulnerability, including its timeline and references to relevant commits in the Linux Kernel repository.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
