Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-52930, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < b1e9aef48e4d8a0c1b54fb913077b0824ed7d650
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < 92cda2593cf2ed25b0e9d78e5e6d8303bba1a064
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < 1f0d01e35dbb228084d5187212e32c91a30dcbeb
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < 6560be3f6a5bb84f006f184f0c966747bb58e1a3
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < b5107b4ce3ad45fcf369ee2058c8910620f4b5a8
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < db752ebfdaf2c7f27cd9690ef48b616af068319c
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < 030bbc857bd51d4b25a90d931d3f8775ef22823a
    • affected 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d – < 2e5c6f4fd4001562781e99bbfc7f1f0127187542
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-52930 badge
[![CVE-2026-52930](https://cveledger.app/badge/CVE-2026-52930.svg)](https://cveledger.app/cve/CVE-2026-52930)

Record last updated .