{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68727 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68727 is a vulnerability in Linux, published on 24 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-68727 and fix it if it is affected.\n\nWhat it is: CVE-2025-68727 is a vulnerability in Linux, published on 24 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-68727 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-68727/ (Markdown: https://insights.sbomify.com/CVE-2025-68727/index.md)","id":"CVE-2025-68727","markdown":"https://insights.sbomify.com/CVE-2025-68727/index.md","name":"CVE-2025-68727","record":{"aliases":["BELL-CVE-2025-68727","DEBIAN-CVE-2025-68727","GHSA-c243-x575-hcmp","ROOT-OS-DEBIAN-12-CVE-2025-68727","ROOT-OS-DEBIAN-13-CVE-2025-68727","ROOT-OS-UBUNTU-2204-CVE-2025-68727","ROOT-OS-UBUNTU-2404-CVE-2025-68727","UBUNTU-CVE-2025-68727"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker with local access can read uninitialized kernel memory via the ntfs3 filesystem driver, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nntfs3: Fix uninit buffer allocated by __getname()\n\nFix uninit errors caused after buffer allocation given to 'de'; by\ninitializing the buffer with zeroes. The fix was found by using KMSAN.","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":"ntfs3: Fix uninit buffer allocated by __getname()","id":"CVE-2025-68727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"ntfs3: fix uninit memory after failed mi_read in mi_format_new","id":"CVE-2025-68728"},"packages":[],"prev":{"headline":"crypto: aead - Fix reqsize handling","id":"CVE-2025-68726"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"An attacker with local access can read uninitialized kernel memory via the ntfs3 filesystem driver, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-68727/"}