{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98961 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98961 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98961 and fix it if it is affected.\n\nWhat it is: CVE-2026-98961 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98961 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-98961/ (Markdown: https://insights.sbomify.com/CVE-2026-98961/index.md)","id":"CVE-2026-98961","markdown":"https://insights.sbomify.com/CVE-2026-98961/index.md","name":"CVE-2026-98961","record":{"aliases":["BELL-CVE-2026-98961","DEBIAN-CVE-2026-98961","GHSA-3xcr-f59c-pjvq","UBUNTU-CVE-2026-98961"],"analysis":null,"analysis_generated_by":null,"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\nbtrfs: unlock inode and extent in caller when io_uring read extent fails\n\nbtrfs_uring_read_extent() runs only after btrfs_encoded_read() has taken\nthe inode shared lock and the extent lock.  On failure it used to unlock\nin out_fail, and a pages-array allocation failure returned -ENOMEM\nwithout unlocking at all.\n\nUnlock in the caller instead on all failure returns, matching the\ncopy_to_user() error path.  The deferred -EIOCBQUEUED path still unlocks\nin btrfs_uring_read_finished().","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":"btrfs: unlock inode and extent in caller when io_uring read extent fails","id":"CVE-2026-98961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"btrfs: free iov when btrfs_uring_read_extent() fails","id":"CVE-2026-98962"},"packages":[],"prev":{"headline":"btrfs: don't stash io_uring encoded data across -EAGAIN","id":"CVE-2026-98960"},"products":["Linux"],"published":"2026-10-23","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-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98961/"}