Service interruption via shared-memory orphan cleanup race
Published Jun 24, 2026 · Updated Jun 24, 2026
Race condition in affected Linux Kernel releases allows local users to interrupt service by racing shared-memory orphan cleanup. The shm_destroy_orphaned() path tests shm_nattch without shm_perm.lock even though attach paths update that field under the object lock, allowing an in-use segment to be mistaken for an unused orphan and destroyed. Exploitation requires local access and a successful timing race between a shared-memory attach and orphan cleanup; the bounded reported consequence is loss of availability.
Summary
What happened
Race condition in affected Linux Kernel releases allows local users to interrupt service by racing shared-memory orphan cleanup. The shm_destroy_orphaned() path tests shm_nattch without shm_perm.lock even though attach paths update that field under the object lock, allowing an in-use segment to be mistaken for an unused orphan and destroyed. Exploitation requires local access and a successful timing race between a shared-memory attach and orphan cleanup; the bounded reported consequence is loss of availability.
The record
- CVE
- CVE-2026-52930
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.1
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <030bbc857bd51d4b25a90d931d3f8775ef22823a
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <1f0d01e35dbb228084d5187212e32c91a30dcbeb
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <2e5c6f4fd4001562781e99bbfc7f1f0127187542
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <6560be3f6a5bb84f006f184f0c966747bb58e1a3
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <92cda2593cf2ed25b0e9d78e5e6d8303bba1a064
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <b1e9aef48e4d8a0c1b54fb913077b0824ed7d650
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <b5107b4ce3ad45fcf369ee2058c8910620f4b5a8
- Affected versionversion=4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d <db752ebfdaf2c7f27cd9690ef48b616af068319c
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo