Linux Kernel: security vulnerability (CVE-2026-52923)
Published Last modified Sources: Debian LTS, BSI, SUSE, Ubuntu, Siemens ProductCERT, Red Hat, CVE.org, Msrc Update Guide
What is affected, what to do
A flaw was found in the Linux kernel. The `ipc_idr_alloc()` function, used in the checkpoint/restore path for SysV Inter-Process Communication (IPC) ID allocation, does not properly limit ID allocation to the valid range.
Update Linux Kernel to version 5.10.259, Linux Kernel to version 5.15.210, Linux Kernel to version 6.1.176.
- Affected
- Linux Kernel
lt 3.8..5.10.259 - Linux Kernel
lt 5.11..5.15.210 - Linux Kernel
lt 5.16..6.1.176 - Linux Kernel
lt 6.2..6.6.143 - Linux Kernel
lt 6.7..6.12.93 - Linux Kernel
lt 6.13..6.18.35 - Linux Kernel
lt 6.19..7.0.12
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.259 - Linux Kernel
5.15.210 - Linux Kernel
6.1.176 - Linux Kernel
6.6.143 - Linux Kernel
6.12.93 - Linux Kernel
6.18.35 - Linux Kernel
7.0.12 - Linux Kernel
7.1
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
7.8
CVSS v3
Severity High on the scale from 0 to 10.
Source: Debian LTS, BSI, SUSE, Ubuntu, Siemens ProductCERT, Red Hat, CVE.org, Msrc Update Guide
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 12.0
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 59.59 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 12.0
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 16 October 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-20
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in the Linux kernel. The `ipc_idr_alloc()` function, used in the checkpoint/restore path for SysV Inter-Process Communication (IPC) ID allocation, does not properly limit ID allocation to the valid range. This can result in the system attempting to dereference freed memory, leading to a use-after-free vulnerability. This issue could potentially cause system instability or information disclosure.
Source: Debian LTS Advisories, BSI WID Portal, BSI CSAF, suse_csaf, Ubuntu Security Notices, siemens_advisory, redhat_csaf, cvelistv5, Microsoft Security Update Guide, NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| IBM | DataPower Gateway |
|
|
| IBM | QRadar SIEM |
|
|
| Siemens | SIMATIC S7 |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | bullseye |
| Linux | debian | linux-6.1 | bullseye |
| Linux | linux | linux_kernel | 3.8 |
| Linux | linux | linux_kernel | 7.1 |
| Linux | linux | linux_kernel | — |
Weakness classes (CWE)
CWE-20Improper Input Validation
Class
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Entry at MITRE CWE-20
References & sources
- git.kernel.orgstable/c/3bbe2bb9111ce6967a951bfac79af142d816fae5Patch
- git.kernel.orgstable/c/8c58a92849175f5e2ab7bc2734b3b89afe79f6efPatch
- git.kernel.orgstable/c/af24e202b543ded8a34f1d5d3db54eb916173f04Patch
- git.kernel.orgstable/c/157ce2c6836ce0ff19108a819f38df061345425fPatch
- git.kernel.orgstable/c/41058d4c3f63ab64901560a704882e0565f4e456Patch
- git.kernel.orgstable/c/a3cc795129e5ec0f8948653a3bf471e7d8852f5ePatch
- git.kernel.orgstable/c/bd4be70669af55b974860d13680348cfdf50bbedPatch
- git.kernel.orgstable/c/fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139Patch
- access.redhat.comsecurity/cve/CVE-2026-52923Vulnerability database, x_refsource_REDHAT, Third-party advisory
- bugzilla.redhat.comRHBZ#2492094Issue tracking, x_refsource_REDHAT, Issue tracking, Third-party advisory
- security.access.redhat.comdata/csaf/v2/vex/2026/cve-2026-52923.jsonx_sadp-csaf-vex, Third-party advisory
- access.redhat.comerrata/RHSA-2026:51603Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:48386Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:49031Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:49212Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:49857Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:47248Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:49851Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:51604Vendor advisory, x_refsource_REDHAT
- access.redhat.comerrata/RHSA-2026:52764Vendor advisory, x_refsource_REDHAT
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
Weakness type: CWE-20
Show the original change
Individual changes of this event as published by NVD Type Action Before After Weakness type (CWE) added —CWE-20Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-52923","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-16T15:22:46.408213Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedSiemens ADP
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/52xxx/CVE-2026-52923.json">CVE-2026-52923</a>Reference added —https://cert-portal.siemens.com/productcert/html/ssa-784472.htmlSource identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
Record modifiedRed Hat ADP
New references:Show the original change
Individual changes of this event as published by NVD Type Action Before After Reference added —https://access.redhat.com/errata/RHSA-2026:61692Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
Record modifiedRed Hat ADP
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://access.redhat.com/errata/RHSA-2026:52649Reference added —https://access.redhat.com/errata/RHSA-2026:52764Affected versions (publisher) changed Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support (+9)Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support (+11)Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
Show 4 older changes
Record modifiedRed Hat ADP
New references:Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://access.redhat.com/errata/RHSA-2026:49857Affected versions (publisher) changed Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 9 (+9)Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support (+9)Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
Record modifiedRed Hat ADP
New references:Show the original change
Individual changes of this event as published by NVD Type Action Before After Reference added —https://access.redhat.com/errata/RHSA-2026:49851Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
Record modifiedRed Hat ADP
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://access.redhat.com/errata/RHSA-2026:48386Reference added —https://access.redhat.com/errata/RHSA-2026:49031Reference added —https://access.redhat.com/errata/RHSA-2026:49212Affected versions (publisher) changed Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 10 (+7)Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 9 (+9)Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/157ce2c6836ce0ff19108a819f38df061345425f
- https://git.kernel.org/stable/c/3bbe2bb9111ce6967a951bfac79af142d816fae5
- https://git.kernel.org/stable/c/41058d4c3f63ab64901560a704882e0565f4e456
- https://git.kernel.org/stable/c/8c58a92849175f5e2ab7bc2734b3b89afe79f6ef
and 4 more references
Show 10 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Linux, LinuxDescription added —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.Reference added —https://git.kernel.org/stable/c/157ce2c6836ce0ff19108a819f38df061345425fReference added —https://git.kernel.org/stable/c/3bbe2bb9111ce6967a951bfac79af142d816fae5Reference added —https://git.kernel.org/stable/c/41058d4c3f63ab64901560a704882e0565f4e456Reference added —https://git.kernel.org/stable/c/8c58a92849175f5e2ab7bc2734b3b89afe79f6efReference added —https://git.kernel.org/stable/c/a3cc795129e5ec0f8948653a3bf471e7d8852f5eReference added —https://git.kernel.org/stable/c/af24e202b543ded8a34f1d5d3db54eb916173f04Reference added —https://git.kernel.org/stable/c/bd4be70669af55b974860d13680348cfdf50bbedReference added —https://git.kernel.org/stable/c/fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-52923"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-52923.svg?lang=en" alt="CVE-2026-52923 – NEOSEC Intel" height="20"></a>