tap: add missing verification for short frame
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0efac27791ee068075d80f07c55a229b1335ce12 · < 73d462a38d5f782b7c872fe9ae8393d9ef5483da| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tap: add missing verification for short frame
The cited commit missed to check against the validity of the frame length in the tap_get_user_xdp() path, which could cause a corrupted skb to be sent downstack. Even before the skb is transmitted, the tap_get_user_xdp()-->skb_set_network_header() may assume the size is more than ETH_HLEN. Once transmitted, this could either cause out-of-bound access beyond the actual length, or confuse the underlayer with incorrect or inconsistent header length in the skb metadata.
In the alternative path, tap_get_user() already prohibits short frame which has the length less than Ethernet header size from being transmitted.
This is to drop any frame shorter than the Ethernet header size just like how tap_get_user() does.
CVE: CVE-2024-41090
From the CVE record · Linux
The Linux kernel’s tap_get_user_xdp() path does not reject frames shorter than an Ethernet header. A short frame can produce a corrupted skb, potentially causing out-of-bounds access or inconsistent header metadata; the input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the affected tap code; affected versions are not specified.