BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-56719High confidence

net: stmmac: fix TSO DMA API usage causing oops

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

10.0CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.50% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

7 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
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: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/
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: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/
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.

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2024-53367

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

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
10.0 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

What

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → vulnerable operation → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of service
A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-53367Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

Official EUVD record ↗
BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-3762Linux 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 und um nicht näher beschriebene Effekte zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250101Security Bulletin 01 Jan 2025

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

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

d?id=CVE-2024-41079 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=CVE-2024-46715 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2025-10263 https://www.cve.org/CVERecord?id=CVE-2025-10263 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41079 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=CVE-2024-46715 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2025-37786 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41079 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=CVE-2024-46715 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-37786 https://www.cve.org/CVERecord?id=CVE-2025-37786 Référence CVE CVE-2025-38006 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-2024-41079 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=CVE-2024-46715 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2025-21709 https://www.cve.org/CVERecord?id=CVE-2025-21709 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-23141 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-2024-41079 Référence CVE CVE-2024-46715 https://www.cve.org/CVERecord?id=CVE-2024-46715 Référence CVE CVE-2024-46770 https://www.cve.org/CVERecord?id=CVE-2024-46770 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-50012 https://www.cve.org/CVERecord?id=CVE-2024-50012 Référence CVE CVE-2024-53221 https://www.cve.org/CVERecord?id=CVE-2024-53221 Référence CVE CVE-2024-56557 https://www.cve.org/CVERecord?id=CVE-2024-56557 Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2025-21709 https://www.cve.org/CVERecord?id=CVE-2025-21709 Référence CVE CVE-2025-21712 https://www.cve.org/CVERecord?id=CVE-2025-21712 Référence CVE CVE-2025-21739 https://www.cve.org/CVERecord?id=CVE-2025-21739 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-22107 https://www.cve.org/CVERecord?id=CVE-2025-22107 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=

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

Élévation de privilèges Systèmes affectés Desigo CC toutes versions Desigo CC toutes versions pour la vulnérabilité CVE-2025-15467 Desigo CC versions antérieures à 9.0.1 SIMATIC S7-1500 versions supérieures ou égales à 3.1.6 pour les vulnérabilités CVE-2021-41617, CVE-2023-28531, CVE-2023-51384, CVE-2023-52927, CVE-2024-26783, CVE-2024-27056, CVE-2024-28956, CVE-2024-36903, CVE-2024-36927, CVE-2024-42079, CVE-2024-46786, CVE-2024-47736, CVE-2024-47809, CVE-2024-49968, CVE-2024-49994, CVE-2024-49998, CVE-2024-50014, CVE-2024-50063, CVE-2024-50164, CVE-2024-50298, CVE-2024-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-21867, CVE-2025-21875, CVE-2025-21887, CVE-2025

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

n LTS msg00005 du 02 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00005.html Référence CVE CVE-2023-53228 https://www.cve.org/CVERecord?id=CVE-2023-53228 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50298 https://www.cve.org/CVERecord?id=CVE-2024-50298 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2025-21676 https://www.cve.org/CVERecord?id=CVE-2025-21676 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=CVE-2025-21682 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37980 https://www.cve.org/CVERecord?id=CVE-2025-37980 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=CVE-2025-38105 Référence CVE CVE-2025-38162 https://www.cve.org/CVERecord?id=CVE-2025-38162 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=

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

