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

PCI/PM: Drain runtime-idle callbacks before driver removal

Linux · Linux

4.7MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

11 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-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-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-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-oem-6.8Affected, 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-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
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-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < 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)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
In the Linux kernel, the following vulnerability has been resolved: PCI/PM: Drain runtime-idle callbacks before driver removal.
Remediation
Update to V3.1.5 or later version
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-2024-35801

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: PCI/PM: Drain runtime-idle callbacks before driver removal A race condition between the .runtime_idle() callback and the .remove() callback in the rtsx_pcr PCI driver leads to a kernel crash due to an unhandled page fault [1]. The problem is that rtsx_pci_runtime_idle() is not expected to be running after pm_runtime_get_sync() has been called, but the latter doesn't really guarantee that. It only guarantees that the suspend and resume callbacks will not be running when it returns. However, if a .runtime_idle() callback is already running when pm_runtime_get_sync() is called, the latter will notice that the runtime PM status of the device is RPM_ACTIVE and it will return right away without waiting for the former to complete. In fact, it cannot wait for .runtime_idle() to complete because it may be called from that callback (it arguably does not make much sense to do that, but it is not strictly prohibited). Thus in general, whoever is providing a .runtime_idle() callback needs to protect it from running in parallel with whatever code runs after pm_runtime_get_sync(). [Note that .runtime_idle() will not start after pm_runtime_get_sync() has returned, but it may continue running then if it has started earlier.] One way to address that race condition is to call pm_runtime_barrier() after pm_runtime_get_sync() (not before it, because a nonzero value of the runtime PM usage counter is necessary to prevent runtime PM callbacks from being invoked) to wait for the .runtime_idle() callback to complete should it be running at that point. A suitable place for doing that is in pci_device_remove() which calls pm_runtime_get_sync() before removing the driver, so it may as well call pm_runtime_barrier() subsequently, which will prevent the race in question from occurring, not just in the rtsx_pcr driver, but in any PCI drivers providing .runtime_idle() callbacks.

What

In the Linux kernel, the following vulnerability has been resolved: PCI/PM: Drain runtime-idle callbacks before driver removal A race condition between the .runtime_idle() callback and the .remove() callback in the rtsx_pcr PCI driver leads to a kernel crash due to an unhandled page fault [1]. The problem is that rtsx_pci_runtime_idle() is not expected to be running after pm_runtime_get_sync() has been called, but the latter doesn't really guarantee that. It only guarantees that the suspend and resume callbacks will not be running when it returns. However, if a .runtime_idle() callback is already running when pm_runtime_get_sync() is called, the latter will notice that the runtime PM status of the device is RPM_ACTIVE and it will return right away without waiting for the former to complete. In fact, it cannot wait for .runtime_idle() to complete because it may be called from that callback (it arguably does not make much sense to do that, but it is not strictly prohibited). Thus in general, whoever is providing a .runtime_idle() callback needs to protect it from running in parallel with whatever code runs after pm_runtime_get_sync(). [Note that .runtime_idle() will not start after pm_runtime_get_sync() has returned, but it may continue running then if it has started earlier.] One way to address that race condition is to call pm_runtime_barrier() after pm_runtime_get_sync() (not before it, because a nonzero value of the runtime PM usage counter is necessary to prevent runtime PM callbacks from being invoked) to wait for the .runtime_idle() callback to complete should it be running at that point. A suitable place for doing that is in pci_device_remove() which calls pm_runtime_get_sync() before removing the driver, so it may as well call pm_runtime_barrier() subsequently, which will prevent the race in question from occurring, not just in the rtsx_pcr driver, but in any PCI drivers providing .runtime_idle() callbacks.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: PCI/PM: Drain runtime-idle callbacks before driver removal A race condition between the .runtime_idle() callback and the .remove() callback in the rtsx_pcr PCI driver leads to a kernel crash due to an unhandled page fault [1]. The problem is that rtsx_pci_runtime_idle() is not expected to be running after pm_runtime_get_sync() has been called, but the latter doesn't really guarantee that. It only guarantees that the suspend and resume callbacks will not be running when it returns. However, if a .runtime_idle() callback is already running when pm_runtime_get_sync() is called, the latter will notice that the runtime PM status of the device is RPM_ACTIVE and it will return right away without waiting for the former to complete. In fact, it cannot wait for .runtime_idle() to complete because it may be called from that callback (it arguably does not make much sense to do that, but it is not strictly prohibited). Thus in general, whoever is providing a .runtime_idle() callback needs to protect it from running in parallel with whatever code runs after pm_runtime_get_sync(). [Note that .runtime_idle() will not start after pm_runtime_get_sync() has returned, but it may continue running then if it has started earlier.] One way to address that race condition is to call pm_runtime_barrier() after pm_runtime_get_sync() (not before it, because a nonzero value of the runtime PM usage counter is necessary to prevent runtime PM callbacks from being invoked) to wait for the .runtime_idle() callback to complete should it be running at that point. A suitable place for doing that is in pci_device_remove() which calls pm_runtime_get_sync() before removing the driver, so it may as well call pm_runtime_barrier() subsequently, which will prevent the race in question from occurring, not just in the rtsx_pcr driver, but in any PCI drivers providing .runtime_idle() callbacks.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/PR:L/UI:N/S:U/C:N/I:N/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-362
A

