{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-98082 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98082 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 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-98082 and fix it if it is affected.\n\nWhat it is: CVE-2026-98082 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 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-98082 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-98082/ (Markdown: https://insights.sbomify.com/CVE-2026-98082/index.md)","id":"CVE-2026-98082","markdown":"https://insights.sbomify.com/CVE-2026-98082/index.md","name":"CVE-2026-98082","record":{"aliases":["AZL-104877","BELL-CVE-2026-98082","DEBIAN-CVE-2026-98082","GHSA-572v-238r-mqg6","UBUNTU-CVE-2026-98082"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A memory leak in the Linux kernel's btrfs filesystem can lead to resource exhaustion and denial of service during specific I/O error conditions.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix the possible bioc_list memory leak during error\n\nThere are two possible ways to leak bioc memory on\nbtrfs_ordered_extent::bioc_list:\n\n- An error occurred for btrfs_insert_one_raid_extent()\n  Then the function btrfs_insert_raid_extent() immediately return\n  without freeing any bioc in the bioc_list.\n\n- An ordered extent hit an IO error\n  In that case the ordered extent will have BTRFS_ORDERED_IOERR set, and\n  skip the call on btrfs_insert_raid_extent() completely.\n\nFix the problem by:\n\n- Introduce a new helper, btrfs_cleanup_ordered_bioc_list()\n  Which will remove all bioc from the bioc_list, and release the bioc.\n\n- Call the above helper for btrfs_insert_raid_extent()\n  So that the cleanup helper is always called no matter what.\n\n- Call the above helper for btrfs_finish_one_ordered()\n  This is called just before the final release on the ordered extent.\n\nThis was reported by Sashiko when reviewing another patch.","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: fix the possible bioc_list memory leak during error","id":"CVE-2026-98082","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"btrfs: fix transaction use-after-free in raid stripe insertion","id":"CVE-2026-98083"},"packages":[],"prev":{"headline":"btrfs: zoned: finish active block group cleanup if call_zone_finish() fails","id":"CVE-2026-98081"},"products":["Linux"],"published":"2026-09-25","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-19","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's btrfs filesystem can lead to resource exhaustion and denial of service during specific I/O error conditions.","url":"https://insights.sbomify.com/CVE-2026-98082/"}