BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-21853High confidence

bpf: avoid holding freeze_mutex during mmap operation

Linux · Linux

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

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 2026

Evidence used

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

Compensating controls

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

Verification

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

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 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

1 current
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/
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-2025-6392

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 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: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/

What

In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
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:L/AC:L/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.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.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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-6392Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: avoid holding freeze_mutex during mmap operation We use map->freeze_mutex to prevent races between map_freeze() and memory mapping BPF map contents with writable permissions. The way we naively do this means we'll hold freeze_mutex for entire duration of all the mm and VMA manipulations, which is completely unnecessary. This can potentially also lead to deadlocks, as reported by syzbot in [0]. So, instead, hold freeze_mutex only during writeability checks, bump (proactively) "write active" count for the map, unlock the mutex and proceed with mmap logic. And only if something went wrong during mmap logic, then undo that "write active" counter increment. [0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/

Official EUVD record ↗
BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0545Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen und um nicht näher beschriebene Auswirkungen zu verursachen.

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

24-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-21913, CVE-2025-21919, CVE-2025-21925, CVE-2025-21926, CVE-2025-21938, CVE-2025-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025

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

d?id=CVE-2025-21832 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21832 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21575 Référence CVE CVE-2025-21577 https://www.cve.org/CVERecord?id=CVE-2025-21577 Référence CVE CVE-2025-21579 https://www.cve.org/CVERecord?id=CVE-2025-21579 Référence CVE CVE-2025-21580 https://www.cve.org/CVERecord?id=CVE-2025-21580 Référence CVE CVE-2025-21581 https://www.cve.org/CVERecord?id=CVE-2025-21581 Référence CVE CVE-2025-21584 https://www.cve.org/CVERecord?id=CVE-2025-21584 Référence CVE CVE-2025-21585 https://www.cve.org/CVERecord?id=CVE-2025-21585 Référence CVE CVE-2025-21588 https://www.cve.org/CVERecord?id=CVE-2025-21588 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21956 https://www.cve.org/CVERecord?id=CVE-2025-21956 Référence CVE CVE-2025-21957 https://www.cve.org/CVERecord?id=CVE-2025-21957 Référence CVE CVE-2025-21959 https://www.cve.org/CVERecord?id=CVE-2025-21959 Référence CVE CVE-2025-21962 https://www.cve.org/CVERecord?id=CVE-2025-21962 Référence CVE CVE-2025-21963 https://www.cve.org/CVERecord?id=CVE-2025-21963 Référence CVE CVE-2025-21964 https://www.cve.org/CVERecord?id=CVE-2025-21964 Référence CVE CVE-2025-21968 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21823 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21823 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53051 Référence CVE CVE-2024-53128 https://www.cve.org/CVERecord?id=CVE-2024-53128 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-54458 https://www.cve.org/CVERecord?id=CVE-2024-54458 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=CVE-2024-56662 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-22027 https://www.cve.org/CVERecord?id=CVE-2025-22027 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=CVE-2025-23140 Référence CVE CVE-2025-23142 https://www.cve.org/CVERecord?id=CVE-2025-23142 Référence CVE CVE-2025-23144 https://www.cve.org/CVERecord?id=CVE-2025-23144 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-23146 https://www.cve.org/CVERecord?id=CVE-2025-23146 Référence CVE CVE-2025-23147 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50272 Référence CVE CVE-2024-50280 https://www.cve.org/CVERecord?id=CVE-2024-50280 Référence CVE CVE-2024-53051 https://www.cve.org/CVERecord?id=CVE-2024-53051 Référence CVE CVE-2024-53128 https://www.cve.org/CVERecord?id=CVE-2024-53128 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-54458 https://www.cve.org/CVERecord?id=CVE-2024-54458 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=CVE-2024-56662 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-22027 https://www.cve.org/CVERecord?id=CVE-2025-22027 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=CVE-2025-23140 Référence CVE CVE-2025-23142 https://www.cve.org/CVERecord?id=CVE-2025-23142 Référence CVE CVE-2025-23144 https://www.cve.org/CVERecord?id=CVE-2025-23144 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-23146 https://www.cve.org/CVERecord?id=CVE-2025-23146 Référence CVE CVE-2025-23147 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21816 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21956 https://www.cve.org/CVERecord?id=CVE-2025-21956 Référence CVE CVE-2025-21957 https://www.cve.org/CVERecord?id=CVE-2025-21957 Référence CVE CVE-2025-21959 https://www.cve.org/CVERecord?id=CVE-2025-21959 Référence CVE CVE-2025-21962 https://www.cve.org/CVERecord?id=CVE-2025-21962 Référence CVE CVE-2025-21963 https://www.cve.org/CVERecord?id=CVE-2025-21963 Référence CVE CVE-2025-21964 https://www.cve.org/CVERecord?id=CVE-2025-21964 Référence CVE CVE-2025-21968 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-2025-21833 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21837 https://www.cve.org/CVERecord?id=CVE-2025-21837 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21850 https://www.cve.org/CVERecord?id=CVE-2025-21850 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 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-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21850 https://www.cve.org/CVERecord?id=CVE-2025-21850 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21696 Référence CVE CVE-2025-21707 https://www.cve.org/CVERecord?id=CVE-2025-21707 Référence CVE CVE-2025-21758 https://www.cve.org/CVERecord?id=CVE-2025-21758 Référence CVE CVE-2025-21768 https://www.cve.org/CVERecord?id=CVE-2025-21768 Référence CVE CVE-2025-21792 https://www.cve.org/CVERecord?id=CVE-2025-21792 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21904 https://www.cve.org/CVERecord?id=CVE-2025-21904 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21962 https://www.cve.org/CVERecord?id=CVE-2025-21962 Référence CVE CVE-2025-21963 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21758 Référence CVE CVE-2025-21768 https://www.cve.org/CVERecord?id=CVE-2025-21768 Référence CVE CVE-2025-21792 https://www.cve.org/CVERecord?id=CVE-2025-21792 Référence CVE CVE-2025-21806 https://www.cve.org/CVERecord?id=CVE-2025-21806 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21811 Référence CVE CVE-2025-21814 https://www.cve.org/CVERecord?id=CVE-2025-21814 Référence CVE CVE-2025-21823 https://www.cve.org/CVERecord?id=CVE-2025-21823 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=CVE-2025-21846 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21791 Référence CVE CVE-2025-21792 https://www.cve.org/CVERecord?id=CVE-2025-21792 Référence CVE CVE-2025-21806 https://www.cve.org/CVERecord?id=CVE-2025-21806 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53034 Référence CVE CVE-2024-36908 https://www.cve.org/CVERecord?id=CVE-2024-36908 Référence CVE CVE-2024-46733 https://www.cve.org/CVERecord?id=CVE-2024-46733 Référence CVE CVE-2024-46742 https://www.cve.org/CVERecord?id=CVE-2024-46742 Référence CVE CVE-2024-46753 https://www.cve.org/CVERecord?id=CVE-2024-46753 Référence CVE CVE-2024-46774 https://www.cve.org/CVERecord?id=CVE-2024-46774 Référence CVE CVE-2024-46816 https://www.cve.org/CVERecord?id=CVE-2024-46816 Référence CVE CVE-2024-46823 https://www.cve.org/CVERecord?id=CVE-2024-46823 Référence CVE CVE-2024-50063 https://www.cve.org/CVERecord?id=CVE-2024-50063 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-22025 https://www.cve.org/CVERecord?id=CVE-2025-22025 Référence CVE CVE-2025-22027 https://www.cve.org/CVERecord?id=CVE-2025-22027 Référence CVE CVE-2025-22033 https://www.cve.org/CVERecord?id=CVE-2025-22033 Référence CVE CVE-2025-22035 https://www.cve.org/CVERecord?id=CVE-2025-22035 Référence CVE CVE-2025-22038 https://www.cve.org/CVERecord?id=CVE-2025-22038 Référence CVE CVE-2025-22040 https://www.cve.org/CVERecord?id=CVE-2025-22040 Référence CVE CVE-2025-22041 https://www.cve.org/CVERecord?id=CVE-2025-22041 Référence CVE CVE-2025-22042 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-002386Linux の 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: < 5.5, 5.10.237 ≤ 5.10.*, 5.15.181 ≤ 5.15.*, 6.1.135 ≤ 6.1.*, 6.6.80 ≤ 6.6.*, 6.12.17 ≤ 6.12.*, 6.13.5 ≤ 6.13.*, 6.14 ≤ *
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 12 Mar 2025 · Last source change 8 Sept 2026, 08:40 UTC · CWE not yet assigned

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-2025-6392
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
    fc9702273e2edb90400a34b3be76f7b08fa3344b < 2ce31c97c219b4fe797749f950274f246eb88c49; fc9702273e2edb90400a34b3be76f7b08fa3344b < 0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f; fc9702273e2edb90400a34b3be76f7b08fa3344b < 4759acbd44d24a69b7b14848012ec4201d6c5501; fc9702273e2edb90400a34b3be76f7b08fa3344b < 29cfda62ab4d92ab94123813db49ab76c1e61b29; fc9702273e2edb90400a34b3be76f7b08fa3344b < d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4; fc9702273e2edb90400a34b3be76f7b08fa3344b < 271e49f8a58edba65bc2b1250a0abaa98c4bfdbe; fc9702273e2edb90400a34b3be76f7b08fa3344b < bc27c52eea189e8f7492d40739b7746d67b65beb; 5.5 · Fixed: < 5.5; 5.10.237 ≤ 5.10.*; 5.15.181 ≤ 5.15.*; 6.1.135 ≤ 6.1.*; 6.6.80 ≤ 6.6.*; 6.12.17 ≤ 6.12.*; 6.13.5 ≤ 6.13.*; 6.14 ≤ *
    After
    Linux: fc9702273e2edb90400a34b3be76f7b08fa3344b < 2ce31c97c219b4fe797749f950274f246eb88c49, fc9702273e2edb90400a34b3be76f7b08fa3344b < 0d90d9e154144a3a80e9fc0eb9b21b7fc990f68f, fc9702273e2edb90400a34b3be76f7b08fa3344b < 4759acbd44d24a69b7b14848012ec4201d6c5501, fc9702273e2edb90400a34b3be76f7b08fa3344b < 29cfda62ab4d92ab94123813db49ab76c1e61b29, fc9702273e2edb90400a34b3be76f7b08fa3344b < d95607a5f2f9bb08194c9deaf4a5f3e8ba59a9d4, fc9702273e2edb90400a34b3be76f7b08fa3344b < 271e49f8a58edba65bc2b1250a0abaa98c4bfdbe, fc9702273e2edb90400a34b3be76f7b08fa3344b < bc27c52eea189e8f7492d40739b7746d67b65beb, 5.5 · Fixed: Linux: < 5.5, 5.10.237 ≤ 5.10.*, 5.15.181 ≤ 5.15.*, 6.1.135 ≤ 6.1.*, 6.6.80 ≤ 6.6.*, 6.12.17 ≤ 6.12.*, 6.13.5 ≤ 6.13.*, 6.14 ≤ *
    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-2025-6392↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗Patch or update reference↗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-2025-21853 · cve.blacktree.nl