cpumap: Zero-initialise xdp_rxq_info struct before running XDP program
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9216477449f33cdbc9c9a99d49f500b7fbb81702 · < 2487007aa3b9fafbd2cb14068f49791ce1d7ede5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
cpumap: Zero-initialise xdp_rxq_info struct before running XDP program
When running an XDP program that is attached to a cpumap entry, we don't initialise the xdp_rxq_info data structure being used in the xdp_buff that backs the XDP program invocation. Tobias noticed that this leads to random values being returned as the xdp_md->rx_queue_index value for XDP programs running in a cpumap.
This means we're basically returning the contents of the uninitialised memory, which is bad. Fix this by zero-initialising the rxq data structure before running the XDP program.
From the CVE record · Linux
The Linux kernel does not initialize xdp_rxq_info before running an XDP program attached to a cpumap entry. The program can receive uninitialized memory contents as its rx_queue_index value. The input does not specify attacker access requirements or user interaction.
Teams running the Linux kernel with XDP programs attached to cpumap entries should check their systems; affected versions are not specified.