BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-52923High confidence

ipc: limit next_id allocation to the valid ID range

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 4 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.20% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-52923 · CSAF 2.0 · revision 36 · interimSUSE Product Security TeamCVE-2026-52923
128 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
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 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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-52923 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ipc: limit next_id allocation to the valid ID range
47 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
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.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-38726

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Expired Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-825 ↗

CWE-825: Expired Pointer Dereference. The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-825
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-38726Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2056Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Angriff auszulösen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52917 https://www.cve.org/CVERecord?id=CVE-2026-52917 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52930 https://www.cve.org/CVERecord?id=CVE-2026-52930 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52917 https://www.cve.org/CVERecord?id=CVE-2026-52917 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52930 https://www.cve.org/CVERecord?id=CVE-2026-52930 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46115 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52946 https://www.cve.org/CVERecord?id=CVE-2026-52946 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52917 https://www.cve.org/CVERecord?id=CVE-2026-52917 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52930 https://www.cve.org/CVERecord?id=CVE-2026-52930 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46091 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52946 https://www.cve.org/CVERecord?id=CVE-2026-52946 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1120Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-31759 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=CVE-2026-46037 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53205 https://www.cve.org/CVERecord?id=CVE-2026-53205 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53233 https://www.cve.org/CVERecord?id=CVE-2026-53233 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1118Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-43450 Référence CVE CVE-2026-43454 https://www.cve.org/CVERecord?id=CVE-2026-43454 Référence CVE CVE-2026-45970 https://www.cve.org/CVERecord?id=CVE-2026-45970 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46099 https://www.cve.org/CVERecord?id=CVE-2026-46099 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46145 https://www.cve.org/CVERecord?id=CVE-2026-46145 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53026 https://www.cve.org/CVERecord?id=CVE-2026-53026 Référence CVE CVE-2026-53053 https://www.cve.org/CVERecord?id=CVE-2026-53053 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53153 https://www.cve.org/CVERecord?id=CVE-2026-53153 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2026-49978 Référence CVE CVE-2026-5038 https://www.cve.org/CVERecord?id=CVE-2026-5038 Référence CVE CVE-2026-50645 https://www.cve.org/CVERecord?id=CVE-2026-50645 Référence CVE CVE-2026-50721 https://www.cve.org/CVERecord?id=CVE-2026-50721 Référence CVE CVE-2026-50722 https://www.cve.org/CVERecord?id=CVE-2026-50722 Référence CVE CVE-2026-50734 https://www.cve.org/CVERecord?id=CVE-2026-50734 Référence CVE CVE-2026-5078 https://www.cve.org/CVERecord?id=CVE-2026-5078 Référence CVE CVE-2026-5079 https://www.cve.org/CVERecord?id=CVE-2026-5079 Référence CVE CVE-2026-5260 https://www.cve.org/CVERecord?id=CVE-2026-5260 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53404 https://www.cve.org/CVERecord?id=CVE-2026-53404 Référence CVE CVE-2026-53434 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46292 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46324 https://www.cve.org/CVERecord?id=CVE-2026-46324 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-52910 https://www.cve.org/CVERecord?id=CVE-2026-52910 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52930 https://www.cve.org/CVERecord?id=CVE-2026-52930 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52942 https://www.cve.org/CVERecord?id=CVE-2026-52942 Référence CVE CVE-2026-52947 https://www.cve.org/CVERecord?id=CVE-2026-52947 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52967 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-52913 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52932 https://www.cve.org/CVERecord?id=CVE-2026-52932 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1028Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2025-71072 Référence CVE CVE-2025-71131 https://www.cve.org/CVERecord?id=CVE-2025-71131 Référence CVE CVE-2026-23415 https://www.cve.org/CVERecord?id=CVE-2026-23415 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31530 https://www.cve.org/CVERecord?id=CVE-2026-31530 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-45991 https://www.cve.org/CVERecord?id=CVE-2026-45991 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-63887 https://www.cve.org/CVERecord?id=CVE-2026-63887 Référence CVE CVE-2026-64300 https://www.cve.org/CVERecord?id=CVE-2026-64300 Référence CVE CVE-2026-64368 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0983Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-31787 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43186 https://www.cve.org/CVERecord?id=CVE-2026-43186 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64531 https://www.cve.org/CVERecord?id=CVE-2026-64531 Gestion détaillée du document le 07 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.f

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0955Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53281 https://www.cve.org/CVERecord?id=CVE-2026-53281 Référence CVE CVE-2026-57231 https://www.cve.org/CVERecord?id=CVE-2026-57231 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0956Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46314 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-52913 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52932 https://www.cve.org/CVERecord?id=CVE-2026-52932 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52934 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-52904 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52948 https://www.cve.org/CVERecord?id=CVE-2026-52948 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-52913 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52932 https://www.cve.org/CVERecord?id=CVE-2026-52932 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52934 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0900Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46275 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0864Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46320 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53040 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-52914 Référence CVE CVE-2026-52915 https://www.cve.org/CVERecord?id=CVE-2026-52915 Référence CVE CVE-2026-52916 https://www.cve.org/CVERecord?id=CVE-2026-52916 Référence CVE CVE-2026-52917 https://www.cve.org/CVERecord?id=CVE-2026-52917 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52921 https://www.cve.org/CVERecord?id=CVE-2026-52921 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52927 https://www.cve.org/CVERecord?id=CVE-2026-52927 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52930 https://www.cve.org/CVERecord?id=CVE-2026-52930 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0812Multiples vulnérabilités dans Microsoft Azure Linux

