Skip to content
Threat Brief

← All advisories

CVE-2026-99755

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom d26ab5a35ad9920940a9e07665130d501b2ae1a3 before 3e83be2d6473118ef6625c00ec9bc6bf990028473e83be2d6473118ef6625c00ec9bc6bf99002847CVE Program
LinuxLinuxfrom d26ab5a35ad9920940a9e07665130d501b2ae1a3 before 6a236983e79b92d989d7179cf74927330f6606a46a236983e79b92d989d7179cf74927330f6606a4CVE Program
LinuxLinuxfrom d26ab5a35ad9920940a9e07665130d501b2ae1a3 before 603a0c40d414ea12509fc45f2b930449a8d4aad2603a0c40d414ea12509fc45f2b930449a8d4aad2CVE Program
LinuxLinuxfrom d26ab5a35ad9920940a9e07665130d501b2ae1a3 before 3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916eCVE Program
LinuxLinux6.7Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.7Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references