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

NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN

Linux · Linux

7.5HighCVSS 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:High, unchanged from published severity.unchanged

Evidence used

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

Compensating controls

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

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 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.37-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.12.37-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.37-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.

2 current
CVE-2025-38393 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2025-38393
158 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN We found a few different systems hung up in writeback waiting on the same page lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in pnfs_update_layout(), however the pnfs_layout_hdr's plh_outstanding count was zero. It seems most likely that this is another race between the waiter and waker similar to commit ed0172af5d6f ("SUNRPC: Fix a race to wake a sync task"). Fix it up by applying the advised barrier.
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: NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN We found a few different systems hung up in writeback waiting on the same page lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in pnfs_update_layout(), however the pnfs_layout_hdr's plh_outstanding count was zero. It seems most likely that this is another race between the waiter and waker similar to commit ed0172af5d6f ("SUNRPC: Fix a race to wake a sync task"). Fix it up by applying the advised barrier.
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-22610

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: NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN We found a few different systems hung up in writeback waiting on the same page lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in pnfs_update_layout(), however the pnfs_layout_hdr's plh_outstanding count was zero. It seems most likely that this is another race between the waiter and waker similar to commit ed0172af5d6f ("SUNRPC: Fix a race to wake a sync task"). Fix it up by applying the advised barrier.

What

In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN We found a few different systems hung up in writeback waiting on the same page lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in pnfs_update_layout(), however the pnfs_layout_hdr's plh_outstanding count was zero. It seems most likely that this is another race between the waiter and waker similar to commit ed0172af5d6f ("SUNRPC: Fix a race to wake a sync task"). Fix it up by applying the advised barrier.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN We found a few different systems hung up in writeback waiting on the same page lock, and one task waiting on the NFS_LAYOUT_DRAIN bit in pnfs_update_layout(), however the pnfs_layout_hdr's plh_outstanding count was zero. It seems most likely that this is another race between the waiter and waker similar to commit ed0172af5d6f ("SUNRPC: Fix a race to wake a sync task"). Fix it up by applying the advised barrier.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-362 ↗

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

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/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.

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

Official authority intelligence

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

BSI · German · WID-SEC-2025-1653Linux Kernel: Mehrere Schwachstellen

Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250730Security Bulletin 30 Jul 2025 [827KB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 30 Jul 2025 [827KB], published on 30 July 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 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-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 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-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 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-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 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-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 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-38383 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38397 https://www.cve.org/CVERecord?id=CVE-2025-38397 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38363 Référence CVE CVE-2025-38371 https://www.cve.org/CVERecord?id=CVE-2025-38371 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-38377 https://www.cve.org/CVERecord?id=CVE-2025-38377 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=CVE-2025-38406 Référence CVE CVE-2025-38410 https://www.cve.org/CVERecord?id=CVE-2025-38410 Référence CVE CVE-2025-38412 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38363 Référence CVE CVE-2025-38371 https://www.cve.org/CVERecord?id=CVE-2025-38371 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-38377 https://www.cve.org/CVERecord?id=CVE-2025-38377 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=CVE-2025-38406 Référence CVE CVE-2025-38410 https://www.cve.org/CVERecord?id=CVE-2025-38410 Référence CVE CVE-2025-38412 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38388 https://www.cve.org/CVERecord?id=CVE-2025-38388 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38390 https://www.cve.org/CVERecord?id=CVE-2025-38390 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38402 https://www.cve.org/CVERecord?id=CVE-2025-38402 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38405 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-38375 Référence CVE CVE-2025-38377 https://www.cve.org/CVERecord?id=CVE-2025-38377 Référence CVE CVE-2025-38382 https://www.cve.org/CVERecord?id=CVE-2025-38382 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38404 https://www.cve.org/CVERecord?id=CVE-2025-38404 Référence CVE CVE-2025-38406 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-38363 Référence CVE CVE-2025-38371 https://www.cve.org/CVERecord?id=CVE-2025-38371 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-38377 https://www.cve.org/CVERecord?id=CVE-2025-38377 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=CVE-2025-38406 Référence CVE CVE-2025-38410 https://www.cve.org/CVERecord?id=CVE-2025-38410 Référence CVE CVE-2025-38412 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-38363 Référence CVE CVE-2025-38371 https://www.cve.org/CVERecord?id=CVE-2025-38371 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-38377 https://www.cve.org/CVERecord?id=CVE-2025-38377 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=CVE-2025-38406 Référence CVE CVE-2025-38410 https://www.cve.org/CVERecord?id=CVE-2025-38410 Référence CVE CVE-2025-38412 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-38363 Référence CVE CVE-2025-38371 https://www.cve.org/CVERecord?id=CVE-2025-38371 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-38377 https://www.cve.org/CVERecord?id=CVE-2025-38377 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=CVE-2025-38406 Référence CVE CVE-2025-38410 https://www.cve.org/CVERecord?id=CVE-2025-38410 Référence CVE CVE-2025-38412 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38380 Référence CVE CVE-2025-38382 https://www.cve.org/CVERecord?id=CVE-2025-38382 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38404 https://www.cve.org/CVERecord?id=CVE-2025-38404 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38380 Référence CVE CVE-2025-38382 https://www.cve.org/CVERecord?id=CVE-2025-38382 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38404 https://www.cve.org/CVERecord?id=CVE-2025-38404 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38380 Référence CVE CVE-2025-38382 https://www.cve.org/CVERecord?id=CVE-2025-38382 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38392 https://www.cve.org/CVERecord?id=CVE-2025-38392 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38404 https://www.cve.org/CVERecord?id=CVE-2025-38404 Référence CVE CVE-2025-38406 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-38377 Référence CVE CVE-2025-38380 https://www.cve.org/CVERecord?id=CVE-2025-38380 Référence CVE CVE-2025-38382 https://www.cve.org/CVERecord?id=CVE-2025-38382 Référence CVE CVE-2025-38384 https://www.cve.org/CVERecord?id=CVE-2025-38384 Référence CVE CVE-2025-38385 https://www.cve.org/CVERecord?id=CVE-2025-38385 Référence CVE CVE-2025-38386 https://www.cve.org/CVERecord?id=CVE-2025-38386 Référence CVE CVE-2025-38387 https://www.cve.org/CVERecord?id=CVE-2025-38387 Référence CVE CVE-2025-38389 https://www.cve.org/CVERecord?id=CVE-2025-38389 Référence CVE CVE-2025-38391 https://www.cve.org/CVERecord?id=CVE-2025-38391 Référence CVE CVE-2025-38393 https://www.cve.org/CVERecord?id=CVE-2025-38393 Référence CVE CVE-2025-38395 https://www.cve.org/CVERecord?id=CVE-2025-38395 Référence CVE CVE-2025-38396 https://www.cve.org/CVERecord?id=CVE-2025-38396 Référence CVE CVE-2025-38399 https://www.cve.org/CVERecord?id=CVE-2025-38399 Référence CVE CVE-2025-38400 https://www.cve.org/CVERecord?id=CVE-2025-38400 Référence CVE CVE-2025-38401 https://www.cve.org/CVERecord?id=CVE-2025-38401 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38404 https://www.cve.org/CVERecord?id=CVE-2025-38404 Référence CVE CVE-2025-38406 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-023204Debian等の複数ベンダの製品における競合状態に関する脆弱性

LinuxカーネルのNFSv4/pNFSにおいて、NFS_LAYOUT_DRAINでのウェイク時の競合状態が修正されました。plh_outstandingのカウントがゼロであるにもかかわらず、pnfs_update_layout()内でNFS_LAYOUT_DRAINビットを待機するタスクが発生し、writebackがハングアップする可能性がありました。これはコミットed0172af5d6fで修正された競合状態と類似しており、適切なバリアを適用することで問題が解決しています。

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
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jul 2025 · Last source change 5 Aug 2026, 12:01 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-22610
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-38393 · cve.blacktree.nl