{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64057 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64057 is a high-severity vulnerability in Linux kernel, published on 19 Jul 2026. 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-2026-64057 and fix it if it is affected.\n\nWhat it is: CVE-2026-64057 is a high-severity vulnerability in Linux kernel, published on 19 Jul 2026. 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-2026-64057 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-64057/ (Markdown: https://insights.sbomify.com/CVE-2026-64057/index.md)","id":"CVE-2026-64057","markdown":"https://insights.sbomify.com/CVE-2026-64057/index.md","name":"CVE-2026-64057","record":{"aliases":["BELL-CVE-2026-64057","DEBIAN-CVE-2026-64057","GHSA-8264-g9fh-vx2h","UBUNTU-CVE-2026-64057"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel AFS","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel AFS filesystem symlink handling can lead to memory leaks or information disclosure.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-667","name":"Improper Locking"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Fix the locking used by afs_get_link()\n\nThe afs filesystem in the kernel doesn't do locking correctly for symbolic\nlinks.  There are a number of problems:\n\n (1) It doesn't do any locking around afs_read_single() to prevent races\n     between multiple -\u003eget_link() calls, thereby allowing the possibility\n     of leaks.\n\n (2) It doesn't use RCU barriering when accessing the buffer pointers\n     during RCU pathwalk.\n\n (3) It can race with another thread updating the contents of the symlink\n     if a third party updated it on the server.\n\nFix this by the following means:\n\n (0) Move symlink handling into its own file as this makes it more\n     complicated.\n\n (1) Take the validate_lock around afs_read_single() to prevent races\n     between multiple -\u003eget_link() calls.\n\n (2) Keep a separate copy of the symlink contents with an rcu_head.  This\n     is always going to be a lot smaller than a page, so it can be\n     kmalloc'd and save quite a bit of memory.  It also needs a refcount\n     for non-RCU pathwalk.\n\n (3) Split the symlink read and write-to-cache routines in afs from those\n     for directories.\n\n (4) Discard the I/O buffer as soon as the write-to-cache completes as this\n     is a full page (plus a folio_queue).\n\n (5) If there's no cache, discard the I/O buffer immediately after reading\n     and copying if there is no cache.","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 the locking used by afs_get_link()","id":"CVE-2026-64057","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"netfs: Fix netfs_read_folio() to wait on writeback","id":"CVE-2026-64058"},"packages":[],"prev":{"headline":"net: ethernet: cortina: Make RX SKB per-port","id":"CVE-2026-64056"},"products":["Linux"],"published":"2026-07-19","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A race condition in the Linux kernel AFS filesystem symlink handling can lead to memory leaks or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-64057/"}