Answer in brief
CVE-2026-52971 records a High severity (CVSS 7.8) vulnerability in net: ena: PHC: Fix potential use-after-free in get_timestamp. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98 || >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <ca9ed40f28949353911dcb524ff8fff2f3409c97 || >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <e42c755582f0960e684298762f0ab927b3778376 | 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, ca9ed40f28949353911dcb524ff8fff2f3409c97, e42c755582f0960e684298762f0ab927b3778376 |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-52971 records a High severity (CVSS 7.8) vulnerability in net: ena: PHC: Fix potential use-after-free in get_timestamp. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98 || >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <ca9ed40f28949353911dcb524ff8fff2f3409c97 || >=e0ea34158ee8c4f7536cd781010339ff28c0d24c <e42c755582f0960e684298762f0ab927b3778376 | 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, ca9ed40f28949353911dcb524ff8fff2f3409c97, e42c755582f0960e684298762f0ab927b3778376 |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.