CVE-2026-52923

Technical 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 stil

Remediation

Check the references section for vendor advisories and patches from linux. Update linux_kernel to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

References