Bug 2492094 (CVE-2026-52923) - CVE-2026-52923 kernel: ipc: limit next_id allocation to the valid ID range
Summary: CVE-2026-52923 kernel: ipc: limit next_id allocation to the valid ID range
Keywords:
Status: NEW
Alias: CVE-2026-52923
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-24 08:01 UTC by OSIDB Bzimport
Modified: 2026-09-03 14:31 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:47248 0 None None None 2026-07-28 21:06:05 UTC
Red Hat Product Errata RHSA-2026:48386 0 None None None 2026-07-30 14:27:08 UTC
Red Hat Product Errata RHSA-2026:49031 0 None None None 2026-07-31 15:05:42 UTC
Red Hat Product Errata RHSA-2026:49212 0 None None None 2026-07-31 20:44:39 UTC
Red Hat Product Errata RHSA-2026:49851 0 None None None 2026-08-04 02:04:09 UTC
Red Hat Product Errata RHSA-2026:49857 0 None None None 2026-08-04 03:30:56 UTC
Red Hat Product Errata RHSA-2026:51603 0 None None None 2026-08-07 17:02:19 UTC
Red Hat Product Errata RHSA-2026:51604 0 None None None 2026-08-07 17:02:13 UTC
Red Hat Product Errata RHSA-2026:52649 0 None None None 2026-08-10 05:35:29 UTC
Red Hat Product Errata RHSA-2026:52764 0 None None None 2026-08-10 10:11:52 UTC
Red Hat Product Errata RHSA-2026:53330 0 None None None 2026-08-11 08:55:24 UTC
Red Hat Product Errata RHSA-2026:61692 0 None None None 2026-08-31 16:08:41 UTC
Red Hat Product Errata RHSA-2026:63189 0 None None None 2026-09-03 14:31:24 UTC

Description OSIDB Bzimport 2026-06-24 08:01:41 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-06-24 16:59:33 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062431-CVE-2026-52923-35fb@gregkh/T

Comment 3 errata-xmlrpc 2026-07-28 21:06:04 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

Via RHSA-2026:47248 https://access.redhat.com/errata/RHSA-2026:47248

Comment 4 errata-xmlrpc 2026-07-30 14:27:07 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:48386 https://access.redhat.com/errata/RHSA-2026:48386

Comment 5 errata-xmlrpc 2026-07-31 15:05:41 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:49031 https://access.redhat.com/errata/RHSA-2026:49031

Comment 6 errata-xmlrpc 2026-07-31 20:44:38 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:49212 https://access.redhat.com/errata/RHSA-2026:49212

Comment 7 errata-xmlrpc 2026-08-04 02:04:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:49851 https://access.redhat.com/errata/RHSA-2026:49851

Comment 8 errata-xmlrpc 2026-08-04 03:30:55 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:49857 https://access.redhat.com/errata/RHSA-2026:49857

Comment 9 errata-xmlrpc 2026-08-07 17:02:12 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:51604 https://access.redhat.com/errata/RHSA-2026:51604

Comment 10 errata-xmlrpc 2026-08-07 17:02:18 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:51603 https://access.redhat.com/errata/RHSA-2026:51603

Comment 11 errata-xmlrpc 2026-08-10 05:35:28 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:52649 https://access.redhat.com/errata/RHSA-2026:52649

Comment 12 errata-xmlrpc 2026-08-10 10:11:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:52764 https://access.redhat.com/errata/RHSA-2026:52764

Comment 13 errata-xmlrpc 2026-08-11 08:55:23 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:53330 https://access.redhat.com/errata/RHSA-2026:53330

Comment 14 Akiyoshi Kurita 2026-08-25 08:39:15 UTC
FYI:

A public LPE (Local Privilege Escalation) exploit for CVE-2026-52923 has been released, targeting RHEL 10.

Red Hat CVE database:
https://access.redhat.com/security/cve/cve-2026-52923

Public exploit:
https://github.com/NebuSec/CyberMeowfia/tree/main/security-research/Linux-CVE-2026-52923-RHEL-6.12.0-211.7.3.el10_2

Demo video:
https://x.com/nebusecurity/status/2092153813247705486

Relevant upstream/stable fix:
https://lore.kernel.org/linux-cve-announce/2026062431-CVE-2026-52923-35fb@gregkh/T/#u

Please re-evaluate the current status given that a working public LPE exploit is now available.

Comment 15 errata-xmlrpc 2026-08-31 16:08:39 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:61692 https://access.redhat.com/errata/RHSA-2026:61692

Comment 16 errata-xmlrpc 2026-09-03 14:31:23 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

Via RHSA-2026:63189 https://access.redhat.com/errata/RHSA-2026:63189


Note You need to log in before you can comment on or make changes to this bug.