CVE-2026-53284

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-39889 (ENISA EUVD) · GHSA-r3r8-3hxx-x882 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

btrfs: only release the dirty pages io tree after successful writes

[WARNING] With extra warning on dirty extent buffers at umount (aka, the next patch in the series), test case generic/388 can trigger the following warning about dirty extent buffers at unmount time:

BTRFS critical (device dm-2 state E): emergency shutdown BTRFS error (device dm-2 state E): error while writing out transaction: -30 BTRFS warning (device dm-2 state E): Skipping commit of aborted transaction. BTRFS error (device dm-2 state EA): Transaction 9 aborted (error -30) BTRFS: error (device dm-2 state EA) in cleanup_transaction:2068: errno=-30 Readonly filesystem BTRFS info (device dm-2 state EA): forced readonly BTRFS info (device dm-2 state EA): last unmount of filesystem 4fbf2e15-f941-49a0-bc7c-716315d2777c ------------[ cut here ]------------ WARNING: disk-io.c:3311 at invalidate_and_check_btree_folios+0xfd/0x1ca [btrfs], CPU#8: umount/914368 CPU: 8 UID: 0 PID: 914368 Comm: umount Tainted: G OE 7.1.0-rc1-custom+ #372 PREEMPT(full) 2de38db8d1deae71fde295430a0ff3ab98ccf596 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 RIP: 0010:invalidate_and_check_btree_folios+0xfd/0x1ca [btrfs] Call Trace: close_ctree+0x52e/0x574 [btrfs d2f0b1cd330d1287e7a9919d112eadfc0e914efd] generic_shutdown_super+0x89/0x1a0 kill_anon_super+0x16/0x40 btrfs_kill_super+0x16/0x20 [btrfs d2f0b1cd330d1287e7a9919d112eadfc0e914efd] deactivate_locked_super+0x2d/0xb0 cleanup_mnt+0xdc/0x140 task_work_run+0x5a/0xa0 exit_to_user_mode_loop+0x123/0x4b0 do_syscall_64+0x243/0x7c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 ---[ end trace 0000000000000000 ]--- BTRFS warning (device dm-2 state EA): unable to release extent buffer 30539776 owner 9 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30621696 owner 257 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30638080 owner 258 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30654464 owner 7 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30703616 owner 2 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30720000 owner 10 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30736384 owner 4 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30752768 owner 11 gen 9 refs 2 flags 0x7

I'm using a stripped down version, which seems to trigger the warning more reliably:

_fsstress_pid="" workload() { dmesg -C mkfs.btrfs -f -K $dev > /dev/null echo 1 > /sys/kernel/debug/clear_warn_once mount $dev $mnt $fsstress -w -n 1024 -p 4 -d $mnt & _fsstress_pid=$! sleep 0 $godown $mnt pkill --echo -PIPE fsstress > /dev/null wait $_fsstress_pid unset _fsstress_pid umount $mnt

if dmesg | grep -q "WARNING"; then fail fi }

for (( i = 0; i < $runtime; i++ )); do echo "=== $i/$runtime ===" workload done

[CAUSE] Inside btrfs_write_and_wait_transaction(), we first try to write all dirty ebs, then wait for them to finish.

After that we call btrfs_extent_io_tree_release() to free all extent states from dirty_pages io tree.

However if we hit an error from btrfs_write_marked_extent(), then we still call btrfs_extent_io_tree_release() to clear that dirty_pages io tree, which may contain dirty records that we haven't yet submitted.

Furthermore, the later transaction cleanup path will utilize that dirty_pages io tree to properly cleanup those dirty ebs, but since it's already empty, no dirty ebs are properly cleaned up, thus will later trigger the warnings inside invalidate_btree_folios(). ---truncated---

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 26, 2026

Last Modified

October 30, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
Patch available.
Web page

btrfs: only release the dirty pages io tree after successful writes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/df03d67dc63722845cb9fe59d815d1225b04fd54
Web page

