CVE-2026-52930

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

September 8, 2026

Advisory Details (8)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/db752ebfdaf2c7f27cd9690ef48b616af068319c
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b5107b4ce3ad45fcf369ee2058c8910620f4b5a8
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1e9aef48e4d8a0c1b54fb913077b0824ed7d650
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92cda2593cf2ed25b0e9d78e5e6d8303bba1a064
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6560be3f6a5bb84f006f184f0c966747bb58e1a3
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e5c6f4fd4001562781e99bbfc7f1f0127187542
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f0d01e35dbb228084d5187212e32c91a30dcbeb
generic

ipc/shm: serialize orphan cleanup with shm_nattch updates - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/030bbc857bd51d4b25a90d931d3f8775ef22823a

Vendor Advisories for CVE-2026-52930(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-08ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-08ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 65× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-08 09:44 UTCVendor advisory
  5. 2026-09-08 09:44 UTCGHSA enrichment
  6. 2026-09-08 08:59 UTCEG score recompute
  7. 2026-09-08 08:59 UTCVendor advisory
  8. 2026-09-08 08:59 UTCGHSA enrichment
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 20:22 UTCEG score recompute
  15. 2026-08-30 20:22 UTCVendor advisory
  16. 2026-08-30 20:22 UTCGHSA enrichment
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-28 04:53 UTCEG score recompute
  20. 2026-08-28 04:53 UTCVendor advisory
  21. 2026-08-28 04:53 UTCGHSA enrichment
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 15:03 UTCEG score recompute
Show 75 more
  1. 2026-08-24 15:03 UTCVendor advisory
  2. 2026-08-24 15:03 UTCGHSA enrichment
  3. 2026-08-23 14:11 UTCEG score recompute
  4. 2026-08-23 14:11 UTCVendor advisory
  5. 2026-08-23 14:11 UTCGHSA enrichment
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 13:20 UTCEG score recompute
  8. 2026-08-22 13:20 UTCVendor advisory
  9. 2026-08-22 13:20 UTCGHSA enrichment
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-21 08:28 UTCEG score recompute
  12. 2026-08-21 08:28 UTCVendor advisory
  13. 2026-08-21 08:28 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 07:37 UTCEG score recompute
  16. 2026-08-20 07:37 UTCVendor advisory
  17. 2026-08-20 07:37 UTCGHSA enrichment
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-19 02:23 UTCEG score recompute
  20. 2026-08-19 02:23 UTCVendor advisory
  21. 2026-08-19 02:22 UTCGHSA enrichment
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 02:47 UTCEG score recompute
  25. 2026-08-17 02:47 UTCVendor advisory
  26. 2026-08-17 02:47 UTCGHSA enrichment
  27. 2026-08-16 14:56 UTCEPSS rescore
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-16 01:56 UTCEG score recompute
  30. 2026-08-16 01:56 UTCVendor advisory
  31. 2026-08-16 01:56 UTCGHSA enrichment
  32. 2026-08-15 01:30 UTCEPSS rescore
  33. 2026-08-15 01:04 UTCVendor advisory
  34. 2026-08-15 01:04 UTCGHSA enrichment
  35. 2026-08-14 00:13 UTCEG score recompute
  36. 2026-08-14 00:13 UTCVendor advisory
  37. 2026-08-14 00:13 UTCGHSA enrichment
  38. 2026-08-13 22:00 UTCEPSS rescore
  39. 2026-08-12 23:21 UTCEG score recompute
  40. 2026-08-12 23:21 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 22:30 UTCEG score recompute
  43. 2026-08-11 22:30 UTCVendor advisory
  44. 2026-08-11 22:30 UTCGHSA enrichment
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-10 21:39 UTCGHSA enrichment
  47. 2026-08-09 20:48 UTCEG score recompute
  48. 2026-08-09 20:48 UTCVendor advisory
  49. 2026-08-09 20:48 UTCGHSA enrichment
  50. 2026-08-09 13:46 UTCEPSS rescore
  51. 2026-08-08 19:57 UTCEG score recompute
  52. 2026-08-08 19:57 UTCVendor advisory
  53. 2026-08-08 19:57 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-07 19:05 UTCGHSA enrichment
  56. 2026-08-06 18:14 UTCEG score recompute
  57. 2026-08-06 18:14 UTCVendor advisory
  58. 2026-08-06 18:14 UTCGHSA enrichment
  59. 2026-08-06 13:47 UTCEPSS rescore
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-05 17:23 UTCGHSA enrichment
  62. 2026-08-04 15:13 UTCEG score recompute
  63. 2026-08-04 15:13 UTCVendor advisory
  64. 2026-08-04 15:13 UTCGHSA enrichment
  65. 2026-08-04 15:10 UTCEPSS rescore
  66. 2026-08-04 10:39 UTCEPSS rescore
  67. 2026-08-03 10:36 UTCEPSS rescore
  68. 2026-08-03 07:58 UTCGHSA enrichment
  69. 2026-08-02 05:20 UTCEG score recompute
  70. 2026-08-02 05:20 UTCVendor advisory
  71. 2026-08-02 05:20 UTCGHSA enrichment
  72. 2026-08-02 02:27 UTCEPSS rescore
  73. 2026-08-01 04:29 UTCVendor advisory
  74. 2026-08-01 04:28 UTCGHSA enrichment
  75. 2026-07-31 03:36 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-52930?
CVE-2026-52930 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ipc/shm: serialize orphan cleanup with shm_nattch updates shmdestroyorphaned() walks the shm idr under shm_ids(ns).rwsem, but that does not serialize all fields tested by shmmaydestroy(). In particular, shmnattch is updated while…
When was CVE-2026-52930 disclosed?
CVE-2026-52930 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52930 actively exploited?
CVE-2026-52930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-52930?
CVE-2026-52930 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52930?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52930, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52930

Explore →

Is Your Infrastructure Affected by CVE-2026-52930?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.