VulnerabilityPublished 24 Jun 2026Updated 6 Nov 2026

CVE-2026-52930: Linux kernel · ipc/shm: serialize orphan cleanup with shm_nattch updates

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in db752ebfdaf2c7f27cd9690ef48b616af068319c : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in db752ebfdaf2c7f27cd9690ef48b616af068319c, b5107b4ce3ad45fcf369ee2058c8910620f4b5a8, b1e9aef48e4d8a0c1b54fb913077b0824ed7d650 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d, < db752ebfdaf2c7f27cd9690ef48b616af068319c	Fixed in db752ebfdaf2c7f27cd9690ef48b616af068319c
LinuxLinux	Affected ≥ 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d, < b5107b4ce3ad45fcf369ee2058c8910620f4b5a8	Fixed in b5107b4ce3ad45fcf369ee2058c8910620f4b5a8
LinuxLinux	Affected ≥ 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d, < b1e9aef48e4d8a0c1b54fb913077b0824ed7d650	Fixed in b1e9aef48e4d8a0c1b54fb913077b0824ed7d650
LinuxLinux	Affected ≥ 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d, < 6560be3f6a5bb84f006f184f0c966747bb58e1a3	Fixed in 6560be3f6a5bb84f006f184f0c966747bb58e1a3
LinuxLinux	Affected ≥ 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d, < 92cda2593cf2ed25b0e9d78e5e6d8303bba1a064	Fixed in 92cda2593cf2ed25b0e9d78e5e6d8303bba1a064
LinuxLinux	Affected ≥ 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d, < 030bbc857bd51d4b25a90d931d3f8775ef22823a	Fixed in 030bbc857bd51d4b25a90d931d3f8775ef22823a

Description

In the Linux kernel, the following vulnerability has been resolved: ipc/shm: serialize orphan cleanup with shm_nattch updates shm_destroy_orphaned() walks the shm idr under shm_ids(ns).rwsem, but that does not serialize all fields tested by shm_may_destroy(). In particular, shm_nattch is updated while holding shm_perm.lock, and attach paths can do that without holding the rwsem. Do not decide that an orphaned segment is unused before taking the object lock. Move the shm_may_destroy() check under shm_perm.lock, matching the other destroy paths, and unlock the segment when it no longer qualifies for removal.

References

Community reviews

Loading reviews…