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

NFSD: NFSv4 file creation neglects setting ACL

Linux · Linux

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

8.0HighCVSS 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 209 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.
  • EPSS is 0.44% 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 209 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.69-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-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-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
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2025-68803 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: NFSD: NFSv4 file creation neglects setting ACL
184 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's NFSv4 server implementation. When an NFSv4 client creates a file and specifies an ACL with named principals, the server fails to apply the requested ACL. The nfsd_create_setattr() function checks only for iattr changes and security labels but not POSIX ACLs, causing the ACL to be silently dropped. The file ends up with a default ACL based on mode bits instead of the client-specified ACL, violating RFC 8881.
Remediation
Fix deferred
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-2026-2303

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.

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
8.0 · CVSS 3.1
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 209 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: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.

What

In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.

Why

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

How

An attacker operating through a network path may attempt exploitation 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: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.

Why

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

How

An attacker operating through a network path may attempt exploitation 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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
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:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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
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.
Network
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-2303Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: NFSD: NFSv4 file creation neglects setting ACL An NFSv4 client that sets an ACL with a named principal during file creation retrieves the ACL afterwards, and finds that it is only a default ACL (based on the mode bits) and not the ACL that was requested during file creation. This violates RFC 8881 section 6.4.1.3: "the ACL attribute is set as given". The issue occurs in nfsd_create_setattr(), which calls nfsd_attrs_valid() to determine whether to call nfsd_setattr(). However, nfsd_attrs_valid() checks only for iattr changes and security labels, but not POSIX ACLs. When only an ACL is present, the function returns false, nfsd_setattr() is skipped, and the POSIX ACL is never applied to the inode. Subsequently, when the client retrieves the ACL, the server finds no POSIX ACL on the inode and returns one generated from the file's mode bits rather than returning the originally-specified ACL.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0086Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260114Security Bulletin 14 Jan 2026

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

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

25-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025-71095, CVE-2025-71097, CVE-2025-71098, CVE-2025-71104, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71197, CVE-2025-71221, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2026-3497, CVE-2026-22977, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-22992, CVE-2026-22994, CVE-2026-

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

d?id=CVE-2025-40149 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-68214 https://www.cve.org/CVERecord?id=CVE-2025-68214 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2025-71183 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68810 https://www.cve.org/CVERecord?id=CVE-2025-68810 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38591 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71160 https://www.cve.org/CVERecord?id=CVE-2025-71160 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2025-71183 https://www.cve.org/CVERecord?id=CVE-2025-71183 Référence CVE CVE-2025-71184 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40149 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=CVE-2025-40164 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68340 https://www.cve.org/CVERecord?id=CVE-2025-68340 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71139 https://www.cve.org/CVERecord?id=CVE-2025-71139 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40149 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=CVE-2025-40164 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-68340 https://www.cve.org/CVERecord?id=CVE-2025-68340 Référence CVE CVE-2025-68351 https://www.cve.org/CVERecord?id=CVE-2025-68351 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-68365 https://www.cve.org/CVERecord?id=CVE-2025-68365 Référence CVE CVE-2025-68725 https://www.cve.org/CVERecord?id=CVE-2025-68725 Référence CVE CVE-2025-68749 https://www.cve.org/CVERecord?id=CVE-2025-68749 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68823 https://www.cve.org/CVERecord?id=CVE-2025-68823 Référence CVE CVE-2025-71088 https://www.cve.org/CVERecord?id=CVE-2025-71088 Référence CVE CVE-2025-71090 https://www.cve.org/CVERecord?id=CVE-2025-71090 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2025-71134 https://www.cve.org/CVERecord?id=CVE-2025-71134 Référence CVE CVE-2025-71139 https://www.cve.org/CVERecord?id=CVE-2025-71139 Référence CVE CVE-2025-71141 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68788 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68810 https://www.cve.org/CVERecord?id=CVE-2025-68810 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68805 https://www.cve.org/CVERecord?id=CVE-2025-68805 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68807 https://www.cve.org/CVERecord?id=CVE-2025-68807 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68810 https://www.cve.org/CVERecord?id=CVE-2025-68810 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68805 https://www.cve.org/CVERecord?id=CVE-2025-68805 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68807 https://www.cve.org/CVERecord?id=CVE-2025-68807 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68810 https://www.cve.org/CVERecord?id=CVE-2025-68810 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=CVE-2025-68817 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68783 Référence CVE CVE-2025-68785 https://www.cve.org/CVERecord?id=CVE-2025-68785 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68810 https://www.cve.org/CVERecord?id=CVE-2025-68810 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68785 Référence CVE CVE-2025-68787 https://www.cve.org/CVERecord?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68818 https://www.cve.org/CVERecord?id=CVE-2025-68818 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68789 Référence CVE CVE-2025-68792 https://www.cve.org/CVERecord?id=CVE-2025-68792 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68783 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68783 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68789 https://www.cve.org/CVERecord?id=CVE-2025-68789 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68819 https://www.cve.org/CVERecord?id=CVE-2025-68819 Référence CVE CVE-2025-68820 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68787 Référence CVE CVE-2025-68788 https://www.cve.org/CVERecord?id=CVE-2025-68788 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=CVE-2025-68814 Référence CVE CVE-2025-68815 https://www.cve.org/CVERecord?id=CVE-2025-68815 Référence CVE CVE-2025-68816 https://www.cve.org/CVERecord?id=CVE-2025-68816 Référence CVE CVE-2025-68817 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68794 Référence CVE CVE-2025-68795 https://www.cve.org/CVERecord?id=CVE-2025-68795 Référence CVE CVE-2025-68796 https://www.cve.org/CVERecord?id=CVE-2025-68796 Référence CVE CVE-2025-68797 https://www.cve.org/CVERecord?id=CVE-2025-68797 Référence CVE CVE-2025-68798 https://www.cve.org/CVERecord?id=CVE-2025-68798 Référence CVE CVE-2025-68799 https://www.cve.org/CVERecord?id=CVE-2025-68799 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-68801 https://www.cve.org/CVERecord?id=CVE-2025-68801 Référence CVE CVE-2025-68802 https://www.cve.org/CVERecord?id=CVE-2025-68802 Référence CVE CVE-2025-68803 https://www.cve.org/CVERecord?id=CVE-2025-68803 Référence CVE CVE-2025-68804 https://www.cve.org/CVERecord?id=CVE-2025-68804 Référence CVE CVE-2025-68806 https://www.cve.org/CVERecord?id=CVE-2025-68806 Référence CVE CVE-2025-68808 https://www.cve.org/CVERecord?id=CVE-2025-68808 Référence CVE CVE-2025-68809 https://www.cve.org/CVERecord?id=CVE-2025-68809 Référence CVE CVE-2025-68810 https://www.cve.org/CVERecord?id=CVE-2025-68810 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-68813 https://www.cve.org/CVERecord?id=CVE-2025-68813 Référence CVE CVE-2025-68814 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

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

Evidence and provenance

Published 13 Jan 2026 · Last source change 8 Sept 2026, 08:43 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-2026-2303
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceUnavailable
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2025-68803 to remediation: access.redhat.com/CVE-2025-68803.
    Before
    remediation: access.redhat.com/CVE-2025-68803
    After
    remediation: access.redhat.com/CVE-2025-68803
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    c5409ce523af40d5c3019717bc5b4f72038d48be < c182e1e0b7640f6bcc0c5ca8d473f7c57199ea3d; d52acd23a327cada5fb597591267cfc09f08bb1d < 75f91534f9acdfef77f8fa094313b7806f801725; c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 60dbdef2ebc2317266a385e4debdb1bb0e57afe1; c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 381261f24f4e4b41521c0e5ef5cc0b9a786a9862; c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < bf4e671c651534a307ab2fabba4926116beef8c3; c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 214b396480061cbc8b16f2c518b2add7fbfa5192; c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 913f7cf77bf14c13cfea70e89bcb6d0b22239562; 5.10.220 < 5.10.248 · Fixed: < 6.0; 5.10.248 ≤ 5.10.*; 5.15.198 ≤ 5.15.*; 6.1.160 ≤ 6.1.*; 6.6.121 ≤ 6.6.*; 6.12.64 ≤ 6.12.*; 6.18.3 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: c5409ce523af40d5c3019717bc5b4f72038d48be < c182e1e0b7640f6bcc0c5ca8d473f7c57199ea3d, d52acd23a327cada5fb597591267cfc09f08bb1d < 75f91534f9acdfef77f8fa094313b7806f801725, c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 60dbdef2ebc2317266a385e4debdb1bb0e57afe1, c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 381261f24f4e4b41521c0e5ef5cc0b9a786a9862, c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < bf4e671c651534a307ab2fabba4926116beef8c3, c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 214b396480061cbc8b16f2c518b2add7fbfa5192, c0cbe70742f4a70893cd6e5f6b10b6e89b6db95b < 913f7cf77bf14c13cfea70e89bcb6d0b22239562, 5.10.220 < 5.10.248, 5.15.154 < 5.15.198, 6.0 · Fixed: Linux: < 6.0, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.160 ≤ 6.1.*, 6.6.121 ≤ 6.6.*, 6.12.64 ≤ 6.12.*, 6.18.3 ≤ 6.18.*, 6.19 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-2303↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-68803 · cve.blacktree.nl