net: ena: PHC: Fix potential use-after-free in get_timestamp
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.33, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From e0ea34158ee8c4f7536cd781010339ff28c0d24c · fixed in 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98; From e0ea34158ee8c4f7536cd781010339ff28c0d24c · fixed in ca9ed40f28949353911dcb524ff8fff2f3409c97; From e0ea34158ee8c4f7536cd781010339ff28c0d24c · fixed in e42c755582f0960e684298762f0ab927b3778376
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10