CVE-2025-68219
NoneCVSS
—
EPSS
0.2%
Published
Dec 16, 2025
CISA due date
—
Cloudanix analysis
A bug in Linux file-share connection handling could slowly waste system memory when setup errors occur.
- Exploitation
- Local Privilege
- Attacker needs
- Local User
- Complexity
- Low
- Impact
- Denial Of Service
- Component
- OS kernel
- Class
- Memory Corruption
- Remediation
- Patch
- Effort
- Medium
- Patch risk
- Low
What it actually does
Memory leak in smb3_fs_context_parse_param error path where ctx->source and fc->source allocations are not freed before jumping to cifs_parse_mount_err, allowing repeated Opt_source handling to exhaust kernel memory.
Why it matters to the business
Long-running Linux systems performing CIFS mounts may experience gradual memory exhaustion, reduced performance, or out-of-memory conditions, especially in container or CI environments with frequent mount attempts; low EPSS and no KEV status indicate limited immediate operational urgency despite 315 days since publication.
How an attack unfolds
An attacker with local or mount-triggering access could repeatedly invoke CIFS mount operations that allocate source strings then hit an error path before cleanup; the original syzbot-reported sequence involves allocation followed by early return without freeing, though no threat actors or ransomware campaigns are associated and EPSS remains flat at ~0.002.
How to fix it
Upgrade affected Linux kernel to commit 7627864dc3121f39e220f5253a227edf472de59e or later; for Chainguard packages update gitlab-runner, gitlab-docker-machine and related helper images to 17.6.1-r0 or newer.
How to confirm the fix worked
Verify package versions match fixed releases, review kernel changelog for the cited commit, and confirm absence of the described leak sequence in smb3_fs_context_parse_param error handling.
Typical attack path
- Trigger CIFS mount with Opt_source option
- Allocate ctx->source via smb3_fs_context_fullpath
- Allocate fc->source via kstrdup
- Induce subsequent error to reach cifs_parse_mount_err without source cleanup
How to detect it
Review kernel logs and memory accounting for repeated CIFS mount failures; correlate with process activity invoking mount or fsconfig on CIFS filesystems, though no specific post-exploitation artifacts are available.
What your security team should do
- Prioritize kernel and dependent package updates on all CIFS-using systems
- Monitor memory usage trends during CIFS mount operations
- Audit mount configurations to reduce unnecessary error-prone attempts
The record
In the Linux kernel, the following vulnerability has been resolved: cifs: fix memory leak in smb3_fs_context_parse_param error path Add proper cleanup of ctx->source and fc->source to the cifs_parse_mount_err error handler. This ensures that memory allocated for the source strings is correctly freed on all error paths, matching the cleanup already performed in the success path by smb3_cleanup_fs_context_contents(). Pointers are also set to NULL after freeing to prevent potential double-free issues. This change fixes a memory leak originally detected by syzbot. The leak occurred when processing Opt_source mount options if an error happened after ctx->source and fc->source were successfully allocated but before the function completed. The specific leak sequence was: 1. ctx->source = smb3_fs_context_fullpath(ctx, '/') allocates memory 2. fc->source = kstrdup(ctx->source, GFP_KERNEL) allocates more memory 3. A subsequent error jumps to cifs_parse_mount_err 4. The old error handler freed passwords but not the source strings, causing the memory to leak. This issue was not addressed by commit e8c73eb7db0a ("cifs: client: fix memory leak in smb3_fs_context_parse_param"), which only fixed leaks from repeated fsconfig() calls but not this error path. Patch updated with minor change suggested by kernel test robot
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Linux | Kernel | 5.11.0 | 6.6.118 |
| Mageia:9 | kernel | 0 | 6.6.120-1.mga9 |
| Mageia:9 | kernel-linus | 0 | 6.6.120-1.mga9 |
| Mageia:9 | kmod-virtualbox | 0 | 7.1.14-14.mga9 |
| Mageia:9 | kmod-xtables-addons | 0 | 3.24-88.mga9 |
Related vulnerabilities
- CVE-2026-23226 In the Linux kernel, the following vulnerability has been resolved: ksmbd: add chann_lock… Also affects Kernel
- CVE-2026-23225 In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't… Also affects Kernel
- CVE-2026-23230 In the Linux kernel, the following vulnerability has been resolved: smb: client: split… Also affects Kernel
- CVE-2026-23224 In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue… Also affects Kernel
- CVE-2026-23227 In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use… Also affects Kernel
- CVE-2026-23223 In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in… Also affects Kernel
- CVE-2026-23228 In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak… Also affects Kernel
- CVE-2026-23229 In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add… Also affects Kernel