Skip to main content

Linux Kernel CVE-2026-98082

| EUVDEUVD-2026-86912 MEDIUM
Memory Leak (CWE-401)
2026-09-25 Linux GHSA-572v-238r-mqg6
5.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Local access to btrfs RAID-stripe-tree volume
  2. Delivery
    Induce ordered-extent I/O errors or raid-extent insert failures
  3. Exploit
    Leak bioc_list memory per error
  4. Execution
    Exhaust kernel memory
  5. Impact
    Degraded/denied service

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Resource cleanup, leak prevention
Exploitation Conditions

Requires a mounted btrfs filesystem using the RAID stripe tree feature, plus the ability to trigger btrfs error paths: either a failing btrfs_insert_one_raid_extent() call or an ordered extent hitting an I/O error (BTRFS_ORDERED_IOERR set), which is when the bioc_list is leaked. Limiting factors: local access only (AV:L), low-privilege but still authenticated access (PR:L) sufficient to drive btrfs writes, the RAID stripe tree is a relatively new non-default btrfs configuration, and exploitation depends on repeatedly inducing error conditions an attacker cannot reliably force - so meaningful impact requires sustained, abnormal error rates rather than a single operation.

Impact

This is a genuinely low-priority issue despite warranting a patch. Every risk signal points the same direction: the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 5.5 MEDIUM) describes a local, authenticated-only flaw with no confidentiality or integrity impact - only availability. EPSS is 0.17% (5th percentile), the CVE is NOT on CISA KEV, and no public POC is identified, so there is no evidence of exploitation interest. The underlying defect (CWE-401, kernel memory leak of btrfs_ordered_extent::bioc_list entries) is a reliability bug, not a classic weaponizable primitive: there is no memory-corruption or privilege-escalation path described, only gradual kernel memory consumption. One signal to scrutinize: the upstream CVSS sets AC:L, but the leak only occurs on error paths (a failed btrfs_insert_one_raid_extent() or an ordered extent hitting BTRFS_ORDERED_IOERR), which an attacker cannot reliably force on demand - realistic attack complexity is higher than AC:L implies. The input Tag 'Information Disclosure' conflicts with the CVSS vector (C:N) and the CWE (memory leak / availability); this is a mislabel, not an information-disclosure bug. Net: a valid stability fix to roll in with normal kernel updates, not an emergency.

Exploit ScenarioDerived

A local user with the ability to perform writes on a btrfs filesystem using the RAID stripe tree feature repeatedly induces I/O errors or raid-extent insertion failures, each of which leaks bioc structures from the ordered extent's bioc_list. Over many iterations unreclaimable kernel memory accumulates, degrading or eventually denying service on the host. No public exploit code is identified, and the bug requires sustained error conditions rather than a single crafted input.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Memory leak in the Linux kernel's btrfs RAID stripe tree error paths causes bioc objects held on a btrfs_ordered_extent's bioc_list to be dropped without being freed, allowing kernel memory to be exhausted over time when applications repeatedly hit those failure paths. Only systems running btrfs with the relatively new RAID stripe tree feature mounted are affected, and the assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) reflects a local, low-privilege condition whose impact requires sustained or abnormal error rates rather than a single operation. No public exploit code exists and EPSS is only 0.17% (5th percentile), so this is a genuinely low-priority issue despite warranting a patch.

RemediationAI

Apply the upstream kernel fix: update to a release containing the bioc_list cleanup, i.e. kernel 6.6.130, 6.12.111, 6.18.53, 7.2.7 or 7.3-rc2 (or the corresponding mainline commit d043c43d2b4ebcd75ee7f907948ef2847306d6b2 for the current tree), which can be tracked through the stable backports at https://git.kernel.org/stable/c/83f0c973cffb184d019390ffdb5d31de5c85bc61, https://git.kernel.org/stable/c/1b4d4e890c2c85d0f6365b5a08c48b4bbf85deb0, https://git.kernel.org/stable/c/bb4da45766d16503821f167054db76b735d89e94 and https://git.kernel.org/stable/c/afbe73778338e6d1ac8c4486fbdf33f0cc1f2624; distro kernels should be updated via the vendor's own advisory. Where immediate upgrade is not possible, the most effective compensating control is to avoid the non-default btrfs RAID stripe tree feature on affected systems, either by not enabling it at mkfs time or by migrating data off such filesystems, with the trade-off that RAID stripe tree users lose the associated extent-tree space savings and must rebuild the filesystem to change the feature. Because the leak only materializes when writes repeatedly fail, reducing induced I/O errors (healthy storage, correct device sizing, avoiding forced error injection on btrfs RAID stripe tree volumes) lowers the practical risk, and monitoring kernel slab/NUMAlist memory growth on such hosts can provide early warning; neither workaround removes the leak, so patching remains the only complete fix.

