CVE Watchtower

CVE-2026-52923Linux Linux Kernel Missing Release of Memory after Effective Lifetime

NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Vulnerability Summary

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.
Severity Level
HIGH(7.8)
Published Date
Jun 24, 2026
Last Modified
Oct 19, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.22%Probability
Root Weakness (CWE)
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required.
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 7.8 (HIGH)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Linux Linux Kernel >= 3.8.1 and < 5.10.259
  • Linux Linux Kernel >= 5.11 and < 5.15.210
  • Linux Linux Kernel >= 5.16 and < 6.1.176
  • Linux Linux Kernel >= 6.2 and < 6.6.143
  • Linux Linux Kernel >= 6.7 and < 6.12.93
  • Linux Linux Kernel >= 6.13 and < 6.18.35
  • Linux Linux Kernel >= 6.19 and < 7.0.12
  • Linux Linux Kernel
Patched Versions
  • Linux Linux Kernel 5.10.259
  • Linux Linux Kernel 5.15.210
  • Linux Linux Kernel 6.1.176
  • Linux Linux Kernel 6.6.143
  • Linux Linux Kernel 6.12.93
  • Linux Linux Kernel 6.18.35
  • Linux Linux Kernel 7.0.12

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Linux Linux Kernel and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Jun 24, 2026Published
  • Oct 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-52923. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

External References

Data last checked: Nov 19, 2026 16:14 UTC