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

bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-15269

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → Use After Free → disrupt the affected service
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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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.
Denial of serviceCWE-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-15269Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim The root cause of this bug is that when 'bpf_link_put' reduces the refcount of 'shim_link->link.link' to zero, the resource is considered released but may still be referenced via 'tr->progs_hlist' in 'cgroup_shim_find'. The actual cleanup of 'tr->progs_hlist' in 'bpf_shim_tramp_link_release' is deferred. During this window, another process can cause a use-after-free via 'bpf_trampoline_link_cgroup_shim'. Based on Martin KaFai Lau's suggestions, I have created a simple patch. To fix this: Add an atomic non-zero check in 'bpf_trampoline_link_cgroup_shim'. Only increment the refcount if it is not already zero. Testing: I verified the fix by adding a delay in 'bpf_shim_tramp_link_release' to make the bug easier to trigger: static void bpf_shim_tramp_link_release(struct bpf_link *link) { /* ... */ if (!shim_link->trampoline) return; + msleep(100); WARN_ON_ONCE(bpf_trampoline_unlink_prog(&shim_link->link, shim_link->trampoline, NULL)); bpf_trampoline_put(shim_link->trampoline); } Before the patch, running a PoC easily reproduced the crash(almost 100%) with a call trace similar to KaiyanM's report. After the patch, the bug no longer occurs even after millions of iterations.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0861Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, weitere nicht spezifizierte Auswirkungen zu verursachen und potentiell Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260401Security Bulletin 01 Apr 2026

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

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

d?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23321 https://www.cve.org/CVERecord?id=CVE-2026-23321 Référence CVE CVE-2026-23324 https://www.cve.org/CVERecord?id=CVE-2026-23324 Référence CVE CVE-2026-23325 https://www.cve.org/CVERecord?id=CVE-2026-23325 Référence CVE CVE-2026-23330 https://www.cve.org/CVERecord?id=CVE-2026-23330 Référence CVE CVE-2026-23334 https://www.cve.org/CVERecord?id=CVE-2026-23334 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23336 https://www.cve.org/CVERecord?id=CVE-2026-23336 Référence CVE CVE-2026-23339 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-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23321 https://www.cve.org/CVERecord?id=CVE-2026-23321 Référence CVE CVE-2026-23324 https://www.cve.org/CVERecord?id=CVE-2026-23324 Référence CVE CVE-2026-23325 https://www.cve.org/CVERecord?id=CVE-2026-23325 Référence CVE CVE-2026-23330 https://www.cve.org/CVERecord?id=CVE-2026-23330 Référence CVE CVE-2026-23334 https://www.cve.org/CVERecord?id=CVE-2026-23334 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23336 https://www.cve.org/CVERecord?id=CVE-2026-23336 Référence CVE CVE-2026-23339 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-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23321 https://www.cve.org/CVERecord?id=CVE-2026-23321 Référence CVE CVE-2026-23324 https://www.cve.org/CVERecord?id=CVE-2026-23324 Référence CVE CVE-2026-23325 https://www.cve.org/CVERecord?id=CVE-2026-23325 Référence CVE CVE-2026-23330 https://www.cve.org/CVERecord?id=CVE-2026-23330 Référence CVE CVE-2026-23334 https://www.cve.org/CVERecord?id=CVE-2026-23334 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23336 https://www.cve.org/CVERecord?id=CVE-2026-23336 Référence CVE CVE-2026-23339 https://www.cve.org/CVERecord?id=

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

26-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-22992, CVE-2026-22994, CVE-2026-23003, CVE-2026-23005, CVE-2026-23010, CVE-2026-23011, CVE-2026-23019, CVE-2026-23026, CVE-2026-23038, CVE-2026-23054, CVE-2026-23060, CVE-2026-23083, CVE-2026-23084, CVE-2026-23086, CVE-2026-23087, CVE-2026-23095, CVE-2026-23100, CVE-2026-23103, CVE-2026-23110, CVE-2026-23111, CVE-2026-23113, CVE-2026-23154, CVE-2026-23204, CVE-2026-23231, CVE-2026-23242, CVE-2026-23243, CVE-2026-23245, CVE-2026-23270, CVE-2026-23271, CVE-2026-23273, CVE-2026-23274, CVE-2026-23277, CVE-2026-23284, CVE-2026-23287, CVE-2026-23290, CVE-2026-23293, CVE-2026-23300, CVE-2026-23304, CVE-2026-23319, CVE-2026-23321, CVE-2026-23335, CVE-2026-23340, CVE-2026-23343, CVE-2026-23351, CVE-2026-23359, CVE-2026-23365, CVE-2026-23368, CVE-2026-23370, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381, CVE-2026-23391, CVE-2026-23392, CVE-2026-23397, CVE-2026-23398, CVE-2026-23414, CVE-2026-23422, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23446, CVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458, CVE-2026-23463, CVE-2026-23474, CVE-2026-23475, CVE-2026-27135, CVE-2026-31389, CVE-2026-31391, CVE-2026-31396, CVE-2026-31402, CVE-2026-31403, CVE-2026-31411, CVE-2026

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

