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

clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 26 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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: As exposure requiresRemediation target: Within 365 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 26 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.

25 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 21 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.41-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.147-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 6 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-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical 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.

3 current
CVE-2025-38499 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns
926 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-64k-debug-debuginfo-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debug-devel-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debug-devel-matched-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debuginfo-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-devel-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-devel-matched-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.50.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.50.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.50.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-devel-0:6.12.0-55.50.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-devel-0:6.12.0-55.50.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
Summary
A vulnerability was found in clone_private_mount in fs/namespace.c in filesystem subsystem in the Linux Kernel.This flaw could allow a local attacker to crash the system or leak kernel internal information.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
CVE-2025-38499 · CSAF 2.0 · revision 75 · interimSUSE Product Security TeamCVE-2025-38499
248 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above.
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-24155

No EUVD known-exploited evidence

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 26 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: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above.

What

In the Linux kernel, the following vulnerability has been resolved: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above.

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: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above.

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:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1757Linux Kernel: Schwachstelle ermöglicht Umgehen von Sicherheitsmechanismen

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um Sicherheitsmechanismen zu umgehen.

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

d?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38001 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38083 https://www.cve.org/CVERecord?id=CVE-2025-38083 Référence CVE CVE-2025-38180 https://www.cve.org/CVERecord?id=CVE-2025-38180 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38352 https://www.cve.org/CVERecord?id=CVE-2025-38352 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38546 https://www.cve.org/CVERecord?id=CVE-2025-38546 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38608 https://www.cve.org/CVERecord?id=CVE-2025-38608 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38492 https://www.cve.org/CVERecord?id=CVE-2025-38492 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38505 https://www.cve.org/CVERecord?id=CVE-2025-38505 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38508 https://www.cve.org/CVERecord?id=CVE-2025-38508 Référence CVE CVE-2025-38509 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53322 Référence CVE CVE-2023-53354 https://www.cve.org/CVERecord?id=CVE-2023-53354 Référence CVE CVE-2023-53365 https://www.cve.org/CVERecord?id=CVE-2023-53365 Référence CVE CVE-2023-53373 https://www.cve.org/CVERecord?id=CVE-2023-53373 Référence CVE CVE-2023-53393 https://www.cve.org/CVERecord?id=CVE-2023-53393 Référence CVE CVE-2023-53401 https://www.cve.org/CVERecord?id=CVE-2023-53401 Référence CVE CVE-2023-53513 https://www.cve.org/CVERecord?id=CVE-2023-53513 Référence CVE CVE-2023-53680 https://www.cve.org/CVERecord?id=CVE-2023-53680 Référence CVE CVE-2024-46679 https://www.cve.org/CVERecord?id=CVE-2024-46679 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-39697 https://www.cve.org/CVERecord?id=CVE-2025-39697 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38508 https://www.cve.org/CVERecord?id=CVE-2025-38508 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38492 https://www.cve.org/CVERecord?id=CVE-2025-38492 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38505 https://www.cve.org/CVERecord?id=CVE-2025-38505 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38508 https://www.cve.org/CVERecord?id=CVE-2025-38508 Référence CVE CVE-2025-38509 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38177 Référence CVE CVE-2025-38181 https://www.cve.org/CVERecord?id=CVE-2025-38181 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38552 https://www.cve.org/CVERecord?id=CVE-2025-38552 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=CVE-2025-38617 Référence CVE CVE-2025-38618 https://www.cve.org/CVERecord?id=CVE-2025-38618 Référence CVE CVE-2025-38644 https://www.cve.org/CVERecord?id=CVE-2025-38644 Référence CVE CVE-2025-38653 https://www.cve.org/CVERecord?id=CVE-2025-38653 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un attaquant de provoquer un contournement de la politique de sécurité, un déni de service et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38468 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 https://www.cve.org/CVERecord?id=CVE-2025-38514 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=CVE-2025-38516 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38445 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38515 https://www.cve.org/CVERecord?id=CVE-2025-38515 Référence CVE CVE-2025-38516 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Gestion détaillée du document le 14 août 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-024235Debian等の複数ベンダの製品における不特定の脆弱性

Linuxカーネルにおいて、clone_private_mnt() 関数には管理者権限の確認漏れによる脆弱性が存在していました。呼び出し元が正しいユーザー名前空間でCAP_SYS_ADMIN権限を持っていることを確認しないため、ロックされたマウントや適切な管理権限がない場合に、マウントの隠蔽や制限が正常に機能しない可能性があります。この脆弱性は将来のリリースで修正される予定です。

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
Linux: 427215d85e8d1476da1a86b8d67aceb485eb3631 < 36fecd740de2d542d2091d65d36554ee2bcf9c65, 427215d85e8d1476da1a86b8d67aceb485eb3631 < d717325b5ecf2a40daca85c61923e17f32306179, 427215d85e8d1476da1a86b8d67aceb485eb3631 < dc6a664089f10eab0fb36b6e4f705022210191d2, 427215d85e8d1476da1a86b8d67aceb485eb3631 < e77078e52fbf018ab986efb3c79065ab35025607, 427215d85e8d1476da1a86b8d67aceb485eb3631 < 38628ae06e2a37770cd794802a3f1310cf9846e3, 427215d85e8d1476da1a86b8d67aceb485eb3631 < c28f922c9dcee0e4876a2c095939d77fe7e15116, c6e8810d25295acb40a7b69ed3962ff181919571, e3eee87c846dc47f6d8eb6d85e7271f24122a279, 517b875dfbf58f0c6c9e32dc90f5cf42d71a42ce, 963d85d630dabe75a3cfde44a006fec3304d07b8, 812f39ed5b0b7f34868736de3055c92c7c4cf459, 6a002d48a66076524f67098132538bef17e8445e, 41812f4b84484530057513478c6770590347dc30, 4.4.281 < 4.5, 4.9.280 < 4.10, 4.14.244 < 4.15, 4.19.204 < 4.20, 5.4.141 < 5.5, 5.10.59 < 5.11, 5.13.11 < 5.14, 5.14
Fixed
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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 11 Aug 2025 · Last source change 5 Aug 2026, 12:02 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-2025-24155
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-24155↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-38499 · cve.blacktree.nl