{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72378 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72378 is a high-severity 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-72378 and fix it if it is affected.\n\nWhat it is: CVE-2026-72378 is a high-severity 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-72378 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-72378/ (Markdown: https://insights.sbomify.com/CVE-2026-72378/index.md)","id":"CVE-2026-72378","markdown":"https://insights.sbomify.com/CVE-2026-72378/index.md","name":"CVE-2026-72378","record":{"aliases":["BELL-CVE-2026-72378","DEBIAN-CVE-2026-72378","GHSA-2wjr-8gx8-q69w","UBUNTU-CVE-2026-72378"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel AFS","requires_auth":"none","summary":"Incorrect error code handling in the Linux kernel AFS module may lead to unexpected behavior during volume location address extraction.","user_interaction":"not_required","vuln_class":"other"},"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\nafs: Fix error code in afs_extract_vl_addrs()\n\nThe error codes on these paths are only set on the first iteration\nthrough the loop.  Set the correct error code on every iteration.","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 error code in afs_extract_vl_addrs()","id":"CVE-2026-72378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid","id":"CVE-2026-72379"},"packages":[],"prev":{"headline":"afs: Remove setting of AS_RELEASE_ALWAYS for symlinks and mountpoints","id":"CVE-2026-72377"},"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":"Incorrect error code handling in the Linux kernel AFS module may lead to unexpected behavior during volume location address extraction.","url":"https://insights.sbomify.com/CVE-2026-72378/"}