CVE-2026-53284

Filesystem denial of service via premature dirty-tree release

Published Jun 26, 2026 · Updated Jun 26, 2026

Incomplete cleanup in Linux Kernel Btrfs before 6.18.33 or 7.0.10 allows local users to force a filesystem read-only. After btrfs_write_marked_extent() fails, btrfs_write_and_wait_transaction() releases the dirty_pages I/O tree while it still contains unsubmitted dirty records, preventing later transaction cleanup from releasing the associated extent buffers. Triggering the condition requires Btrfs write activity plus an extent-write error; the resulting denial of service blocks further writes to that filesystem.

CVSS severity7.5
High
EPSS probability0.43%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incomplete cleanup in Linux Kernel Btrfs before 6.18.33 or 7.0.10 allows local users to force a filesystem read-only. After btrfs_write_marked_extent() fails, btrfs_write_and_wait_transaction() releases the dirty_pages I/O tree while it still contains unsubmitted dirty records, preventing later transaction cleanup from releasing the associated extent buffers. Triggering the condition requires Btrfs write activity plus an extent-write error; the resulting denial of service blocks further writes to that filesystem.

The record

CVE
CVE-2026-53284
Published
Jun 26, 2026
Updated
Jun 26, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-459, CWE-476, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 26, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.18.33
  2. Affected versionversion=0 <7.0.10
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4066c55e109475a06d18a1f127c939d551211956
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9ebb7eba1237dc198768b9c76506a79f924c82bb
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <df03d67dc63722845cb9fe59d815d1225b04fd54

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=0 <6.18.33; version=0 <7.0.10; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4066c55e109475a06d18a1f127c939d551211956; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9ebb7eba1237dc198768b9c76506a79f924c82bb; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <df03d67dc63722845cb9fe59d815d1225b04fd54

Published CVSS scores

7.5Linux kernel.org CNACVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-459Incomplete Cleanup
CWE-476NULL Pointer Dereference
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo