{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90260 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90260 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 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-90260 and fix it if it is affected.\n\nWhat it is: CVE-2026-90260 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 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-90260 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-90260/ (Markdown: https://insights.sbomify.com/CVE-2026-90260/index.md)","id":"CVE-2026-90260","markdown":"https://insights.sbomify.com/CVE-2026-90260/index.md","name":"CVE-2026-90260","record":{"aliases":["BELL-CVE-2026-90260","DEBIAN-CVE-2026-90260","GHSA-3xv6-4m2c-phmw","UBUNTU-CVE-2026-90260"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A use-after-free style memory corruption in the Linux kernel's btrfs zoned filesystem can cause extent tree corruption and system crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: don't clobber the extent buffer when zeroing it out\n\nOn a zoned filesystem a freed-but-still-dirty tree block is written out\nas zeros (EXTENT_BUFFER_ZONED_ZEROOUT) only to keep the zone write\npointer advancing. btree_csum_one_bio() implemented this by memzeroing\nthe extent buffer's own folios before submission.\n\nThat destroys the in-memory buffer while it may still be referenced. In\nparticular btrfs_free_tree_block() can run on it afterwards and reads\nthe header to add a delayed reference; once the header has been zeroed\nit frees bytenr 0 and corrupts the extent tree (the\nbtrfs_header_bytenr(buf) != 0 ASSERT in btrfs_free_tree_block(), or an\n\"unable to find ref\" abort). It is flaky and reproduces under fsstress,\ne.g. generic/461 and generic/013.\n\nWrite the zeros to disk from the shared zero page instead and leave the\nextent buffer content untouched, so any later reference - including the\ndelayed reference from btrfs_free_tree_block() - still sees a valid\nheader. end_bbio_meta_write() now clears writeback on the buffer's own\nfolios, as the bio no longer carries them.","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: zoned: don't clobber the extent buffer when zeroing it out","id":"CVE-2026-90260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"btrfs: zoned: flush active metadata block group at btree_writepages() start","id":"CVE-2026-90261"},"packages":[],"prev":{"headline":"btrfs: qgroup: fix a wrong length calculation in qgroup_free_reserved_data()","id":"CVE-2026-90259"},"products":["Linux"],"published":"2026-09-17","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-10-21","vendors":["Linux"]},"summary":"A use-after-free style memory corruption in the Linux kernel's btrfs zoned filesystem can cause extent tree corruption and system crashes.","url":"https://insights.sbomify.com/CVE-2026-90260/"}