CVE-2025-66002
Argument Injection in smb4k Mount Helper Allows Arbitrary Unmounts
Publication date: 2026-01-08
Last updated on: 2026-01-08
Assigner: SUSE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kde | smb4k | 4.0.5 |
| kde | smb4k | 4.0.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-88 | The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-66002 is a vulnerability in the privileged mount helper component of smb4k, a KDE utility for mounting Samba/CIFS network shares. It allows local users to perform arbitrary unmount operations and mount with arbitrary arguments due to improper input validation and insufficient restrictions. This includes mounting over critical system directories, passing dangerous command line options to mount.cifs and umount commands, and manipulating environment variables like KRB5CCNAME. These flaws can lead to local denial-of-service, privilege escalation, and information leaks. The root cause includes unsafe API usage and race conditions in mount verification, allowing attackers to bypass checks and unmount arbitrary file systems. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing local users with limited privileges to escalate to full root privileges if they have write access to a Samba share. It can cause denial-of-service by unmounting critical system file systems or mounting malicious binaries over system paths, potentially leading to system compromise. It also risks leaking sensitive information through hijacking Kerberos credentials or accessing protected files. Overall, it threatens system integrity, availability, and confidentiality. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves checking for unauthorized or arbitrary unmount operations performed via the smb4k mount helper. Since the vulnerability allows local users to unmount arbitrary file systems and pass arbitrary options to mount.cifs and umount commands, monitoring for unusual mount or unmount commands with suspicious options (e.g., filemode=04777, uid=0, or -N --namespace) is recommended. Additionally, verifying whether smb4k version 4.0.4 or earlier is installed can help identify vulnerable systems. Specific commands to check mounts and unmounts include: 1) Listing current mounts: `mount | grep cifs` or `findmnt -t cifs` 2) Checking running smb4k processes and their versions: `smb4k --version` or `rpm -q smb4k` 3) Monitoring system logs for mount or unmount commands with unusual parameters. However, no explicit detection commands are provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading smb4k to version 4.0.5 or later, which contains patches addressing the vulnerabilities. Additionally, restrict mount and unmount operations to predefined directories not writable by unprivileged users, whitelist and validate allowed command line options passed to mount.cifs and umount, and avoid passing file paths for Kerberos tickets by using open file descriptors instead. Monitoring and restricting Polkit settings to require authentication for mount/unmount actions can also reduce risk. These mitigations help prevent arbitrary unmounts, privilege escalation, and denial-of-service attacks caused by the vulnerability. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of CVE-2025-66002 on compliance with common standards and regulations such as GDPR or HIPAA. However, given that the vulnerability allows local users to perform arbitrary unmounts and potentially escalate privileges to root, it could lead to unauthorized access or disruption of sensitive data, which may affect compliance with data protection regulations. No direct statements about compliance impact are available in the provided texts. [1, 2]