d?id=CVE-2026-23300 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23306 https://www.cve.org/CVERecord?id=CVE-2026-23306 Référence CVE CVE-2026-23307 https://www.cve.org/CVERecord?id=CVE-2026-23307 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23321 https://www.cve.org/CVERecord?id=CVE-2026-23321 Référence CVE CVE-2026-23324 https://www.cve.org/CVERecord?id=CVE-2026-23324 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23336 https://www.cve.org/CVERecord?id=CVE-2026-23336 Référence CVE CVE-2026-23339 https://www.cve.org/CVERecord?id=CVE-2026-23339 Référence CVE CVE-2026-23340 https://www.cve.org/CVERecord?id=CVE-2026-23340 Référence CVE CVE-2026-23343 https://www.cve.org/CVERecord?id=CVE-2026-23343 Référence CVE CVE-2026-23351 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23307 Référence CVE CVE-2026-23308 https://www.cve.org/CVERecord?id=CVE-2026-23308 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23312 https://www.cve.org/CVERecord?id=CVE-2026-23312 Référence CVE CVE-2026-23313 https://www.cve.org/CVERecord?id=CVE-2026-23313 Référence CVE CVE-2026-23315 https://www.cve.org/CVERecord?id=CVE-2026-23315 Référence CVE CVE-2026-23316 https://www.cve.org/CVERecord?id=CVE-2026-23316 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23321 https://www.cve.org/CVERecord?id=CVE-2026-23321 Référence CVE CVE-2026-23324 https://www.cve.org/CVERecord?id=CVE-2026-23324 Référence CVE CVE-2026-23325 https://www.cve.org/CVERecord?id=CVE-2026-23325 Référence CVE CVE-2026-23330 https://www.cve.org/CVERecord?id=CVE-2026-23330 Référence CVE CVE-2026-23334 https://www.cve.org/CVERecord?id=CVE-2026-23334 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23336 https://www.cve.org/CVERecord?id=CVE-2026-23336 Référence CVE CVE-2026-23339 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23272 Référence CVE CVE-2026-23274 https://www.cve.org/CVERecord?id=CVE-2026-23274 Référence CVE CVE-2026-23277 https://www.cve.org/CVERecord?id=CVE-2026-23277 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23281 https://www.cve.org/CVERecord?id=CVE-2026-23281 Référence CVE CVE-2026-23292 https://www.cve.org/CVERecord?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23318 https://www.cve.org/CVERecord?id=CVE-2026-23318 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23361 https://www.cve.org/CVERecord?id=CVE-2026-23361 Référence CVE CVE-2026-23362 https://www.cve.org/CVERecord?id=CVE-2026-23362 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23382 https://www.cve.org/CVERecord?id=CVE-2026-23382 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=CVE-2026-23386 Référence CVE CVE-2026-23398 https://www.cve.org/CVERecord?id=CVE-2026-23398 Référence CVE CVE-2026-23413 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23274 Référence CVE CVE-2026-23277 https://www.cve.org/CVERecord?id=CVE-2026-23277 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23281 https://www.cve.org/CVERecord?id=CVE-2026-23281 Référence CVE CVE-2026-23292 https://www.cve.org/CVERecord?id=CVE-2026-23292 Référence CVE CVE-2026-23293 https://www.cve.org/CVERecord?id=CVE-2026-23293 Référence CVE CVE-2026-23297 https://www.cve.org/CVERecord?id=CVE-2026-23297 Référence CVE CVE-2026-23304 https://www.cve.org/CVERecord?id=CVE-2026-23304 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23319 https://www.cve.org/CVERecord?id=CVE-2026-23319 Référence CVE CVE-2026-23326 https://www.cve.org/CVERecord?id=CVE-2026-23326 Référence CVE CVE-2026-23335 https://www.cve.org/CVERecord?id=CVE-2026-23335 Référence CVE CVE-2026-23343 https://www.cve.org/CVERecord?id=CVE-2026-23343 Référence CVE CVE-2026-23361 https://www.cve.org/CVERecord?id=CVE-2026-23361 Référence CVE CVE-2026-23379 https://www.cve.org/CVERecord?id=CVE-2026-23379 Référence CVE CVE-2026-23381 https://www.cve.org/CVERecord?id=CVE-2026-23381 Référence CVE CVE-2026-23383 https://www.cve.org/CVERecord?id=CVE-2026-23383 Référence CVE CVE-2026-23386 https://www.cve.org/CVERecord?id=

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

