idpf: cleanup remaining SKBs in PTP flows
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2c84e91ef831d4fedb0b94670b3cfd1cc5f966a5 and Kernel a3f8c0a273120fd2638f03403e786c3de2382e72.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=4901e83a94ef0a8baf27916f31daf59b0a68547f <2c84e91ef831d4fedb0b94670b3cfd1cc5f966a5, >=4901e83a94ef0a8baf27916f31daf59b0a68547f <a3f8c0a273120fd2638f03403e786c3de2382e72 | 2c84e91ef831d4fedb0b94670b3cfd1cc5f966a5, a3f8c0a273120fd2638f03403e786c3de2382e72 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket