Descrizione
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.
Come correggere
Priorità: Bassa — correggere con la manutenzione ordinaria. Motivazione: EPSS 0.2% (percentile 6).
Versioni da aggiornare
- Linux Linux: versione corretta
6.12.118(o successiva). - Linux Linux: versione corretta
6.18.64(o successiva). - Linux Linux: versione corretta
7.3.5(o successiva). - Linux Linux: versione corretta
7.4-rc2(o successiva). - Linux Linux: vulnerabile la versione
6.7→ installare l'ultima release supportata dal vendor.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ridurre l'esposizione del componente vulnerabile (segmentazione, accesso solo da reti fidate) finché la patch non è applicata.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| Linux | Linux | — | 6.12.118 |
| Linux | Linux | — | 6.18.64 |
| Linux | Linux | — | 7.3.5 |
| Linux | Linux | — | 7.4-rc2 |
| Linux | Linux | 6.7 | — |
Riferimenti
- Riferimentohttps://git.kernel.org/stable/c/3d5d16b797a5a7131bb1a1fb81e2dfbe67aa916e
- Riferimentohttps://git.kernel.org/stable/c/3e83be2d6473118ef6625c00ec9bc6bf99002847
- Riferimentohttps://git.kernel.org/stable/c/603a0c40d414ea12509fc45f2b930449a8d4aad2
- Riferimentohttps://git.kernel.org/stable/c/6a236983e79b92d989d7179cf74927330f6606a4