CVE-2025-40175
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In Linux kernel's idpf driver, SKBs in PTP timestamp flows may remain unreleased after reset, causing memory leaks; fixed by adding cleanup in release function.
A vulnerability in the Linux kernel's idpf driver occurs when PTP (Precision Time Protocol) timestamp requests are processed. The driver correctly clones SKBs using skb_get to increase the reference counter and prevent premature freeing. However, if a device reset occurs while PTP flows are active, the cloned SKBs assigned to Tx timestamp latches may never be consumed, leaving them unreleased and causing a memory leak [1].
To trigger this issue, an attacker would need to be able to induce a reset on the interface while PTP timestamping is in use. This could be achieved through local access or by causing a reset condition. The vulnerability is present in kernel versions where the idpf driver includes PTP support and the reset handling does not clean up pending timestamp SKBs [2].
The impact is a memory leak that can degrade system performance and stability over time. Each unreleased SKB consumes kernel memory, and repeated resets or continuous PTP usage could accumulate significant leakage, potentially leading to denial of service.
The fix, introduced in the Linux kernel mainline and backported to stable releases, adds a check in the release timestamping function to verify if the SKB assigned to the Tx timestamp latch was freed, and releases any remaining SKBs [1][2]. Users should update to a kernel version containing the patch. No workaround is documented.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
3Patches
22c84e91ef831a3f8c0a27312Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
2News mentions
0No linked articles in our index yet.