BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2023-52879High confidence

tracing: Have trace_event_file have ref counters

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.

21 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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.

1 current
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: tracing: Have trace_event_file have ref counters
Remediation
No remediation text is recorded.
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-2023-59592

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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: tracing: Have trace_event_file have ref counters The following can crash the kernel: # cd /sys/kernel/tracing # echo 'p:sched schedule' > kprobe_events # exec 5>>events/kprobes/sched/enable # > kprobe_events # exec 5>&- The above commands: 1. Change directory to the tracefs directory 2. Create a kprobe event (doesn't matter what one) 3. Open bash file descriptor 5 on the enable file of the kprobe event 4. Delete the kprobe event (removes the files too) 5. Close the bash file descriptor 5 The above causes a crash! BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 877 Comm: bash Not tainted 6.5.0-rc4-test-00008-g2c6b6b1029d4-dirty #186 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:tracing_release_file_tr+0xc/0x50 What happens here is that the kprobe event creates a trace_event_file "file" descriptor that represents the file in tracefs to the event. It maintains state of the event (is it enabled for the given instance?). Opening the "enable" file gets a reference to the event "file" descriptor via the open file descriptor. When the kprobe event is deleted, the file is also deleted from the tracefs system which also frees the event "file" descriptor. But as the tracefs file is still opened by user space, it will not be totally removed until the final dput() is called on it. But this is not true with the event "file" descriptor that is already freed. If the user does a write to or simply closes the file descriptor it will reference the event "file" descriptor that was just freed, causing a use-after-free bug. To solve this, add a ref count to the event "file" descriptor as well as a new flag called "FREED". The "file" will not be freed until the last reference is released. But the FREE flag will be set when the event is removed to prevent any more modifications to that event from happening, even if there's still a reference to the event "file" descriptor.

What

In the Linux kernel, the following vulnerability has been resolved: tracing: Have trace_event_file have ref counters The following can crash the kernel: # cd /sys/kernel/tracing # echo 'p:sched schedule' > kprobe_events # exec 5>>events/kprobes/sched/enable # > kprobe_events # exec 5>&- The above commands: 1. Change directory to the tracefs directory 2. Create a kprobe event (doesn't matter what one) 3. Open bash file descriptor 5 on the enable file of the kprobe event 4. Delete the kprobe event (removes the files too) 5. Close the bash file descriptor 5 The above causes a crash! BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 877 Comm: bash Not tainted 6.5.0-rc4-test-00008-g2c6b6b1029d4-dirty #186 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:tracing_release_file_tr+0xc/0x50 What happens here is that the kprobe event creates a trace_event_file "file" descriptor that represents the file in tracefs to the event. It maintains state of the event (is it enabled for the given instance?). Opening the "enable" file gets a reference to the event "file" descriptor via the open file descriptor. When the kprobe event is deleted, the file is also deleted from the tracefs system which also frees the event "file" descriptor. But as the tracefs file is still opened by user space, it will not be totally removed until the final dput() is called on it. But this is not true with the event "file" descriptor that is already freed. If the user does a write to or simply closes the file descriptor it will reference the event "file" descriptor that was just freed, causing a use-after-free bug. To solve this, add a ref count to the event "file" descriptor as well as a new flag called "FREED". The "file" will not be freed until the last reference is released. But the FREE flag will be set when the event is removed to prevent any more modifications to that event from happening, even if there's still a reference to the event "file" descriptor.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: tracing: Have trace_event_file have ref counters The following can crash the kernel: # cd /sys/kernel/tracing # echo 'p:sched schedule' > kprobe_events # exec 5>>events/kprobes/sched/enable # > kprobe_events # exec 5>&- The above commands: 1. Change directory to the tracefs directory 2. Create a kprobe event (doesn't matter what one) 3. Open bash file descriptor 5 on the enable file of the kprobe event 4. Delete the kprobe event (removes the files too) 5. Close the bash file descriptor 5 The above causes a crash! BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 877 Comm: bash Not tainted 6.5.0-rc4-test-00008-g2c6b6b1029d4-dirty #186 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:tracing_release_file_tr+0xc/0x50 What happens here is that the kprobe event creates a trace_event_file "file" descriptor that represents the file in tracefs to the event. It maintains state of the event (is it enabled for the given instance?). Opening the "enable" file gets a reference to the event "file" descriptor via the open file descriptor. When the kprobe event is deleted, the file is also deleted from the tracefs system which also frees the event "file" descriptor. But as the tracefs file is still opened by user space, it will not be totally removed until the final dput() is called on it. But this is not true with the event "file" descriptor that is already freed. If the user does a write to or simply closes the file descriptor it will reference the event "file" descriptor that was just freed, causing a use-after-free bug. To solve this, add a ref count to the event "file" descriptor as well as a new flag called "FREED". The "file" will not be freed until the last reference is released. But the FREE flag will be set when the event is removed to prevent any more modifications to that event from happening, even if there's still a reference to the event "file" descriptor.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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-476
A

Official authority intelligence

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

BSI · German · WID-SEC-W-2024-1197Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52732 Référence CVE CVE-2023-52737 https://www.cve.org/CVERecord?id=CVE-2023-52737 Référence CVE CVE-2023-52749 https://www.cve.org/CVERecord?id=CVE-2023-52749 Référence CVE CVE-2023-52751 https://www.cve.org/CVERecord?id=CVE-2023-52751 Référence CVE CVE-2023-52761 https://www.cve.org/CVERecord?id=CVE-2023-52761 Référence CVE CVE-2023-52829 https://www.cve.org/CVERecord?id=CVE-2023-52829 Référence CVE CVE-2023-52831 https://www.cve.org/CVERecord?id=CVE-2023-52831 Référence CVE CVE-2023-52837 https://www.cve.org/CVERecord?id=CVE-2023-52837 Référence CVE CVE-2023-52857 https://www.cve.org/CVERecord?id=CVE-2023-52857 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52905 https://www.cve.org/CVERecord?id=CVE-2023-52905 Référence CVE CVE-2023-52916 https://www.cve.org/CVERecord?id=CVE-2023-52916 Référence CVE CVE-2023-52920 https://www.cve.org/CVERecord?id=CVE-2023-52920 Référence CVE CVE-2023-52921 https://www.cve.org/CVERecord?id=CVE-2023-52921 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2023-52939 https://www.cve.org/CVERecord?id=CVE-2023-52939 Référence CVE CVE-2023-52981 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52732 Référence CVE CVE-2023-52737 https://www.cve.org/CVERecord?id=CVE-2023-52737 Référence CVE CVE-2023-52749 https://www.cve.org/CVERecord?id=CVE-2023-52749 Référence CVE CVE-2023-52751 https://www.cve.org/CVERecord?id=CVE-2023-52751 Référence CVE CVE-2023-52761 https://www.cve.org/CVERecord?id=CVE-2023-52761 Référence CVE CVE-2023-52829 https://www.cve.org/CVERecord?id=CVE-2023-52829 Référence CVE CVE-2023-52831 https://www.cve.org/CVERecord?id=CVE-2023-52831 Référence CVE CVE-2023-52837 https://www.cve.org/CVERecord?id=CVE-2023-52837 Référence CVE CVE-2023-52857 https://www.cve.org/CVERecord?id=CVE-2023-52857 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52905 https://www.cve.org/CVERecord?id=CVE-2023-52905 Référence CVE CVE-2023-52916 https://www.cve.org/CVERecord?id=CVE-2023-52916 Référence CVE CVE-2023-52920 https://www.cve.org/CVERecord?id=CVE-2023-52920 Référence CVE CVE-2023-52921 https://www.cve.org/CVERecord?id=CVE-2023-52921 Référence CVE CVE-2023-52926 https://www.cve.org/CVERecord?id=CVE-2023-52926 Référence CVE CVE-2023-52939 https://www.cve.org/CVERecord?id=CVE-2023-52939 Référence CVE CVE-2023-52981 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2023-52858 Référence CVE CVE-2023-52864 https://www.cve.org/CVERecord?id=CVE-2023-52864 Référence CVE CVE-2023-52865 https://www.cve.org/CVERecord?id=CVE-2023-52865 Référence CVE CVE-2023-52867 https://www.cve.org/CVERecord?id=CVE-2023-52867 Référence CVE CVE-2023-52868 https://www.cve.org/CVERecord?id=CVE-2023-52868 Référence CVE CVE-2023-52871 https://www.cve.org/CVERecord?id=CVE-2023-52871 Référence CVE CVE-2023-52873 https://www.cve.org/CVERecord?id=CVE-2023-52873 Référence CVE CVE-2023-52875 https://www.cve.org/CVERecord?id=CVE-2023-52875 Référence CVE CVE-2023-52876 https://www.cve.org/CVERecord?id=CVE-2023-52876 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-52887 https://www.cve.org/CVERecord?id=CVE-2023-52887 Référence CVE CVE-2023-52917 https://www.cve.org/CVERecord?id=CVE-2023-52917 Référence CVE CVE-2023-52919 https://www.cve.org/CVERecord?id=CVE-2023-52919 Référence CVE CVE-2023-5678 https://www.cve.org/CVERecord?id=CVE-2023-5678 Référence CVE CVE-2023-5717 https://www.cve.org/CVERecord?id=CVE-2023-5717 Référence CVE CVE-2023-6040 https://www.cve.org/CVERecord?id=CVE-2023-6040 Référence CVE CVE-2023-6121 https://www.cve.org/CVERecord?id=CVE-202

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

d?id=CVE-2023-52870 Référence CVE CVE-2023-52871 https://www.cve.org/CVERecord?id=CVE-2023-52871 Référence CVE CVE-2023-52872 https://www.cve.org/CVERecord?id=CVE-2023-52872 Référence CVE CVE-2023-52873 https://www.cve.org/CVERecord?id=CVE-2023-52873 Référence CVE CVE-2023-52874 https://www.cve.org/CVERecord?id=CVE-2023-52874 Référence CVE CVE-2023-52875 https://www.cve.org/CVERecord?id=CVE-2023-52875 Référence CVE CVE-2023-52876 https://www.cve.org/CVERecord?id=CVE-2023-52876 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52880 https://www.cve.org/CVERecord?id=CVE-2023-52880 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-52882 https://www.cve.org/CVERecord?id=CVE-2023-52882 Référence CVE CVE-2023-52883 https://www.cve.org/CVERecord?id=CVE-2023-52883 Référence CVE CVE-2023-52884 https://www.cve.org/CVERecord?id=CVE-2023-52884 Référence CVE CVE-2023-52885 https://www.cve.org/CVERecord?id=CVE-2023-52885 Référence CVE CVE-2023-52886 https://www.cve.org/CVERecord?id=CVE-2023-52886 Référence CVE CVE-2023-6238 https://www.cve.org/CVERecord?id=C

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

d?id=CVE-2023-52870 Référence CVE CVE-2023-52871 https://www.cve.org/CVERecord?id=CVE-2023-52871 Référence CVE CVE-2023-52872 https://www.cve.org/CVERecord?id=CVE-2023-52872 Référence CVE CVE-2023-52873 https://www.cve.org/CVERecord?id=CVE-2023-52873 Référence CVE CVE-2023-52874 https://www.cve.org/CVERecord?id=CVE-2023-52874 Référence CVE CVE-2023-52875 https://www.cve.org/CVERecord?id=CVE-2023-52875 Référence CVE CVE-2023-52876 https://www.cve.org/CVERecord?id=CVE-2023-52876 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52880 https://www.cve.org/CVERecord?id=CVE-2023-52880 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-52882 https://www.cve.org/CVERecord?id=CVE-2023-52882 Référence CVE CVE-2023-52883 https://www.cve.org/CVERecord?id=CVE-2023-52883 Référence CVE CVE-2023-52884 https://www.cve.org/CVERecord?id=CVE-2023-52884 Référence CVE CVE-2023-52885 https://www.cve.org/CVERecord?id=CVE-2023-52885 Référence CVE CVE-2023-52886 https://www.cve.org/CVERecord?id=CVE-2023-52886 Référence CVE CVE-2024-25741 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52870 Référence CVE CVE-2023-52871 https://www.cve.org/CVERecord?id=CVE-2023-52871 Référence CVE CVE-2023-52872 https://www.cve.org/CVERecord?id=CVE-2023-52872 Référence CVE CVE-2023-52873 https://www.cve.org/CVERecord?id=CVE-2023-52873 Référence CVE CVE-2023-52874 https://www.cve.org/CVERecord?id=CVE-2023-52874 Référence CVE CVE-2023-52875 https://www.cve.org/CVERecord?id=CVE-2023-52875 Référence CVE CVE-2023-52876 https://www.cve.org/CVERecord?id=CVE-2023-52876 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52879 https://www.cve.org/CVERecord?id=CVE-2023-52879 Référence CVE CVE-2023-52880 https://www.cve.org/CVERecord?id=CVE-2023-52880 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-52883 https://www.cve.org/CVERecord?id=CVE-2023-52883 Référence CVE CVE-2023-52884 https://www.cve.org/CVERecord?id=CVE-2023-52884 Référence CVE CVE-2024-0090 https://www.cve.org/CVERecord?id=CVE-2024-0090 Référence CVE CVE-2024-0091 https://www.cve.org/CVERecord?id=CVE-2024-0091 Référence CVE CVE-2024-0092 https://www.cve.org/CVERecord?id=CVE-2024-0092 Référence CVE CVE-2024-26482 https://www.cve.org/CVERecord?id=CVE-20

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
e6807c873d8791ae5a5186ad05ec66cab926539a < 961c4511c7578d6b8f39118be919016ec3db1c1e; 407bf1c140f0757706c0b28604bcc90837d45ce2 < a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f; fa6d449e4d024d8c17f4288e0567d28ace69415c < cbc7c29dff0fa18162f2a3889d82eeefd67305e0; a46bf337a20f9edd3c8041b025639842280d0575 < 2fa74d29fc1899c237d51bf9a6e132ea5c488976; 9beec04370132a7a6cd1aa9897f6fffc6262ff28 < 2c9de867ca285c397cd71af703763fe416265706; f5ca233e2e66dc1c249bf07eefa37e34a6c9346a < 9034c87d61be8cff989017740a91701ac8195a1d; f5ca233e2e66dc1c249bf07eefa37e34a6c9346a < bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4; 5.4.258 < 5.4.262
Fixed
< 6.6; 5.4.262 ≤ 5.4.*; 5.10.202 ≤ 5.10.*; 5.15.140 ≤ 5.15.*; 6.1.64 ≤ 6.1.*; 6.5.13 ≤ 6.5.*; 6.6.1 ≤ 6.6.*; 6.7 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 May 2024 · Last source change 5 Aug 2026, 09:11 UTC · CWE-476 · NULL 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-2023-59592
Product sourceCNA
Remediation sourceCVE/CNA references
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 →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-2023-59592↗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-2023-52879 · cve.blacktree.nl