{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68803 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68803 is a high-severity missing authorization vulnerability in Linux, published on 13 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-68803 and fix it if it is affected.\n\nWhat it is: CVE-2025-68803 is a high-severity missing authorization vulnerability in Linux, published on 13 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-68803 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-68803/ (Markdown: https://insights.sbomify.com/CVE-2025-68803/index.md)","id":"CVE-2025-68803","markdown":"https://insights.sbomify.com/CVE-2025-68803/index.md","name":"CVE-2025-68803","record":{"aliases":["AZL-74297","BELL-CVE-2025-68803","DEBIAN-CVE-2025-68803","GHSA-69qx-3mcm-9wpc","ROOT-OS-DEBIAN-11-CVE-2025-68803","ROOT-OS-DEBIAN-12-CVE-2025-68803","ROOT-OS-DEBIAN-13-CVE-2025-68803","ROOT-OS-UBUNTU-2204-CVE-2025-68803","ROOT-OS-UBUNTU-2404-CVE-2025-68803","UBUNTU-CVE-2025-68803"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel NFS server","requires_auth":"low_privilege","summary":"NFSv4 file creation ignores requested ACLs, allowing clients to bypass intended access controls by receiving default permissions instead.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \"the ACL attribute is set as given\".\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file's\nmode bits rather than returning the originally-specified ACL.","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":"NFSD: NFSv4 file creation neglects setting ACL","id":"CVE-2025-68803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver","id":"CVE-2025-68804"},"packages":[],"prev":{"headline":"drm/xe: Limit num_syncs to prevent oversized allocations","id":"CVE-2025-68802"},"products":["Linux"],"published":"2026-01-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"NFSv4 file creation ignores requested ACLs, allowing clients to bypass intended access controls by receiving default permissions instead.","url":"https://insights.sbomify.com/CVE-2025-68803/"}