Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-52971: net: ena: PHC: Fix potential use-after-free in get_timestamp

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, ca9ed40f28949353911dcb524ff8fff2f3409c97, e42c755582f0960e684298762f0ab927b3778376.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98, ca9ed40f28949353911dcb524ff8fff2f3409c97, e42c755582f0960e684298762f0ab927b3778376 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 24, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 0th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-52971

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.17 and later · before 6.18.33
  • linux linux kernel6.19 and later · before 7.0.10
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.17affected
    • e0ea34158ee8c4f7536cd781010339ff28c0d24c and later · before 95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98affected · git
    • e0ea34158ee8c4f7536cd781010339ff28c0d24c and later · before ca9ed40f28949353911dcb524ff8fff2f3409c97affected · git
    • e0ea34158ee8c4f7536cd781010339ff28c0d24c and later · before e42c755582f0960e684298762f0ab927b3778376affected · git
    • before 6.17not affected · semver
    • 6.18.33 and later · up to and including 6.18.*not affected · semver
    • 7.0.10 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.56.1.el10_26.12.0-211.56.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-52968Jun 24, 2026 · KVM: s390: pci: fix GAIT table indexing due to double-scaling pointer arithmetic
    28Monitor
  • ← EarlierCVE-2026-52970Jun 24, 2026 · netfilter: nft_ct: fix missing expect put in obj eval
    22Monitor
  • Later →CVE-2026-52972Jun 24, 2026 · crypto: af_alg - Cap AEAD AD length to 0x80000000
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux95e8ae9af2a61b4e72f5c585bf4c7d8aaf2a2c98Vendor (CNA)
Linux Linuxca9ed40f28949353911dcb524ff8fff2f3409c97Vendor (CNA)
Linux Linuxe42c755582f0960e684298762f0ab927b3778376Vendor (CNA)
almalinux:kernel6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.56.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux7.0.10-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.56.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:kernel0:6.12.0-211.56.1.el10_2.0.1 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records