CVE-2026-52923ipc: limit next_id allocation to the valid ID range
- 7.8HighCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 4 months later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| redhat-SADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS: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
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 3bbe2bb9111ce6967a951bfac79af142d816fae5
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 8c58a92849175f5e2ab7bc2734b3b89afe79f6ef
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < af24e202b543ded8a34f1d5d3db54eb916173f04
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 157ce2c6836ce0ff19108a819f38df061345425f
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < 41058d4c3f63ab64901560a704882e0565f4e456
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < a3cc795129e5ec0f8948653a3bf471e7d8852f5e
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < bd4be70669af55b974860d13680348cfdf50bbed
- affected 03f595668017f1a1fb971c02fc37140bc6e7bb1c – < fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139
- 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
- https://git.kernel.org/stable/c/3bbe2bb9111ce6967a951bfac79af142d816fae5 (opens in a new tab)
- https://git.kernel.org/stable/c/8c58a92849175f5e2ab7bc2734b3b89afe79f6ef (opens in a new tab)
- https://git.kernel.org/stable/c/af24e202b543ded8a34f1d5d3db54eb916173f04 (opens in a new tab)
- https://git.kernel.org/stable/c/157ce2c6836ce0ff19108a819f38df061345425f (opens in a new tab)
- https://git.kernel.org/stable/c/41058d4c3f63ab64901560a704882e0565f4e456 (opens in a new tab)
- https://git.kernel.org/stable/c/a3cc795129e5ec0f8948653a3bf471e7d8852f5e (opens in a new tab)
- https://git.kernel.org/stable/c/bd4be70669af55b974860d13680348cfdf50bbed (opens in a new tab)
- https://git.kernel.org/stable/c/fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139 (opens in a new tab)
- https://access.redhat.com/security/cve/CVE-2026-52923 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2492094 (opens in a new tab)issue-trackingx_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52923.json (opens in a new tab)x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:61692 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:63189 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:52764 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:53330 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:51603 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:48386 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:49031 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:49212 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:49857 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:47248 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:52649 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:49851 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:51604 (opens in a new tab)vendor-advisoryx_refsource_REDHAT
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38726 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-52923)Record last updated .