Linux Kernel up to 6.6.119/6.12.63/6.18.2 ksmbd vfs_cache.c ksmbd_query_inode_status state issue

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.119/6.12.63/6.18.2. It has been rated as critical. This affects the function ksmbd_query_inode_status of the file vfs_cache.c of the component ksmbd. Performing a manipulation results in state issue. This vulnerability was named CVE-2025-68809. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.119/6.12.63/6.18.2. It has been classified as critical. This affects the function ksmbd_query_inode_status of the file vfs_cache.c of the component ksmbd. The manipulation with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. The impact remains unknown. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-68809 since 12/24/2025. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/19/2026).

The vulnerability scanner Nessus provides a plugin with the ID 307007 (Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel vulnerabilities (USN-8179-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.120, 6.12.64, 6.18.3 or 6.19-rc1 eliminates this vulnerability. Applying the patch 5adad9727a815c26013b0d41cfee92ffa7d4037c/ccc78781041589ea383e61d5d7a1e9a31b210b93/ee63729760f5b61a66f345c54dc4c7514e62383d/991f8a79db99b14c48d20d2052c82d65b9186cad is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (307007) and CERT Bund (WID-SEC-2026-0086). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.4

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 307007
Nessus Name: Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel vulnerabilities (USN-8179-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.120/6.12.64/6.18.3/6.19-rc1
Patch: 5adad9727a815c26013b0d41cfee92ffa7d4037c/ccc78781041589ea383e61d5d7a1e9a31b210b93/ee63729760f5b61a66f345c54dc4c7514e62383d/991f8a79db99b14c48d20d2052c82d65b9186cad

Timelineinfo

12/24/2025 CVE reserved
01/13/2026 +20 days Advisory disclosed
01/13/2026 +0 days VulDB entry created
04/19/2026 +96 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68809 (🔒)
GCVE (CVE): GCVE-0-2025-68809
GCVE (VulDB): GCVE-100-340683
CERT Bund: WID-SEC-2026-0086 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 01/13/2026 17:51
Updated: 04/19/2026 20:42
Changes: 01/13/2026 17:51 (60), 03/27/2026 09:38 (7), 04/19/2026 20:42 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!