CVE-2026-99755

published 20 Nov 2026 · updated 20 Nov 2026

ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6a236983e79b92d989d7179cf74927330f6606a4, Kernel 3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e, Kernel 3e83be2d6473118ef6625c00ec9bc6bf99002847 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=d26ab5a35ad9920940a9e07665130d501b2ae1a3 <6a236983e79b92d989d7179cf74927330f6606a4, >=d26ab5a35ad9920940a9e07665130d501b2ae1a3 <3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e, >=d26ab5a35ad9920940a9e07665130d501b2ae1a3 <3e83be2d6473118ef6625c00ec9bc6bf99002847, >=d26ab5a35ad9920940a9e07665130d501b2ae1a3 <603a0c40d414ea12509fc45f2b930449a8d4aad2, =6.76a236983e79b92d989d7179cf74927330f6606a4, 3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e, 3e83be2d6473118ef6625c00ec9bc6bf99002847, 603a0c40d414ea12509fc45f2b930449a8d4aad2
linux-kernel: Kernel>=6.19.0 <7.3.5, >=6.7.0 <6.12.118, >=6.13.0 <6.18.647.3.5, 6.12.118, 6.18.64

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99755 severity on Zeptric[![CVE-2026-99755](https://zeptric.io/badge/cve/CVE-2026-99755.svg)](https://zeptric.io/cve/CVE-2026-99755)