Official authority intelligence

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

BSI · German · WID-SEC-W-2025-0225Dell PowerProtect Data Domain: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell PowerProtect Data Domain ausnutzen, um erhöhte Rechte zu erlangen, einen Denial-of-Service-Zustand herbeizuführen und einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory
BSI · German · WID-SEC-W-2024-1188Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

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

d?id=CVE-2024-26929 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-27011 https://www.cve.org/CVERecord?id=CVE-2024-27011 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29025 https://www.cve.org/CVERecord?id=CVE-2024-29025 Référence CVE CVE-2024-34155 https://www.cve.org/CVERecord?id=CVE-2024-34155 Référence CVE CVE-2024-34156 https://www.cve.org/CVERecord?id=CVE-2024-34156 Référence CVE CVE-2024-34158 https://www.cve.org/CVERecord?id=CVE-2024-34158 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35944 https://www.cve.org/CVERecord?id=CVE-2024-35944 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-37890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26947 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26991 https://www.cve.org/CVERecord?id=CVE-2024-26991 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-27013 https://www.cve.org/CVERecord?id=CVE-2024-27013 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-27020 https://www.cve.org/CVERecord?id=CVE-2024-27020 Référence CVE CVE-2024-27022 https://www.cve.org/CVERecord?id=CVE-2024-27022 Référence CVE CVE-2024-27042 https://www.cve.org/CVERecord?id=CVE-2024-27042 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35877 https://www.cve.org/CVERecord?id=CVE-2024-35877 Référence CVE CVE-2024-35884 https://www.cve.org/CVERecord?id=CVE-2024-35884 Référence CVE CVE-2024-35895 https://www.cve.org/CVERecord?id=CVE-2024-35895 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=CVE-2024-35898 Référence CVE CVE-2024-35944 https://www.cve.org/CVERecord?id=CVE-2024-35944 Référence CVE CVE-2024-35989 https://www.cve.org/CVERecord?id=CVE-2024-35989 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35247 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35799 Référence CVE CVE-2024-35800 https://www.cve.org/CVERecord?id=CVE-2024-35800 Référence CVE CVE-2024-35801 https://www.cve.org/CVERecord?id=CVE-2024-35801 Référence CVE CVE-2024-35803 https://www.cve.org/CVERecord?id=CVE-2024-35803 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35808 https://www.cve.org/CVERecord?id=CVE-2024-35808 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35810 https://www.cve.org/CVERecord?id=CVE-2024-35810 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35812 https://www.cve.org/CVERecord?id=CVE-2024-35812 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=CVE-2024-35814 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27437 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27437 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27437 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35798 Référence CVE CVE-2024-35799 https://www.cve.org/CVERecord?id=CVE-2024-35799 Référence CVE CVE-2024-35800 https://www.cve.org/CVERecord?id=CVE-2024-35800 Référence CVE CVE-2024-35801 https://www.cve.org/CVERecord?id=CVE-2024-35801 Référence CVE CVE-2024-35803 https://www.cve.org/CVERecord?id=CVE-2024-35803 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35808 https://www.cve.org/CVERecord?id=CVE-2024-35808 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35810 https://www.cve.org/CVERecord?id=CVE-2024-35810 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=CVE-2024-35814 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35795 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35799 https://www.cve.org/CVERecord?id=CVE-2024-35799 Référence CVE CVE-2024-35800 https://www.cve.org/CVERecord?id=CVE-2024-35800 Référence CVE CVE-2024-35801 https://www.cve.org/CVERecord?id=CVE-2024-35801 Référence CVE CVE-2024-35803 https://www.cve.org/CVERecord?id=CVE-2024-35803 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35808 https://www.cve.org/CVERecord?id=CVE-2024-35808 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35810 https://www.cve.org/CVERecord?id=CVE-2024-35810 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35812 https://www.cve.org/CVERecord?id=CVE-2024-35812 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35814 https://www.cve.org/CVERecord?id=CVE-2024-35814 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-31076 Référence CVE CVE-2024-33621 https://www.cve.org/CVERecord?id=CVE-2024-33621 Référence CVE CVE-2024-35785 https://www.cve.org/CVERecord?id=CVE-2024-35785 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35805 https://www.cve.org/CVERecord?id=CVE-2024-35805 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35807 https://www.cve.org/CVERecord?id=CVE-2024-35807 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35819 https://www.cve.org/CVERecord?id=CVE-2024-35819 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-35825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27435 Référence CVE CVE-2024-27436 https://www.cve.org/CVERecord?id=CVE-2024-27436 Référence CVE CVE-2024-35789 https://www.cve.org/CVERecord?id=CVE-2024-35789 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35796 https://www.cve.org/CVERecord?id=CVE-2024-35796 Référence CVE CVE-2024-35799 https://www.cve.org/CVERecord?id=CVE-2024-35799 Référence CVE CVE-2024-35801 https://www.cve.org/CVERecord?id=CVE-2024-35801 Référence CVE CVE-2024-35804 https://www.cve.org/CVERecord?id=CVE-2024-35804 Référence CVE CVE-2024-35806 https://www.cve.org/CVERecord?id=CVE-2024-35806 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35812 https://www.cve.org/CVERecord?id=CVE-2024-35812 Référence CVE CVE-2024-35813 https://www.cve.org/CVERecord?id=CVE-2024-35813 Référence CVE CVE-2024-35815 https://www.cve.org/CVERecord?id=CVE-2024-35815 Référence CVE CVE-2024-35817 https://www.cve.org/CVERecord?id=CVE-2024-35817 Référence CVE CVE-2024-35821 https://www.cve.org/CVERecord?id=CVE-2024-35821 Référence CVE CVE-2024-35822 https://www.cve.org/CVERecord?id=CVE-2024-35822 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=

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
SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0); SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0); SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0); SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0); SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Fixed
< 2.6.36; 4.19.312 ≤ 4.19.*; 5.4.274 ≤ 5.4.*; 5.10.215 ≤ 5.10.*; 5.15.154 ≤ 5.15.*; 6.1.84 ≤ 6.1.*; 6.6.24 ≤ 6.6.*; 6.7.12 ≤ 6.7.*
Action
Update to V3.1.5 or later version
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 May 2024 · Last source change 11 May 2026, 20:11 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-2024-35801
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD enriched

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-2024-35801↗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-2024-35809 · cve.blacktree.nl