From this webpage screenshot, we can extract the following key information about the vulnerability: 1. Vulnerability Description: - The vulnerability occurs in the module, where sending untagged traffic through a VxLAN device may cause a kernel crash. - This happens during the fragment checking in the function. 2. Triggering Conditions: - The following conditions must be met: 1. The module is loaded. 2. is set to 1. 3. There is a bridge with a VxLAN (single VxLAN device) as a bridge port. 4. The size of untagged frames exceeds the VxLAN MTU. 3. Root Cause: - When forwarding untagged packets to a VxLAN bridge port, the function is called, setting to the tunnel destination. is a metadata type, meaning is false and is NULL. - In the hook, the function checks for frames requiring fragmentation. For frames larger than the VxLAN device’s MTU, attempts to use as a valid destination, leading to a crash. 4. Fixes Implemented: - The module code was fixed to avoid processing untagged frames when unsupported. - Code in was corrected to properly handle untagged frames. 5. Patch Application: - The patch addresses the issue in . - It fixes the conditional checks in the code to prevent processing untagged frames when not supported. 6. Review and Verification: - The patch was reviewed and verified by Ido Schimmel, Andy Roulin, Nikolay Aleksandrov, Jakub Kicinski, and Sasha Levin. This information provides a clear understanding of the vulnerability’s triggering conditions, root cause, mitigation steps, and review process, which is crucial for comprehending the nature and resolution of the issue.