ulletin de sécurité Microsoft CVE-2026-23300 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23303 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23304 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23306 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23307 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23310 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23312 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23315 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23317 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23318 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23319 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23324 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23334 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23336 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23340 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23343 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23347 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23351 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23352 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23356 du 26 mars 2026 Bulletin de sécurité Microsoft CVE-2026-23357 du 26 mars 2026 Bulletin de s

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-012925LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。bpf_trampoline_link_cgroup_shimにおけるUse-After-Free（UAF）問題が修正されました。このバグの根本原因は、'bpf_link_put'が'shim_link-link.link'の参照カウントをゼロに減らしたときにリソースを解放済みとみなす一方で、'cgroup_shim_find'内の'tr-progs_hlist'を介して依然として参照される可能性があることにあります。実際の'tr-progs_hlist'のクリーンアップは'bpf_shim_tramp_link_release'で遅延されます。この間に別のプロセスが'bpf_trampoline_link_cgroup_shim'を介してUse-After-Freeを引き起こす可能性があります。Martin KaFai Lauの提案に基づき、簡単なパッチが作成されました。修正内容は、'bpf_trampoline_link_cgroup_shim'で非ゼロの原子チェックを追加し、参照カウントがすでにゼロでない場合のみインクリメントすることです。テストでは、バグのトリガーを容易にするために'bpf_shim_tramp_link_release'に遅延(msleep(100))を挿入し、PoCを実行するとパッチ適用前はほぼ100%の確率でクラッシュが再現され、パッチ適用後は数百万回の反復実行後もバグが発生しなくなりました。

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.
Patch available
Affected
Fixed
Linux: < 6.0, 6.1.167 ≤ 6.1.*, 6.6.130 ≤ 6.6.*, 6.12.77 ≤ 6.12.*, 6.18.17 ≤ 6.18.*, 6.19.7 ≤ 6.19.*, 7.0 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 25 Mar 2026 · Last source change 14 Jul 2026, 12:46 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-15269
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
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. Affected versionsThe structured affected or fixed version information changed.
    Before
    69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 529e685e522b9d7fb379dbe6929dcdf520e34c8c; 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 9b02c5c4147f8af8ed783c8deb5df927a55c3951; 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < cfcfa0ca0212162aa472551266038e8fd6768cff; 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 3eeddb80191f7626ec1ef742bfff51ec3b0fa5c2; 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 4e8a0005d633a4adc98e3b65d5080f93b90d356b; 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 56145d237385ca0e7ca9ff7b226aaf2eb8ef368b; 6.0 · Fixed: < 6.0; 6.1.167 ≤ 6.1.*; 6.6.130 ≤ 6.6.*; 6.12.77 ≤ 6.12.*; 6.18.17 ≤ 6.18.*; 6.19.7 ≤ 6.19.*; 7.0 ≤ *
    After
    Linux: 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 529e685e522b9d7fb379dbe6929dcdf520e34c8c, 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 9b02c5c4147f8af8ed783c8deb5df927a55c3951, 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < cfcfa0ca0212162aa472551266038e8fd6768cff, 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 3eeddb80191f7626ec1ef742bfff51ec3b0fa5c2, 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 4e8a0005d633a4adc98e3b65d5080f93b90d356b, 69fd337a975c7e690dfe49d9cb4fe5ba1e6db44e < 56145d237385ca0e7ca9ff7b226aaf2eb8ef368b, 6.0 · Fixed: Linux: < 6.0, 6.1.167 ≤ 6.1.*, 6.6.130 ≤ 6.6.*, 6.12.77 ≤ 6.12.*, 6.18.17 ≤ 6.18.*, 6.19.7 ≤ 6.19.*, 7.0 ≤ *
    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-15269↗Vendor CSAF · Siemens ProductCERT↗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-23319 · cve.blacktree.nl