xsk: validate metadata when processing requests
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 metadata when processing requests
The zero-copy path validates TX metadata while obtaining the descriptor context, then reads it again later when preparing the hardware request. User space can change the metadata between those operations and bypass the original validation.
Validate the metadata in xsk_tx_metadata_request() and use the resulting flags snapshot for every feature check. Read request fields once so all zero-copy drivers process only values observed after successful validation.
From the CVE record · Linux
The Linux kernel’s XSK zero-copy TX path validates metadata, then reads it again when preparing a hardware request. User space can change the metadata between those operations and bypass the original validation. This requires access to the zero-copy TX path; the input does not specify authentication requirements or user interaction.
Engineers running the Linux kernel with XSK zero-copy TX should check their installations; affected versions are not specified.