CVE-2026-99755ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked
- —Not scoredno CVSS score yet
- —Exploitation in 30 daysno EPSS score yet
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked extts_fifo_show() walks ptp->tsevqs with list_count_nodes() and then list_first_entry() without holding ptp->tsevqs_lock, the spinlock that "protects tsevqs from concurrent access". Every other accessor of the list honours it: ptp_open() (list_add_tail), ptp_release() (list_del followed by kfree of the per-fd queue), ptp_clock_release() and ptp_clock_event() all take tsevqs_lock. extts_fifo_show() is the only one that does not. A per-fd timestamp queue is appended to tsevqs on open("/dev/ptpN") and removed and freed on close(), both under tsevqs_lock: scoped_guard(spinlock_irq, &ptp->tsevqs_lock) list_del(&queue->qlist); bitmap_free(queue->mask); kfree(queue); So a read of /sys/class/ptp/ptpN/fifo running concurrently with a close() of a /dev/ptpN fd can have list_count_nodes() walk into the queue that close() is removing and freeing, dereferencing freed memory (use-after-free) or a poisoned list pointer. Take tsevqs_lock around the list walk. The fifo only ever draws from the first queue, which is the registration-time queue created in ptp_clock_register() and freed only in ptp_clock_release(); that cannot run while the sysfs attribute is being read, so the dequeue from queue->buf under queue->lock may stay outside tsevqs_lock and the lock order is unchanged.
Timeline
ID reserved
By Linux
- 56 days later
· 56 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.
- EPSS (exploitation in 30 days)
- Not scored
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected d26ab5a35ad9920940a9e07665130d501b2ae1a3 – < 3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e
- affected d26ab5a35ad9920940a9e07665130d501b2ae1a3 – < 3e83be2d6473118ef6625c00ec9bc6bf99002847
- affected d26ab5a35ad9920940a9e07665130d501b2ae1a3 – < 6a236983e79b92d989d7179cf74927330f6606a4
- affected d26ab5a35ad9920940a9e07665130d501b2ae1a3 – < 603a0c40d414ea12509fc45f2b930449a8d4aad2
- affected 6.7
- unaffected < 6.7
- unaffected 6.12.118 – ≤ 6.12.*
- unaffected 6.18.64 – ≤ 6.18.*
- unaffected 7.3.5 – ≤ 7.3.*
- unaffected 7.4-rc2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e (opens in a new tab)
- https://git.kernel.org/stable/c/3e83be2d6473118ef6625c00ec9bc6bf99002847 (opens in a new tab)
- https://git.kernel.org/stable/c/6a236983e79b92d989d7179cf74927330f6606a4 (opens in a new tab)
- https://git.kernel.org/stable/c/603a0c40d414ea12509fc45f2b930449a8d4aad2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99755)Record last updated .