Affected VersionsENISA

Linux patch: 6.18.53
Linux 6.6.130 <6.7
Linux 02c372e1f016e5113217597ab37b399c4e407477 <83f0c973cffb184d019390ffdb5d31de5c85bc61
Linux patch: 6.12.111
Linux patch: 7.3-rc2
Linux 02c372e1f016e5113217597ab37b399c4e407477 <bb4da45766d16503821f167054db76b735d89e94
Linux ab69bf6f8970c09d3735c25094e9471d54365282
Linux 02c372e1f016e5113217597ab37b399c4e407477 <afbe73778338e6d1ac8c4486fbdf33f0cc1f2624
Linux patch: 0
Linux 02c372e1f016e5113217597ab37b399c4e407477 <1b4d4e890c2c85d0f6365b5a08c48b4bbf85deb0
Linux patch: 7.2.7
Linux 6.7

Affected Packages

euvd linux fix: 6.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

btrfs maintains per-ordered-extent bookkeeping for the RAID stripe tree: btrfs_ordered_extent carries a bioc_list of btrfs_bio_control (bioc) structures that describe the physical extents to be inserted into the stripe tree. Two code paths fail to unwind that list. First, if btrfs_insert_one_raid_extent() returns an error, btrfs_insert_raid_extent() returns immediately without freeing any bioc still queued on bioc_list. Second, when an ordered extent hits an I/O error and BTRFS_ORDERED_IOERR is set, the finish path skips btrfs_insert_raid_extent() entirely, so the bioc_list is never drained. The upstream fix adds a helper, btrfs_cleanup_ordered_bioc_list(), that walks and removes every bioc on the list and releases it, then calls it unconditionally from btrfs_insert_raid_extent() and from btrfs_finish_one_ordered() just before the ordered extent is finally released. The root cause class is CWE-401 (Missing Release of Memory after Effective Lifetime); it is not a use-after-free or corruption bug, so confidentiality and integrity are unaffected and only availability degrades. Note that NVD publishes a base score of 5.5 with AC:L while the independent assessment scores AC:H because the leak is only realized on abnormal error conditions; the RAID stripe tree is a non-default, recently introduced btrfs configuration, which further narrows exposure.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI 4.7 MEDIUM

Local btrfs access gives AV:L/PR:L; the leak only fires on hard-to-force error paths so AC:H; no data exposure (C:N/I:N) and only gradual memory exhaustion gives A:H.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE 3.3 LOW
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Red Hat 5.5 LOW

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 06, 2026 - 15:07 NVD
5.5 (MEDIUM)
Patch available
Sep 25, 2026 - 11:02 EUVD
CVE Published
Sep 25, 2026 - 10:24 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 25, 2026 - 10:24 nvd
MEDIUM 5.5

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

btrfs: fix the possible bioc_list memory leak during error

There are two possible ways to leak bioc memory on btrfs_ordered_extent::bioc_list:

  • An error occurred for btrfs_insert_one_raid_extent()

Then the function btrfs_insert_raid_extent() immediately return without freeing any bioc in the bioc_list.

  • An ordered extent hit an IO error

In that case the ordered extent will have BTRFS_ORDERED_IOERR set, and skip the call on btrfs_insert_raid_extent() completely.

Fix the problem by:

  • Introduce a new helper, btrfs_cleanup_ordered_bioc_list()

Which will remove all bioc from the bioc_list, and release the bioc.

  • Call the above helper for btrfs_insert_raid_extent()

So that the cleanup helper is always called no matter what.

  • Call the above helper for btrfs_finish_one_ordered()

This is called just before the final release on the ordered extent.

This was reported by Sashiko when reviewing another patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Ubiquitous
Linux kernel is ubiquitous, though btrfs RAID stripe tree is an opt-in subset
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Vendor StatusVendor

SUSE

Severity: Low
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy