BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-68809High confidence

ksmbd: vfs: fix race on m_flags in vfs_cache

Linux · Linux

9.1CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2025-68809 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ksmbd: Remote race condition leads to data integrity issues and denial of service
274 known not affected

The vendor explicitly states that these products are not 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 ksmbd, a Linux kernel module that provides an SMB3 protocol server. A remote attacker can exploit a race condition due to inconsistent locking when multiple threads concurrently open, close, and delete the same file. This can lead to delete-on-close and pending-delete states being lost or observed inconsistently. Consequently, files may remain on disk after a delete-on-close operation or disappear while still in use, potentially causing data integrity issues or a denial of service.
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-2295

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 actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and pending-delete state in ksmbd_inode->m_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read and modify m_flags under ci->m_lock while others do so without taking the lock at all. Examples: - ksmbd_query_inode_status() and __ksmbd_inode_close() use ci->m_lock when checking or updating m_flags. - ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete() and ksmbd_fd_set_delete_on_close() used to read and modify m_flags without ci->m_lock. This creates a potential data race on m_flags when multiple threads open, close and delete the same file concurrently. In the worst case delete-on-close and pending-delete bits can be lost or observed in an inconsistent state, leading to confusing delete semantics (files that stay on disk after delete-on-close, or files that disappear while still in use). Fix it by: - Making ksmbd_query_inode_status() look at m_flags under ci->m_lock after dropping inode_hash_lock. - Adding ci->m_lock protection to all helpers that read or modify m_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()). - Keeping the existing ci->m_lock protection in __ksmbd_inode_close(), and moving the actual unlink/xattr removal outside the lock. This unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close behaviour.

What

In the Linux kernel, the following vulnerability has been resolved: ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and pending-delete state in ksmbd_inode->m_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read and modify m_flags under ci->m_lock while others do so without taking the lock at all. Examples: - ksmbd_query_inode_status() and __ksmbd_inode_close() use ci->m_lock when checking or updating m_flags. - ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete() and ksmbd_fd_set_delete_on_close() used to read and modify m_flags without ci->m_lock. This creates a potential data race on m_flags when multiple threads open, close and delete the same file concurrently. In the worst case delete-on-close and pending-delete bits can be lost or observed in an inconsistent state, leading to confusing delete semantics (files that stay on disk after delete-on-close, or files that disappear while still in use). Fix it by: - Making ksmbd_query_inode_status() look at m_flags under ci->m_lock after dropping inode_hash_lock. - Adding ci->m_lock protection to all helpers that read or modify m_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()). - Keeping the existing ci->m_lock protection in __ksmbd_inode_close(), and moving the actual unlink/xattr removal outside the lock. This unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close behaviour.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ksmbd: vfs: fix race on m_flags in vfs_cache ksmbd maintains delete-on-close and pending-delete state in ksmbd_inode->m_flags. In vfs_cache.c this field is accessed under inconsistent locking: some paths read and modify m_flags under ci->m_lock while others do so without taking the lock at all. Examples: - ksmbd_query_inode_status() and __ksmbd_inode_close() use ci->m_lock when checking or updating m_flags. - ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete() and ksmbd_fd_set_delete_on_close() used to read and modify m_flags without ci->m_lock. This creates a potential data race on m_flags when multiple threads open, close and delete the same file concurrently. In the worst case delete-on-close and pending-delete bits can be lost or observed in an inconsistent state, leading to confusing delete semantics (files that stay on disk after delete-on-close, or files that disappear while still in use). Fix it by: - Making ksmbd_query_inode_status() look at m_flags under ci->m_lock after dropping inode_hash_lock. - Adding ci->m_lock protection to all helpers that read or modify m_flags (ksmbd_inode_pending_delete(), ksmbd_set_inode_pending_delete(), ksmbd_clear_inode_pending_delete(), ksmbd_fd_set_delete_on_close()). - Keeping the existing ci->m_lock protection in __ksmbd_inode_close(), and moving the actual unlink/xattr removal outside the lock. This unifies the locking around m_flags and removes the data race while preserving the existing delete-on-close behaviour.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may 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
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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.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.
NetworkUnauthenticated
A

Official authority intelligence

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

BSI · German · WID-SEC-W-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
CERT-FR · French · CERTFR-2026-AVI-0787Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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=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-0602Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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-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=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-0545Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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=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-0522Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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-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=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-0495Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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=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-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-0453Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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=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-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-0326Multiples vulnérabilités dans les produits VMware

d?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=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=CVE-2025-68818 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-0316Multiples vulnérabilités dans les produits VMware

d?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=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=CVE-2025-68818 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-0166Multiples vulnérabilités dans le noyau Linux de Debian

d?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=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
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.
Patch available
Affected
f44158485826c076335d6860d35872271a83791d < 5adad9727a815c26013b0d41cfee92ffa7d4037c; f44158485826c076335d6860d35872271a83791d < ccc78781041589ea383e61d5d7a1e9a31b210b93; f44158485826c076335d6860d35872271a83791d < ee63729760f5b61a66f345c54dc4c7514e62383d; f44158485826c076335d6860d35872271a83791d < 991f8a79db99b14c48d20d2052c82d65b9186cad; 5.15
Fixed
< 5.15; 6.6.120 ≤ 6.6.*; 6.12.64 ≤ 6.12.*; 6.18.3 ≤ 6.18.*; 6.19 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
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 13 Jan 2026 · Last source change 5 Aug 2026, 12:11 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-2295
Product sourceCNA
Remediation sourceCVE/CNA references
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 →

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-68809 · cve.blacktree.nl