bnxt: prevent skb UAF after handing over to PTP worker
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 |
|
|
5.15.715.19.126.0In the Linux kernel, the following vulnerability has been resolved:
bnxt: prevent skb UAF after handing over to PTP worker
When reading the timestamp is required bnxt_tx_int() hands over the ownership of the completed skb to the PTP worker. The skb should not be used afterwards, as the worker may run before the rest of our code and free the skb, leading to a use-after-free.
Since dev_kfree_skb_any() accepts NULL make the loss of ownership more obvious and set skb to NULL.
From the CVE record · Linux
The Linux kernel's bnxt driver can use a completed network buffer after handing it to a PTP worker for timestamp processing. The worker may free the buffer first, causing a use-after-free. The input does not specify an attack path, authentication requirements, or user interaction.
Teams running Linux kernels with the bnxt driver should check whether their kernel includes the fix; affected versions were not provided.