btrfs: only release the dirty pages io tree after successful writes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ebb7eba1237dc198768b9c76506a79f924c82bb
Web page

btrfs: only release the dirty pages io tree after successful writes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4066c55e109475a06d18a1f127c939d551211956

Vendor Advisories for CVE-2026-53284(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-10-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-30ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-30ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-30ubuntu
linuxKernel @ 6.18.33 (fixes >=3.19.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (375 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (144 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 365 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 265 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 20:41 UTCEchelonGraph re-scored
  2. 2026-11-12 20:41 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-11-06 05:05 UTCEchelonGraph re-scored
  11. 2026-11-06 05:05 UTCVendor advisory
  12. 2026-11-06 05:05 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  20. 2026-10-30 13:28 UTCEchelonGraph re-scored
  21. 2026-10-30 13:28 UTCVendor advisory
  22. 2026-10-30 13:28 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-30 12:30 UTCEchelonGraph re-scored
  24. 2026-10-30 12:30 UTCVendor advisory
  25. 2026-10-30 12:30 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
Show 75 more
  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-10-28 15:02 UTCEchelonGraph re-scored
  4. 2026-10-28 15:02 UTCVendor advisory
  5. 2026-10-28 15:02 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  9. 2026-10-25 14:20 UTCEchelonGraph re-scored
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-21 13:50 UTCEchelonGraph re-scored
  15. 2026-10-21 13:50 UTCVendor advisory
  16. 2026-10-21 13:49 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-21 12:54 UTCEchelonGraph re-scored
  18. 2026-10-21 12:54 UTCVendor advisory
  19. 2026-10-21 12:54 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-18 03:31 UTCEchelonGraph re-scored
  24. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  25. 2026-10-17 11:10 UTCEchelonGraph re-scored
  26. 2026-10-17 11:10 UTCVendor advisory
  27. 2026-10-17 11:10 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  29. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-10-13 20:54 UTCOSV refresh
  32. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  33. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-10-12 15:57 UTCEchelonGraph re-scored
  35. 2026-10-11 19:40 UTCEchelonGraph re-scored
  36. 2026-10-11 16:55 UTCEchelonGraph re-scored
  37. 2026-10-11 14:19 UTCEchelonGraph re-scored
  38. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  40. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  41. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  42. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  43. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  44. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  45. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  47. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  48. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  50. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  51. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  52. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  54. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  56. 2026-09-23 07:47 UTCEchelonGraph re-scored
  57. 2026-09-23 07:47 UTCVendor advisory
  58. 2026-09-23 07:46 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  61. 2026-09-18 07:10 UTCEchelonGraph re-scored
  62. 2026-09-18 07:10 UTCVendor advisory
  63. 2026-09-18 07:10 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  65. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  66. 2026-09-14 00:58 UTCEchelonGraph re-scored
  67. 2026-09-14 00:58 UTCVendor advisory
  68. 2026-09-14 00:58 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  69. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  70. 2026-09-13 09:31 UTCVendor advisory
  71. 2026-09-13 09:31 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-09-12 15:31 UTCEchelonGraph re-scored
  73. 2026-09-12 15:31 UTCVendor advisory
  74. 2026-09-12 15:31 UTCGHSA enrichmentGHSA-r3r8-3hxx-x882 · GitHub severity HIGH · GitHub CVSS 7.5
  75. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile

Related CVEs(same vendor + same CWE)· as of November 11, 2026

Frequently asked(5)

What is CVE-2026-53284?
CVE-2026-53284 is a high-severity vulnerability; its CVE record was published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: only release the dirty pages io tree after successful writes [WARNING] With extra warning on dirty extent buffers at umount (aka, the next patch in the series), test case generic/388 can trigger the following warning about…
When was the CVE record for CVE-2026-53284 published?
The CVE record for CVE-2026-53284 was published on June 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-53284 actively exploited?
CVE-2026-53284 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53284?
CVE-2026-53284 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53284?
A fix for CVE-2026-53284 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53284 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53284

Explore →

Is Your Infrastructure Affected by CVE-2026-53284?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs