net: ena: PHC: Fix potential use-after-free in get_timestamp
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, Kernel ca9ed40f28949353911dcb524ff8fff2f3409c97 and Kernel e42c755582f0960e684298762f0ab927b3778376.
In the Linux kernel, the following vulnerability has been resolved: net: ena: PHC: Fix potential use-after-free in get_timestamp Move the phc->active check and resp pointer assignment to after acquiring the spinlock. Previously, phc->active was checked without holding the lock, and resp was cached from ena_dev->phc.virt_addr before the lock was acquired. If ena_com_phc_destroy() runs between the lockless active check and the lock acquisition, it sets active=false, releases the lock, frees the DMA memory, and sets virt_addr=NULL. The get_timestamp path would then read a NULL virt_addr and dereference it. With both the active check and the pointer read under the lock, destroy cannot free the memory while get_timestamp is using it.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <ca9ed40f28949353911dcb524ff8fff2f3409c97, >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <e42c755582f0960e684298762f0ab927b3778376 | 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, ca9ed40f28949353911dcb524ff8fff2f3409c97, e42c755582f0960e684298762f0ab927b3778376 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket