idpf: cleanup remaining SKBs in PTP flows
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
idpf: cleanup remaining SKBs in PTP flows
When the driver requests Tx timestamp value, one of the first steps is to clone SKB using skb_get. It increases the reference counter for that SKB to prevent unexpected freeing by another component. However, there may be a case where the index is requested, SKB is assigned and never consumed by PTP flows - for example due to reset during running PTP apps.
Add a check in release timestamping function to verify if the SKB assigned to Tx timestamp latch was freed, and release remaining SKBs.
From the CVE record · Linux
The Linux kernel’s idpf driver can retain transmit packet buffers (SKBs) assigned to PTP timestamps when they are not consumed, such as after a reset while PTP applications are running. The input does not describe an attacker path, required access, or user interaction.
Engineers running Linux kernels with the idpf driver should check their exposure; affected versions are not specified.