Cyber Resilience

CVE-2026-52952

Linux Kernel 7.0 – 7.0.10

Published
24 June 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0014 4th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2026-52952 is a high-severity Reachable Assertion (CWE-617) vulnerability in Linux Linux Kernel. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset In __iommu_group_set_domain_internal(), concurrent domain attachments are rejected when any device in the group is recovering. This is necessary to fence concurrent attachments…

more

to a multi-device group where devices might share the same RID due to PCI DMA alias quirks, but triggers the WARN_ON in __iommu_group_set_domain_nofail(). Other IOMMU_SET_DOMAIN_MUST_SUCCEED callers in detach/teardown paths, such as __iommu_group_set_core_domain and __iommu_release_dma_ownership, should not be rejected, as the domain would be freed anyway in these nofail paths while group->domain is still pointing to it. So pci_dev_reset_iommu_done() could trigger a UAF when re-attaching group->domain. Honor the IOMMU_SET_DOMAIN_MUST_SUCCEED flag, allowing the callers through the group->recovery_cnt fence, so as to update the group->domain pointer. Instead add a gdev->blocked check in the device iteration loop, to prevent any concurrent per-device detachment.

CWE(s)
CWE-617CWE-825

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-46176Same product: Linux Linux Kernel
CVE-2026-52923Same product: Linux Linux Kernel
CVE-2026-53085Same product: Linux Linux Kernel
CVE-2026-31703Same product: Linux Linux Kernel
CVE-2026-45972Same product: Linux Linux Kernel
CVE-2026-52924Same product: Linux Linux Kernel
CVE-2026-45998Same product: Linux Linux Kernel
CVE-2026-46166Same product: Linux Linux Kernel
CVE-2026-52950Same product: Linux Linux Kernel
CVE-2026-46117Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
7.1 · 7.0 — 7.0.10

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation finds reachable assertions during development.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles discourage use of assertions for handling untrusted input.

SC-39 Process Isolation partial match

Process isolation confines the effects of a use-after-free within a single address space, reducing cross-process impact.

SI-10 Information Input Validation partial match

Validating untrusted inputs structurally prevents attacker data from reaching and triggering assertions.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the blast radius when an expired pointer is dereferenced, even though they do not stop the coding flaw itself.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.

DE.CM-09 partial match
prevents

Runtime monitoring of software can detect assertion-triggered crashes as adverse events.

ID.AM-08 partial match
prevents

Lifecycle management includes secure development and maintenance phases that reduce memory-safety defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.

PR.PS-02 partial match
prevents

Routine patching and replacement can eliminate known instances of expired-pointer bugs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect reachable assertions before release, reducing the likelihood of exploitation.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates defensive coding and input validation that prevent reachable assertions from being triggered by untrusted data.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify that assertions must not be reachable from attacker-controlled inputs.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage the use of assertions for runtime error handling that an attacker could exploit.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.

A.8.32 Change management partial match
prevents

Change-management processes can require re-validation of memory safety after modifications, indirectly reducing the weakness.

References