From this webpage screenshot, we can extract the following key information about the vulnerability: 1. Vulnerability Description: - Issue: A kernel panic occurs in the module when sending untagged traffic through a VxLAN device. - Trigger Conditions: - The module is loaded. - is set to 1. - A bridge with a VxLAN (single VxLAN device) as a bridge port. - Untagged frames larger than the VxLAN MTU (Maximum Transmission Unit). 2. Root Cause: - Before forwarding untagged packets to the VxLAN bridge port, the function is called and modifies to point to the tunnel destination. The tunnel destination is a metadata type, meaning returns false and is NULL. - In the hook, within the function, there is a check for frames that need fragmentation: if the frame's MTU exceeds the VxLAN device's MTU, is called, which in turn invokes . - attempts to use as a valid destination. If is invalid, this leads to a kernel crash. 3. Resolution: - Fixed the kernel panic issue occurring in the module when sending untagged traffic. - Corrected the logical error in the function when checking for frames requiring fragmentation. 4. Patch Content: - In the file, added a check for metadata destinations to prevent using invalid destinations during fragmentation. 5. Patch Application: - The patch resolves the kernel panic by introducing a check for metadata destinations, preventing the use of invalid destinations during fragmentation. 6. Patch Application Result: - The patch was applied to the file and successfully fixes the kernel panic issue. This information indicates that the vulnerability arises from improper handling of metadata destinations when processing untagged traffic, leading to a kernel panic. The fix addresses this by adding validation logic to avoid using invalid destinations during fragmentation.