[CVE-2026-64593][LOW] btrfs: do not trim a device which is not writeable [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-64593
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: btrfs: do not trim a device which is not writeable [ Upstream
Commit: f41ae7e6664f3c4361129728f2c4d5f3ed995251
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f41ae7e6664f3c4361129728f2c4d5f3ed995251
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64593
Analysis date: Thu, 06 Aug 2026 04:00:09 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
Btrfs FITRIM may dereference a NULL device bdev after a missing device is rescanned without becoming writeable, allowing a local storage administrator or delegated storage context to trigger a kernel crash.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64593 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64593

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-64593	LOW	CHECK WITH IMPACT FROM ORIG NN NONE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-362;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'Btrfs FITRIM can crash the kernel when a device that was missing at mount time is later rescanned and has the MISSING state cleared while its bdev pointer remains NULL and the WRITEABLE state is still unset. The vulnerable path reaches btrfs_trim_free_extents_throttle and calls bdev_max_discard_sectors on device bdev before safely excluding this non writable device state. For the CVSS the PR:L is used for the paranoid score because a reduced-capability root, container root, or delegated storage administration context may be enough to trigger FITRIM and device rescan operations in some deployments. The issue is not network reachable and requires local filesystem or storage control plane access. Impact is denial of service via kernel crash. No evidence of UAF, OOB access, arbitrary write, information disclosure, or privilege escalation is visible from the code path.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1)	YES	OOB DANGER NULLPTR DISK SKIP KERNEL_PANIC_PLUS_UAF HARDWARE 	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like**::

## 2. Signal breakdown

Conservative signals:

* Reliable kernel crash / strong DoS: +1. The commit shows a concrete NULL pointer dereference in `btrfs_trim_fs()` via `bdev_max_discard_sectors(device->bdev)`.
* Important filesystem/storage path: +1. The bug is in Btrfs FITRIM device handling.
* Requires admin/root/CAP_SYS_ADMIN in typical deployments: -2. Degraded mount handling, device rescan, and FITRIM are normally storage administration operations.
* Hard or unreliable race / special timing required: -1. The crash depends on a missing device being rescanned and having `MISSING` cleared while `bdev` remains NULL.
* Rare AND difficult-to-reach condition: -1. The scenario needs multi-device degraded Btrfs plus reappearing-device state plus trim.

Paranoid adjustment:

* Use reduced privilege interpretation instead of full admin only in environments with delegated storage administration, container root, or service-managed trim/rescan access. This raises the practical concern slightly, but still no memory corruption primitive is shown.

No added signals for UAF, OOB write, arbitrary write, page-cache corruption, confidentiality impact, integrity impact, or LPE. The primitive is a NULL pointer dereference only.

Call-site confidence: high. The failing call chain and fixed dereference site are both present.

## 3. Reachability analysis

The realistic trigger is local and storage-control-plane based. An attacker would need the ability to influence Btrfs degraded device state, rescan a device, and trigger FITRIM. In normal deployments this requires administrator privileges or equivalent storage management rights. Namespace or container setups only matter if such storage controls are delegated to a reduced-privilege root or service account. The path is not network reachable.

## 4. Severity interpretation

This behaves like ordinary Moderate or Low-like kernel DoS, not Important. Theoretical memory corruption potential is not supported by the patch because `device->bdev` is NULL, not stale attacker-reclaimed memory. Realistic impact is a local kernel crash under specific Btrfs degraded-device timing conditions.

## 5. One-sentence report phrase

Btrfs FITRIM may dereference a NULL device bdev after a missing device is rescanned without becoming writeable, allowing a local storage administrator or delegated storage context to trigger a kernel crash.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED.

Reason: this is a constrained NULL pointer dereference DoS with admin-level storage preconditions, no network reachability, and no evidence of UAF, arbitrary write, information disclosure, or privilege escalation.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: btrfs: do not trim a device which is not writeable [ Upstream
Commit: f41ae7e6664f3c4361129728f2c4d5f3ed995251
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f41ae7e6664f3c4361129728f2c4d5f3ed995251

Changed files:
  fs/btrfs/extent-tree.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f41ae7e6664f3c4361129728f2c4d5f3ed995251

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64593 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64593

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 1

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).