{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68299 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68299 is a 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-68299 and fix it if it is affected.\n\nWhat it is: CVE-2025-68299 is a 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-68299 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-68299/ (Markdown: https://insights.sbomify.com/CVE-2025-68299/index.md)","id":"CVE-2025-68299","markdown":"https://insights.sbomify.com/CVE-2025-68299/index.md","name":"CVE-2025-68299","record":{"aliases":["DEBIAN-CVE-2025-68299","GHSA-wq3w-wxhr-h474","UBUNTU-CVE-2025-68299"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel AFS filesystem can cause a system crash when mounting a cell before the anonymous key is allocated.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nafs: Fix delayed allocation of a cell's anonymous key\n\nThe allocation of a cell's anonymous key is done in a background thread\nalong with other cell setup such as doing a DNS upcall.  In the reported\nbug, this is triggered by afs_parse_source() parsing the device name given\nto mount() and calling afs_lookup_cell() with the name of the cell.\n\nThe normal key lookup then tries to use the key description on the\nanonymous authentication key as the reference for request_key() - but it\nmay not yet be set and so an oops can happen.\n\nThis has been made more likely to happen by the fix for dynamic lookup\nfailure.\n\nFix this by firstly allocating a reference name and attaching it to the\nafs_cell record when the record is created.  It can share the memory\nallocation with the cell name (unfortunately it can't just overlap the cell\nname by prepending it with \"afs@\" as the cell name already has a '.'\nprepended for other purposes).  This reference name is then passed to\nrequest_key().\n\nSecondly, the anon key is now allocated on demand at the point a key is\nrequested in afs_request_key() if it is not already allocated.  A mutex is\nused to prevent multiple allocation for a cell.\n\nThirdly, make afs_request_key_rcu() return NULL if the anonymous key isn't\nyet allocated (if we need it) and then the caller can return -ECHILD to\ndrop out of RCU-mode and afs_request_key() can be called.\n\nNote that the anonymous key is kind of necessary to make the key lookup\ncache work as that doesn't currently cache a negative lookup, but it's\nprobably worth some investigation to see if NULL can be used instead.","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":"afs: Fix delayed allocation of a cell's anonymous key","id":"CVE-2025-68299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"fs/namespace: fix reference leak in grab_requested_mnt_ns","id":"CVE-2025-68300"},"packages":[],"prev":{"headline":"Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref","id":"CVE-2025-68298"},"products":["Linux"],"published":"2025-12-16","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-08-03","vendors":["Linux"]},"summary":"A null pointer dereference in the Linux kernel AFS filesystem can cause a system crash when mounting a cell before the anonymous key is allocated.","url":"https://insights.sbomify.com/CVE-2025-68299/"}