LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon()

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix memory leak in cifs_construct_tcon() When having a multiuser mount with domain= specified and using cifscreds, cifs_set_cifscreds() will end up setting @ctx->domainname, so it needs to be freed before leaving cifs_construct_tcon(). This fixes the following memory leak reported by kmemleak: mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,... su - testuser cifscreds add -d ZELDA -u testuser ... ls /mnt/1 ... umount /mnt echo scan > /sys/kernel/debug/kmemleak cat /sys/kernel/debug/kmemleak unreferenced object 0xffff8881203c3f08 (size 8): comm "ls", pid 5060, jiffies 4307222943 hex dump (first 8 bytes): 5a 45 4c 44 41 00 cc cc ZELDA... backtrace (crc d109a8cf): __kmalloc_node_track_caller_noprof+0x572/0x710 kstrdup+0x3a/0x70 cifs_sb_tlink+0x1209/0x1770 [cifs] cifs_get_fattr+0xe1/0xf50 [cifs] cifs_get_inode_info+0xb5/0x240 [cifs] cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs] cifs_getattr+0x28e/0x450 [cifs] vfs_getattr_nosec+0x126/0x180 vfs_statx+0xf6/0x220 do_statx+0xab/0x110 __x64_sys_statx+0xd5/0x130 do_syscall_64+0xbb/0x380 entry_SYSCALL_64_after_hwframe+0x77/0x7f

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2025-68295 is a Linux kernel SMB/CIFS client memory leak. It appears tied to a specific setup: multiuser CIFS mounts using a domain and cifscreds. The public record does not show active exploitation, CVSS, or broad impact details. Treat this as a patch hygiene issue unless affected file-sharing clients are operationally important.

Executive priority

Schedule remediation through normal kernel patch cycles, with faster handling for systems that depend on domain-based multiuser CIFS mounts. Current evidence supports low urgency because the record describes a memory leak and does not cite exploitation or severe security impact.

Technical view

The resolved flaw frees ctx->domainname in cifs_construct_tcon(). Without that cleanup, cifs_set_cifscreds() can allocate a domain name during multiuser CIFS access and leave it unreferenced. The source describes kmemleak evidence during CIFS attribute lookup paths after use of cifscreds with a domain.

Likely exposure

Exposure is most likely on Linux systems acting as SMB/CIFS clients with multiuser mounts, domain= configured, and cifscreds usage. Systems not using the CIFS client, not using multiuser mounts, or not using domain-based cifscreds appear less likely to be affected based on the record.

Exploitation context

The provided sources do not report active exploitation, KEV listing, public weaponization, privilege escalation, or remote code execution. The described impact is a kernel memory leak triggered by normal CIFS client activity under a specific configuration.

Researcher notes

The source bundle is narrow: it provides the kernel fix rationale, kmemleak trace, affected Linux version data, and stable commit references. It does not provide CVSS, CWE, exploitability analysis, or downstream distribution mappings. Avoid expanding impact beyond the CIFS client memory leak evidence.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • Follow distribution vendor advisories for package-specific fixed versions.
  • Prioritize hosts using CIFS multiuser mounts with domain credentials.
  • Review whether affected CIFS mount patterns are operationally required before patching.
  • Monitor affected clients for memory pressure until updates are applied.

Validation and detection

  • Inventory Linux hosts using CIFS or SMB client mounts.
  • Identify mounts using multiuser, domain=, and cifscreds workflows.
  • Confirm kernel builds include the relevant stable fix commit.
  • Check distribution changelogs for CVE-2025-68295 backports.
  • Use kernel memory diagnostics in a lab to confirm leak remediation.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68295 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf2aee329a68f5a907bcff11a109dfe17c0b41aeb, f2aee329a68f5a907bcff11a109dfe17c0b41aeb, f2aee329a68f5a907bcff11a109dfe17c0b41aeb, f2aee329a68f5a907bcff11a109dfe17c0b41aeb, f2aee329a68f5a907bcff11a109dfe17c0b41aeb, f2aee329a68f5a907bcff11a109dfe17c0b41aeb, f2aee329a68f5a907bcff11a109dfe17c0b41aeb, 1456d3cea31114137fabf1110d20a2e2c6d6060f, 16764d7486d02b1699ae16e91d7a577602398b17, 904847402bd74a28164bd4d8da082d1eace7c190, 325fa2a6729b74b2806b31725940cb54658515e5, 8db988a982908b7bff76e095000adabf9c29698b, 4.4.194, 4.9.194, 4.14.146, 4.19.75, 5.2.17unaffected
LinuxLinux5.3, 0, 5.10.247, 5.15.197, 6.1.159, 6.6.119, 6.12.61, 6.17.11, 6.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.