CVE-2026-98091

Analyzed Analyzed - Analysis Complete

Btrfs Filesystem Transaction List Use-After-Free

Publication date: 2026-09-25

Last updated on: 2026-10-23

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-10-23

Generated

2026-11-08

AI Q&A

2026-09-25

EPSS Evaluated

2026-11-07

NVD

CVE-2026-98091

EUVD

EUVD-2026-86921

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.19 (inc) to 7.2.7 (exc)
linux	linux_kernel	7.3
linux	linux_kernel	From 6.13 (inc) to 6.18.53 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.111 (exc)
linux	linux_kernel	From 5.11 (inc) to 5.15.222 (exc)
linux	linux_kernel	From 6.2 (inc) to 6.6.158 (exc)
linux	linux_kernel	From 5.16 (inc) to 6.1.189 (exc)
linux	linux_kernel	From 5.2 (inc) to 5.10.271 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves a flaw in the btrfs filesystem where a device added to a transaction list during metadata chunk creation is not properly detached if subsequent operations fail. This can lead to a use-after-free scenario where the transaction list references freed memory, potentially causing system instability or crashes.

Detection Guidance

This vulnerability is specific to the Linux kernel's btrfs filesystem and requires kernel-level inspection. Detection involves checking kernel logs for warnings related to btrfs device handling or transaction list corruption. Use commands like dmesg | grep -i btrfs or journalctl -k | grep -i btrfs to review kernel messages for errors.

Impact Analysis

This vulnerability could lead to system crashes, data corruption, or unexpected behavior in systems using the btrfs filesystem. If exploited, it may cause denial-of-service conditions or compromise the integrity of stored data.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA as it is a low-level filesystem issue in the Linux kernel. Compliance impacts would depend on how the affected system is used and whether it leads to data corruption or unauthorized access, which is not specified in the provided context.

Mitigation Strategies

Update the Linux kernel to the latest stable version that includes the fix for this btrfs vulnerability. Avoid creating sprout filesystems or adding new devices to existing btrfs filesystems until the kernel is patched. Monitor kernel logs for any related errors after updates.

Hi! I’m here to help you understand CVE-2026-98091. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...