{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68295 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68295 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68295 and fix it if it is affected.\n\nWhat it is: CVE-2025-68295 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68295 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68295/ (Markdown: https://insights.sbomify.com/CVE-2025-68295/index.md)","id":"CVE-2025-68295","markdown":"https://insights.sbomify.com/CVE-2025-68295/index.md","name":"CVE-2025-68295","record":{"aliases":["AZL-72625","BELL-CVE-2025-68295","DEBIAN-CVE-2025-68295","GHSA-8xfh-972h-pq2h","ROOT-OS-DEBIAN-12-CVE-2025-68295","ROOT-OS-DEBIAN-13-CVE-2025-68295","ROOT-OS-UBUNTU-2204-CVE-2025-68295","ROOT-OS-UBUNTU-2404-CVE-2025-68295","UBUNTU-CVE-2025-68295"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a memory leak in the Linux kernel CIFS client, potentially leading to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix memory leak in cifs_construct_tcon()\n\nWhen having a multiuser mount with domain= specified and using\ncifscreds, cifs_set_cifscreds() will end up setting @ctx-\u003edomainname,\nso it needs to be freed before leaving cifs_construct_tcon().\n\nThis fixes the following memory leak reported by kmemleak:\n\n  mount.cifs //srv/share /mnt -o domain=ZELDA,multiuser,...\n  su - testuser\n  cifscreds add -d ZELDA -u testuser\n  ...\n  ls /mnt/1\n  ...\n  umount /mnt\n  echo scan \u003e /sys/kernel/debug/kmemleak\n  cat /sys/kernel/debug/kmemleak\n  unreferenced object 0xffff8881203c3f08 (size 8):\n    comm \"ls\", pid 5060, jiffies 4307222943\n    hex dump (first 8 bytes):\n      5a 45 4c 44 41 00 cc cc                          ZELDA...\n    backtrace (crc d109a8cf):\n      __kmalloc_node_track_caller_noprof+0x572/0x710\n      kstrdup+0x3a/0x70\n      cifs_sb_tlink+0x1209/0x1770 [cifs]\n      cifs_get_fattr+0xe1/0xf50 [cifs]\n      cifs_get_inode_info+0xb5/0x240 [cifs]\n      cifs_revalidate_dentry_attr+0x2d1/0x470 [cifs]\n      cifs_getattr+0x28e/0x450 [cifs]\n      vfs_getattr_nosec+0x126/0x180\n      vfs_statx+0xf6/0x220\n      do_statx+0xab/0x110\n      __x64_sys_statx+0xd5/0x130\n      do_syscall_64+0xbb/0x380\n      entry_SYSCALL_64_after_hwframe+0x77/0x7f","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"smb: client: fix memory leak in cifs_construct_tcon()","id":"CVE-2025-68295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup","id":"CVE-2025-68296"},"packages":[],"prev":{"headline":"io_uring/net: ensure vectored buffer node import is tied to notification","id":"CVE-2025-68294"},"products":["Linux"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-16","vendors":["Linux"]},"summary":"A local attacker can trigger a memory leak in the Linux kernel CIFS client, potentially leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2025-68295/"}