/2026/msg00154.html Référence CVE CVE-2023-53228 https://www.cve.org/CVERecord?id=CVE-2023-53228 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2024-14027 https://www.cve.org/CVERecord?id=CVE-2024-14027 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50298 https://www.cve.org/CVERecord?id=CVE-2024-50298 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2025-21676 https://www.cve.org/CVERecord?id=CVE-2025-21676 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=CVE-2025-21682 Référence CVE CVE-2025-21709 https://www.cve.org/CVERecord?id=CVE-2025-21709 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-22117 https://www.cve.org/CVERecord?id=CVE-2025-22117 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37980 https://www.cve.org/CVERecord?id=CVE-2025-37980 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56674 Référence CVE CVE-2024-56677 https://www.cve.org/CVERecord?id=CVE-2024-56677 Référence CVE CVE-2024-56692 https://www.cve.org/CVERecord?id=CVE-2024-56692 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-56707 https://www.cve.org/CVERecord?id=CVE-2024-56707 Référence CVE CVE-2024-56709 https://www.cve.org/CVERecord?id=CVE-2024-56709 Référence CVE CVE-2024-56712 https://www.cve.org/CVERecord?id=CVE-2024-56712 Référence CVE CVE-2024-56717 https://www.cve.org/CVERecord?id=CVE-2024-56717 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56722 https://www.cve.org/CVERecord?id=CVE-2024-56722 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2024-56737 https://www.cve.org/CVERecord?id=CVE-2024-56737 Référence CVE CVE-2024-56738 https://www.cve.org/CVERecord?id=CVE-2024-56738 Référence CVE CVE-2024-56744 https://www.cve.org/CVERecord?id=CVE-2024-56744 Référence CVE CVE-2024-56757 https://www.cve.org/CVERecord?id=CVE-2024-56757 Référence CVE CVE-2024-56782 https://www.cve.org/CVERecord?id=CVE-2024-56782 Référence CVE CVE-2024-56788 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-2024-56674 Référence CVE CVE-2024-56677 https://www.cve.org/CVERecord?id=CVE-2024-56677 Référence CVE CVE-2024-56692 https://www.cve.org/CVERecord?id=CVE-2024-56692 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-56707 https://www.cve.org/CVERecord?id=CVE-2024-56707 Référence CVE CVE-2024-56709 https://www.cve.org/CVERecord?id=CVE-2024-56709 Référence CVE CVE-2024-56712 https://www.cve.org/CVERecord?id=CVE-2024-56712 Référence CVE CVE-2024-56717 https://www.cve.org/CVERecord?id=CVE-2024-56717 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56722 https://www.cve.org/CVERecord?id=CVE-2024-56722 Référence CVE CVE-2024-56727 https://www.cve.org/CVERecord?id=CVE-2024-56727 Référence CVE CVE-2024-56737 https://www.cve.org/CVERecord?id=CVE-2024-56737 Référence CVE CVE-2024-56738 https://www.cve.org/CVERecord?id=CVE-2024-56738 Référence CVE CVE-2024-56744 https://www.cve.org/CVERecord?id=CVE-2024-56744 Référence CVE CVE-2024-56757 https://www.cve.org/CVERecord?id=CVE-2024-56757 Référence CVE CVE-2024-56782 https://www.cve.org/CVERecord?id=CVE-2024-56782 Référence CVE CVE-2024-56788 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56558 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56702 https://www.cve.org/CVERecord?id=CVE-2024-56702 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-56705 https://www.cve.org/CVERecord?id=CVE-2024-56705 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56758 https://www.cve.org/CVERecord?id=CVE-2024-56758 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-56779 https://www.cve.org/CVERecord?id=CVE-2024-56779 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2024-57974 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-54458 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56558 https://www.cve.org/CVERecord?id=CVE-2024-56558 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56702 https://www.cve.org/CVERecord?id=CVE-2024-56702 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56758 https://www.cve.org/CVERecord?id=CVE-2024-56758 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57834 https://www.cve.org/CVERecord?id=CVE-2024-57834 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53680 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56702 https://www.cve.org/CVERecord?id=CVE-2024-56702 Référence CVE CVE-2024-56703 https://www.cve.org/CVERecord?id=CVE-2024-56703 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56758 https://www.cve.org/CVERecord?id=CVE-2024-56758 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57834 https://www.cve.org/CVERecord?id=CVE-2024-57834 Référence CVE CVE-2024-57900 https://www.cve.org/CVERecord?id=CVE-2024-57900 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2024-57973 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56710 Référence CVE CVE-2024-56711 https://www.cve.org/CVERecord?id=CVE-2024-56711 Référence CVE CVE-2024-56712 https://www.cve.org/CVERecord?id=CVE-2024-56712 Référence CVE CVE-2024-56713 https://www.cve.org/CVERecord?id=CVE-2024-56713 Référence CVE CVE-2024-56714 https://www.cve.org/CVERecord?id=CVE-2024-56714 Référence CVE CVE-2024-56715 https://www.cve.org/CVERecord?id=CVE-2024-56715 Référence CVE CVE-2024-56716 https://www.cve.org/CVERecord?id=CVE-2024-56716 Référence CVE CVE-2024-56717 https://www.cve.org/CVERecord?id=CVE-2024-56717 Référence CVE CVE-2024-56718 https://www.cve.org/CVERecord?id=CVE-2024-56718 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2024-56757 https://www.cve.org/CVERecord?id=CVE-2024-56757 Référence CVE CVE-2024-56758 https://www.cve.org/CVERecord?id=CVE-2024-56758 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-56760 https://www.cve.org/CVERecord?id=CVE-2024-56760 Référence CVE CVE-2024-56761 https://www.cve.org/CVERecord?id=CVE-2024-56761 Référence CVE CVE-2024-56763 https://www.cve.org/CVERecord?id=CVE-2024-56763 Référence CVE CVE-2024-56764 https://www.cve.org/CVERecord?id=CVE-2024-56764 Référence CVE CVE-2024-56765 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-016151Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.12, 5.15.209 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.68 ≤ 6.6.*, 6.12.7 ≤ 6.12.*, 6.13 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 29 Dec 2024 · Last source change 8 Sept 2026, 08:39 UTC · CWE not yet assigned

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-2024-53367
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    ece593fc9c00741b682869d3f3dc584d37b7c9df < 05968b6dd0ffc65d7386608b11a11fb4fdfc9f36; a3ff23f7c3f0e13f718900803e090fd3997d6bc9 < 6abcdc9a73274052a9e96a1926994ecf9aedad82; 07c9c26e37542486e34d767505e842f48f29c3f6 < db3667c9bbfbbf5de98e6c9542f7e03fb5243286; 66600fac7a984dea4ae095411f644770b2561ede < 9d5dd7ccea1b46a9a7c6b3c2b9e5ed8864e185e2; 66600fac7a984dea4ae095411f644770b2561ede < 4c49f38e20a57f8abaebdf95b369295b153d1f8e; 58d23d835eb498336716cca55b5714191a309286; 5.15.171 < 5.15.209; 6.1.116 < 6.1.167 · Fixed: < 6.12; 5.15.209 ≤ 5.15.*; 6.1.167 ≤ 6.1.*; 6.6.68 ≤ 6.6.*; 6.12.7 ≤ 6.12.*; 6.13 ≤ *
    After
    Linux: ece593fc9c00741b682869d3f3dc584d37b7c9df < 05968b6dd0ffc65d7386608b11a11fb4fdfc9f36, a3ff23f7c3f0e13f718900803e090fd3997d6bc9 < 6abcdc9a73274052a9e96a1926994ecf9aedad82, 07c9c26e37542486e34d767505e842f48f29c3f6 < db3667c9bbfbbf5de98e6c9542f7e03fb5243286, 66600fac7a984dea4ae095411f644770b2561ede < 9d5dd7ccea1b46a9a7c6b3c2b9e5ed8864e185e2, 66600fac7a984dea4ae095411f644770b2561ede < 4c49f38e20a57f8abaebdf95b369295b153d1f8e, 58d23d835eb498336716cca55b5714191a309286, 5.15.171 < 5.15.209, 6.1.116 < 6.1.167, 6.6.60 < 6.6.68, 6.11.7 < 6.12, 6.12 · Fixed: Linux: < 6.12, 5.15.209 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.68 ≤ 6.6.*, 6.12.7 ≤ 6.12.*, 6.13 ≤ *
    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-2024-53367↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-56719 · cve.blacktree.nl