CVE-2026-52971

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net: ena: PHC: Fix potential use-after-free in get_timestamp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e42c755582f0960e684298762f0ab927b3778376
generic

net: ena: PHC: Fix potential use-after-free in get_timestamp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca9ed40f28949353911dcb524ff8fff2f3409c97
generic

net: ena: PHC: Fix potential use-after-free in get_timestamp - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98

Vendor Advisories for CVE-2026-52971(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 4× in last 7d / 82× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 250 total refreshes for this CVE.

  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-30 20:16 UTCEG score recompute
  10. 2026-08-30 20:16 UTCVendor advisory
  11. 2026-08-30 20:16 UTCGHSA enrichment
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 04:48 UTCEG score recompute
  16. 2026-08-28 04:48 UTCVendor advisory
  17. 2026-08-28 04:48 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 01:55 UTCEG score recompute
  22. 2026-08-25 01:55 UTCVendor advisory
  23. 2026-08-25 01:55 UTCGHSA enrichment
  24. 2026-08-24 13:45 UTCEG score recompute
  25. 2026-08-24 13:45 UTCVendor advisory
Show 75 more
  1. 2026-08-24 13:45 UTCGHSA enrichment
  2. 2026-08-24 01:37 UTCVendor advisory
  3. 2026-08-24 01:37 UTCGHSA enrichment
  4. 2026-08-23 13:27 UTCVendor advisory
  5. 2026-08-23 13:27 UTCGHSA enrichment
  6. 2026-08-23 01:15 UTCEG score recompute
  7. 2026-08-23 01:15 UTCVendor advisory
  8. 2026-08-23 01:15 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 13:08 UTCEG score recompute
  11. 2026-08-22 13:08 UTCVendor advisory
  12. 2026-08-22 13:08 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 19:52 UTCVendor advisory
  15. 2026-08-21 19:52 UTCGHSA enrichment
  16. 2026-08-21 07:46 UTCEG score recompute
  17. 2026-08-21 07:46 UTCVendor advisory
  18. 2026-08-21 07:46 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 19:39 UTCVendor advisory
  21. 2026-08-20 19:39 UTCGHSA enrichment
  22. 2026-08-20 07:32 UTCEG score recompute
  23. 2026-08-20 07:32 UTCVendor advisory
  24. 2026-08-20 07:32 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
  26. 2026-08-19 14:52 UTCVendor advisory
  27. 2026-08-19 14:52 UTCGHSA enrichment
  28. 2026-08-19 02:14 UTCEG score recompute
  29. 2026-08-19 02:14 UTCVendor advisory
  30. 2026-08-19 02:14 UTCGHSA enrichment
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-17 06:11 UTCVendor advisory
  33. 2026-08-17 06:11 UTCGHSA enrichment
  34. 2026-08-16 17:06 UTCEG score recompute
  35. 2026-08-16 17:06 UTCVendor advisory
  36. 2026-08-16 17:06 UTCGHSA enrichment
  37. 2026-08-16 14:56 UTCEPSS rescore
  38. 2026-08-16 05:00 UTCEG score recompute
  39. 2026-08-16 05:00 UTCVendor advisory
  40. 2026-08-16 05:00 UTCGHSA enrichment
  41. 2026-08-16 02:14 UTCEPSS rescore
  42. 2026-08-15 16:54 UTCVendor advisory
  43. 2026-08-15 16:54 UTCGHSA enrichment
  44. 2026-08-15 04:47 UTCEG score recompute
  45. 2026-08-15 04:47 UTCVendor advisory
  46. 2026-08-15 04:47 UTCGHSA enrichment
  47. 2026-08-15 01:30 UTCEPSS rescore
  48. 2026-08-14 16:40 UTCVendor advisory
  49. 2026-08-14 16:40 UTCGHSA enrichment
  50. 2026-08-14 04:22 UTCEG score recompute
  51. 2026-08-14 04:22 UTCVendor advisory
  52. 2026-08-14 04:22 UTCGHSA enrichment
  53. 2026-08-13 22:00 UTCEPSS rescore
  54. 2026-08-13 16:15 UTCVendor advisory
  55. 2026-08-13 16:15 UTCGHSA enrichment
  56. 2026-08-13 03:48 UTCVendor advisory
  57. 2026-08-13 03:48 UTCGHSA enrichment
  58. 2026-08-12 15:41 UTCEG score recompute
  59. 2026-08-12 15:41 UTCVendor advisory
  60. 2026-08-12 15:41 UTCGHSA enrichment
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-12 03:08 UTCVendor advisory
  63. 2026-08-12 03:08 UTCGHSA enrichment
  64. 2026-08-11 15:01 UTCVendor advisory
  65. 2026-08-11 15:01 UTCGHSA enrichment
  66. 2026-08-11 02:54 UTCEG score recompute
  67. 2026-08-11 02:54 UTCVendor advisory
  68. 2026-08-11 02:54 UTCGHSA enrichment
  69. 2026-08-11 00:00 UTCEPSS rescore
  70. 2026-08-10 14:48 UTCVendor advisory
  71. 2026-08-10 14:48 UTCGHSA enrichment
  72. 2026-08-10 02:42 UTCVendor advisory
  73. 2026-08-10 02:42 UTCGHSA enrichment
  74. 2026-08-09 14:35 UTCEG score recompute
  75. 2026-08-09 14:35 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-52971?
CVE-2026-52971 is a high vulnerability published on June 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…
When was CVE-2026-52971 disclosed?
CVE-2026-52971 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52971 actively exploited?
CVE-2026-52971 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-52971?
CVE-2026-52971 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-52971?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52971, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52971

Explore →

Is Your Infrastructure Affected by CVE-2026-52971?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.