ent Référence CERTFR-2026-AVI-0812 Titre Multiples vulnérabilités dans Microsoft Azure Linux Date de la première version 29 juin 2026 Date de la dernière version 29 juin 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-52912 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52913 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52915 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52916 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52919 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52921 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52922 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52923 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52924 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52926 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52927 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52930 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52931 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52934 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52941 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52942 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52943 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52947 du 27 juin 2026 Bulletin de s

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023085LinuxのLinux Kernelにおける複数の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。checkpoint/restoreのsysctlパスは、ids-＞next_idを介して次のSysV IPC IDを要求できますが、ipc: next_idの割り当てを有効なID範囲内に制限する必要があります。ipc_idr_alloc()は現在、その要求をidr_alloc()に対し上限を設けずに転送しています。SysV IPC ID空間の有効な末尾が満杯の場合、割り当てがipc_mniを超えてしまうことがあります。返されるSysV IPC IDは通常のインデックスエンコーディングを使用しているため、後の検索や削除が誤ったスロットを対象にしてしまいます。これにより実際のIDRエントリが残り、オブジェクトのIDR状態が破損します。バグはcheckpoint/restoreパスのipc_idr_alloc()に存在します。具体的には以下の問題があります。1. ids-＞next_idは以下に渡されます：idr_alloc(&ids-＞ipcs_idr, new, ipcid_to_idx(next_id), 0, ...)2. 上限が0であるため、割り当ては事実上無制限になります。有効なSysV IPCの末尾が既に使用されている場合、idr_alloc()はipc_mniを超えてエントリを割り当ててしまうことがあります。3. 新しいオブジェクトIDは狭いSysV IPCインデックス幅でエンコードされたままです：new-＞id = (new-＞seq ＜＜ ipcmni_seq_shift()) + idx4. その後の削除はipc_rmid()を通じて行われ、そこでipcid_to_idx(ipcp-＞id)が使われます。これは実際のIDRインデックスを切り捨てるため、高いインデックスに格納されたオブジェクトが低い有効範囲内のインデックスとして削除されてしまいます。5. 共有メモリではshm_destroy()が現在のオブジェクトを解放しますが、実際の高いIDRスロットはダングリングポインタとして残ります。6. その後、/proc/sysvipc/shmを巡回すると古いIDRエントリに到達し、解放済みメモリの参照が発生します。この問題は、要求された割り当てをipc_mniで制限し、有効範囲が尽きた場合にcheckpoint/restoreパスの処理を失敗させることで防止できます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.8, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 24 Jun 2026 · Last source change 4 Sept 2026, 12:04 UTC · CWE-825 · Expired Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-38726
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceOther authority
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:63189.
    Before
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 7 more references
    After
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 6 more references
    git.kernel.org ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:63189.
    Before
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 6 more references
    After
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 7 more references
    git.kernel.org ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:61692.
    Before
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 7 more references
    After
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 6 more references
    git.kernel.org ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:61692.
    Before
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 6 more references
    After
    patch: git.kernel.org/157ce2c6836ce0ff19108a819f38df061345425f · patch: git.kernel.org/3bbe2bb9111ce6967a951bfac79af142d816fae5 · patch: git.kernel.org/41058d4c3f63ab64901560a704882e0565f4e456 · 7 more references
    git.kernel.org ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; bpftool as a component of Red Hat Enterprise Linux 7; kernel as a component of Red Hat Enterprise Linux 7; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7; kernel-bootwrapper as a component of Red Hat Enterprise Linux 7; kernel-debug as a component of Red Hat Enterprise Linux 7; kernel-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-devel as a component of Red Hat Enterprise Linux 7; kernel-doc as a component of Red Hat Enterprise Linux 7; kernel-headers as a component of Red Hat Enterprise Linux 7; kernel-kdump as a component of Red Hat Enterprise Linux 7; kernel-kdump-devel as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 7; kernel-rt-debug as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-devel as a component of Red Hat Enterprise Linux 7; and 34 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debug-devel-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debug-devel-matched-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debuginfo-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-devel-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-devel-matched-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.95.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.95.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.95.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.95.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.95.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.95.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.95.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.95.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.95.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.95.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.95.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.95.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-aarch64-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-ppc64le-0:6.12.0-55.95.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-s390x-0:6.12.0-55.95.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-x86_64-0:6.12.0-55.95.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.95.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.95.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.95.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.95.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); and 1900 more
    After
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; kernel-rt as a component of Red Hat Enterprise Linux 7; kernel-rt-debug as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-doc as a component of Red Hat Enterprise Linux 7; kernel-rt-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt-trace as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-devel as a component of Red Hat Enterprise Linux 7; kernel-rt-trace-kvm as a component of Red Hat Enterprise Linux 7; kernel-rt.src as a component of Red Hat Enterprise Linux 7; kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9; and 17 more · Fixed: bpftool-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-0:3.10.0-1160.159.1.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-debuginfo-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-debuginfo-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-debuginfo-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); bpftool-debuginfo-0:3.10.0-1160.159.1.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-0:3.10.0-1160.159.1.el7.src as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-0:3.10.0-1160.159.1.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-abi-whitelists-0:3.10.0-1160.159.1.el7.noarch as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-bootwrapper-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-bootwrapper-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-0:3.10.0-1160.159.1.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-debuginfo-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-debuginfo-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-debuginfo-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-debuginfo-0:3.10.0-1160.159.1.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-devel-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-devel-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debug-devel-0:3.10.0-1160.159.1.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debuginfo-0:3.10.0-1160.159.1.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debuginfo-0:3.10.0-1160.159.1.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS); kernel-debuginfo-0:3.10.0-1160.159.1.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7 ELS); and 1993 more
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    03f595668017f1a1fb971c02fc37140bc6e7bb1c < 3bbe2bb9111ce6967a951bfac79af142d816fae5; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 8c58a92849175f5e2ab7bc2734b3b89afe79f6ef; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < af24e202b543ded8a34f1d5d3db54eb916173f04; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 157ce2c6836ce0ff19108a819f38df061345425f; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 41058d4c3f63ab64901560a704882e0565f4e456; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < a3cc795129e5ec0f8948653a3bf471e7d8852f5e; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < bd4be70669af55b974860d13680348cfdf50bbed; 03f595668017f1a1fb971c02fc37140bc6e7bb1c < fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139 · Fixed: < 3.8; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.143 ≤ 6.6.*; 6.12.93 ≤ 6.12.*; 6.18.35 ≤ 6.18.*; 7.0.12 ≤ 7.0.*
    After
    Linux: 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 3bbe2bb9111ce6967a951bfac79af142d816fae5, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 8c58a92849175f5e2ab7bc2734b3b89afe79f6ef, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < af24e202b543ded8a34f1d5d3db54eb916173f04, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 157ce2c6836ce0ff19108a819f38df061345425f, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < 41058d4c3f63ab64901560a704882e0565f4e456, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < a3cc795129e5ec0f8948653a3bf471e7d8852f5e, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < bd4be70669af55b974860d13680348cfdf50bbed, 03f595668017f1a1fb971c02fc37140bc6e7bb1c < fa0b9b2b7ae3539908d69c2b9ac0d144d9bc5139, 3.8 · Fixed: Linux: < 3.8, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-38726↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-52923 · cve.blacktree.nl