{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64588 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64588 is a high-severity vulnerability in Linux, published on 6 Aug 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-64588 and fix it if it is affected.\n\nWhat it is: CVE-2026-64588 is a high-severity vulnerability in Linux, published on 6 Aug 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-64588 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-64588/ (Markdown: https://insights.sbomify.com/CVE-2026-64588/index.md)","id":"CVE-2026-64588","markdown":"https://insights.sbomify.com/CVE-2026-64588/index.md","name":"CVE-2026-64588","record":{"aliases":["BELL-CVE-2026-64588","DEBIAN-CVE-2026-64588","GHSA-ww4g-j47r-8q39","UBUNTU-CVE-2026-64588"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A data race in the Linux kernel's fuse-uring module allows stale pointer usage, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"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":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfuse-uring: fix data races on ring-\u003eready\n\nOn weakly-ordered architectures, the store to fiq-\u003eops can be\nreordered past the store to ring-\u003eready, allowing a CPU that sees\nring-\u003eready == true via fuse_uring_ready() to dispatch requests\nthrough a stale fiq-\u003eops pointer. Upgrade the store to\nsmp_store_release() and the load in fuse_uring_ready() to\nsmp_load_acquire() so that the preceding WRITE_ONCE(fiq-\u003eops, ...)\nis visible to any CPU that observes ring-\u003eready == true.\n\nAdditionally, fuse_uring_do_register() publishes ring-\u003eready with\nWRITE_ONCE() but the fast-path check reads it with a plain load.\nThis is a marked-vs-unmarked access that KCSAN will flag. Wrap it in\nREAD_ONCE() to mark it without adding unnecessary ordering.\n\nAlso wrap the fc-\u003ering load in fuse_uring_ready() in READ_ONCE() to\nprevent the compiler from reloading it between the NULL check and the\ndereference.","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":"fuse-uring: fix data races on ring-\u003eready","id":"CVE-2026-64588","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"i2c: core: fix NULL-deref on adapter registration failure","id":"CVE-2026-64589"},"packages":[],"prev":{"headline":"net: ethernet: arc: emac: quiesce interrupts before requesting IRQ","id":"CVE-2026-64587"},"products":["Linux"],"published":"2026-08-06","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":"A data race in the Linux kernel's fuse-uring module allows stale pointer usage, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-64588/"}