{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68349 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68349 is a high-severity vulnerability in Linux, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68349 and fix it if it is affected.\n\nWhat it is: CVE-2025-68349 is a high-severity vulnerability in Linux, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68349 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-68349/ (Markdown: https://insights.sbomify.com/CVE-2025-68349/index.md)","id":"CVE-2025-68349","markdown":"https://insights.sbomify.com/CVE-2025-68349/index.md","name":"CVE-2025-68349","record":{"aliases":["AZL-73057","BELL-CVE-2025-68349","DEBIAN-CVE-2025-68349","GHSA-pchw-pcf7-8p47","OESA-2026-1011","ROOT-OS-DEBIAN-11-CVE-2025-68349","ROOT-OS-DEBIAN-12-CVE-2025-68349","ROOT-OS-DEBIAN-13-CVE-2025-68349","ROOT-OS-UBUNTU-2204-CVE-2025-68349","ROOT-OS-UBUNTU-2404-CVE-2025-68349","UBUNTU-CVE-2025-68349"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NFS","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel's NFSv4/pNFS module can cause a system crash during inode writes.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u003e nfs4_write_inode\n        -\u003e pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.","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":"NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid","id":"CVE-2025-68349","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"exfat: fix divide-by-zero in exfat_allocate_bitmap","id":"CVE-2025-68350"},"packages":[],"prev":{"headline":"block: fix memory leak in __blkdev_issue_zero_pages","id":"CVE-2025-68348"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel's NFSv4/pNFS module can cause a system crash during inode writes.","url":"https://insights.sbomify.com/CVE-2025-68349/"}