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-52923ipc: limit next_id allocation to the valid ID range

Description

In the Linux kernel, the following vulnerability has been resolved: ipc: limit next_id allocation to the valid ID range The checkpoint/restore sysctl path can request the next SysV IPC id through ids->next_id. ipc_idr_alloc() currently forwards that request to idr_alloc() with an open-ended upper bound. If the valid tail of the SysV IPC id space is full, the allocation can spill beyond ipc_mni. The returned SysV IPC id still uses the normal index encoding, so later lookup and removal can target the wrong slot. This leaves the real IDR entry behind and breaks the IDR state for the object. The bug is in ipc_idr_alloc() in the checkpoint/restore path. 1. ids->next_id is passed to: idr_alloc(&ids->ipcs_idr, new, ipcid_to_idx(next_id), 0, ...) 2. The zero upper bound makes the allocation effectively open-ended. Once the valid SysV IPC tail is occupied, idr_alloc() can spill past ipc_mni and allocate an entry beyond the valid IPC id range. 3. The new object id is still encoded with the narrower SysV IPC index width: new->id = (new->seq << ipcmni_seq_shift()) + idx 4. Later removal goes through ipc_rmid(), which uses: ipcid_to_idx(ipcp->id) That truncates the real IDR index. An object actually stored at a high index can then be removed as if it lived at a low in-range index. 5. For shared memory, shm_destroy() frees the current object anyway, but the real high IDR slot is left behind as a dangling pointer. 6. A subsequent walk of /proc/sysvipc/shm reaches the stale IDR entry and dereferences freed memory. Prevent this by bounding the requested allocation to ipc_mni so the checkpoint/restore path fails once the valid range is exhausted.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 4 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-52923, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
redhat-SADPADP (enrichment)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 3bbe2bb9111ce6967a951bfac79af142d816fae5
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 8c58a92849175f5e2ab7bc2734b3b89afe79f6ef
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < af24e202b543ded8a34f1d5d3db54eb916173f04
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 157ce2c6836ce0ff19108a819f38df061345425f
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 41058d4c3f63ab64901560a704882e0565f4e456
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < a3cc795129e5ec0f8948653a3bf471e7d8852f5e
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < bd4be70669af55b974860d13680348cfdf50bbed
    • affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • 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.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References25

Sources

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

Badge for a README or a ticket

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

Record last updated .