bpf: Zero queue and stack outputs on lock failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a34a9f1a19afe9c60ca0ea61dfeee63a1c2baac8 · < 7ac6e1ae41a09f1dd4baeeff1d028ae49ee01232| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Zero queue and stack outputs on lock failure
Queue and stack pop/peek helpers accept an uninitialized output buffer because the verifier expects the helper to initialize it. The empty-map error path clears the buffer, but a failed lock acquisition returns -EBUSY without writing it.
Clear the output before returning -EBUSY so BPF programs cannot observe uninitialized stack contents after a failed helper call.
From the CVE record · Linux
Linux kernel BPF queue and stack pop/peek helpers can leave an output buffer uninitialized when lock acquisition fails. A BPF program can then observe uninitialized stack contents after the helper returns -EBUSY. The input does not specify network access, authentication requirements, or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.