{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74315 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74315 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74315 and fix it if it is affected.\n\nWhat it is: CVE-2026-74315 is a critical vulnerability in Linux, published on 15 Aug 2026. 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-2026-74315 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-2026-74315/ (Markdown: https://insights.sbomify.com/CVE-2026-74315/index.md)","id":"CVE-2026-74315","markdown":"https://insights.sbomify.com/CVE-2026-74315/index.md","name":"CVE-2026-74315","record":{"aliases":["DEBIAN-CVE-2026-74315","GHSA-5v8r-fj78-ffg6","UBUNTU-CVE-2026-74315"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An attacker can read uninitialized kernel memory via NLMv4 file handle hashing, potentially leaking sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlockd: Avoid hashing uninitialized bytes in nlm4svc_lookup_file()\n\nfile_hash() digests the first LOCKD_FH_HASH_SIZE bytes of\nnfs_fh.data when bucketing nlm_files[], independent of fh.size.\nCommit 3de744ee4e45 (\"lockd: Use xdrgen XDR functions for the\nNLMv4 TEST procedure\") set .pc_argzero to zero for the converted\nprocedures and moved file-handle population into\nnlm4svc_lookup_file(), which copies only xdr_lock-\u003efh.len bytes\ninto lock-\u003efh.data.\n\nWhen an NLMv4 client presents a file handle shorter than\nLOCKD_FH_HASH_SIZE, bytes fh.len..31 retain whatever the argument\nbuffer held from an earlier request.  The same wire handle then\nhashes to different buckets across calls; nlm_lookup_file() misses\nthe existing nlm_file entry, and lock-state lookups fail.\n\nZero only the tail bytes that file_hash() would otherwise consume.\nHandles of LOCKD_FH_HASH_SIZE or larger already populate every byte\nthat file_hash() reads.","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":"lockd: Avoid hashing uninitialized bytes in nlm4svc_lookup_file()","id":"CVE-2026-74315","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"NFSD: Handle layout stid in nfsd4_drop_revoked_stid()","id":"CVE-2026-74316"},"packages":[],"prev":{"headline":"bpf: Cancel special fields on map value recycle","id":"CVE-2026-74314"},"products":["Linux"],"published":"2026-08-15","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"An attacker can read uninitialized kernel memory via NLMv4 file handle hashing, potentially leaking sensitive data.","url":"https://insights.sbomify.com/CVE-2026-74315/"}