xsk: validate launch-time metadata size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
6.15
|
In the Linux kernel, the following vulnerability has been resolved:
xsk: validate launch-time metadata size
Launch-time metadata extends beyond the first 16 bytes of struct xsk_tx_metadata. Reject the request when the registered metadata area does not contain the complete field.
Snapshot the validated flags for the generic transmit path and use that snapshot for request and completion processing, avoiding inconsistent decisions if user space changes the flags concurrently.
Note that only xsk_skb_metadata is properly using the flags, __xsk_buff_get_metadata ignores them. Next commits address that.
From the CVE record · Linux
The Linux kernel's xsk transmit path does not reject launch-time requests when the registered metadata area is too small for the complete field. Local user space can submit such a request and can change metadata flags concurrently, causing inconsistent request and completion processing. The input does not specify whether additional privileges are required.
Teams running Linux kernels with xsk support should check their versions against the vendor advisory; affected versions are not specified in the input.