What is CVE-2026-52971?

CVE-2026-52971 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, classified as a Use After Free flaw (CWE-416), affecting Linux kernel versions from 6.17 onward and patched in 6.18.33, 7.0.10 and 7.1. CVE-2026-52971 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-52971?

CVE-2026-52971 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-52971?

Yes, CVE-2026-52971 has been patched. Fixed versions include 6.18.33, 7.0.10 and 7.1. If you are running Linux kernel 6.17 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-52971 actively exploited?

CVE-2026-52971 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Use After Free (CWE-416)?

The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/416.html

CVE-2026-52971

High

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.

Package Linux Kernel

Published 2026-06-24

Last modified 2026-07-14

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Weakness type

CWE-416

CVE-2026-52971 is a Use After Free vulnerability

What is Use After Free?

The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.17 and later are affected. Fixed in 6.18.33, 7.0.10, 7.1 and their respective stable series.

Affected from

≥ 6.17

Fixed in

✓ 6.18.33 6.18.x ✓ 7.0.10 7.0.x ✓ 7.1

References

3 total

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

Patch
Kernel Git
https://git.kernel.org/stable/c/ca9ed40f28949353911dcb524ff8fff2f3409c97

Patch
Kernel Git
https://git.kernel.org/stable/c/e42c755582f0960e684298762f0ab927b3778376

Patch

Details

CVE ID CVE-2026-52971

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-06-24

Modified 2026-07-14

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-52971?

CVE-2026-52971 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 , classified as an Use After Free flaw (CWE-416) . It affects Linux kernel versions from 6.17 onward and has been patched in 6.18.33, 7.0.10 and 7.1. CVE-2026-52971 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-52971?

CVE-2026-52971 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-52971?

Yes. CVE-2026-52971 has been patched. Fixed versions include 6.18.33, 7.0.10 and 7.1. If you are running Linux kernel 6.17 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-52971 actively exploited?

No. CVE-2026-52971 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.