CVE-2023-53187

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2023-59789 (ENISA EUVD) · GHSA-4xcf-q92v-qp8c (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

btrfs: fix use-after-free of new block group that became unused

If a task creates a new block group and that block group becomes unused before we finish its creation, at btrfs_create_pending_block_groups(), then when btrfs_mark_bg_unused() is called against the block group, we assume that the block group is currently in the list of block groups to reclaim, and we move it out of the list of new block groups and into the list of unused block groups. This has two consequences:

1) We move it out of the list of new block groups associated to the current transaction. So the block group creation is not finished and if we attempt to delete the bg because it's unused, we will not find the block group item in the extent tree (or the new block group tree), its device extent items in the device tree etc, resulting in the deletion to fail due to the missing items;

2) We don't increment the reference count on the block group when we move it to the list of unused block groups, because we assumed the block group was on the list of block groups to reclaim, and in that case it already has the correct reference count. However the block group was on the list of new block groups, in which case no extra reference was taken because it's local to the current task. This later results in doing an extra reference count decrement when removing the block group from the unused list, eventually leading the reference count to 0.

This second case was caught when running generic/297 from fstests, which produced the following assertion failure and stack trace:

[589.559] assertion failed: refcount_read(&block_group->refs) == 1, in fs/btrfs/block-group.c:4299 [589.559] ------------[ cut here ]------------ [589.559] kernel BUG at fs/btrfs/block-group.c:4299! [589.560] invalid opcode: 0000 [#1] PREEMPT SMP PTI [589.560] CPU: 8 PID: 2819134 Comm: umount Tainted: G W 6.4.0-rc6-btrfs-next-134+ #1 [589.560] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 [589.560] RIP: 0010:btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.561] Code: 68 62 da c0 (...) [589.561] RSP: 0018:ffffa55a8c3b3d98 EFLAGS: 00010246 [589.561] RAX: 0000000000000058 RBX: ffff8f030d7f2000 RCX: 0000000000000000 [589.562] RDX: 0000000000000000 RSI: ffffffff953f0878 RDI: 00000000ffffffff [589.562] RBP: ffff8f030d7f2088 R08: 0000000000000000 R09: ffffa55a8c3b3c50 [589.562] R10: 0000000000000001 R11: 0000000000000001 R12: ffff8f05850b4c00 [589.562] R13: ffff8f030d7f2090 R14: ffff8f05850b4cd8 R15: dead000000000100 [589.563] FS: 00007f497fd2e840(0000) GS:ffff8f09dfc00000(0000) knlGS:0000000000000000 [589.563] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [589.563] CR2: 00007f497ff8ec10 CR3: 0000000271472006 CR4: 0000000000370ee0 [589.563] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [589.564] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [589.564] Call Trace: [589.564] [589.565] ? __die_body+0x1b/0x60 [589.565] ? die+0x39/0x60 [589.565] ? do_trap+0xeb/0x110 [589.565] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.566] ? do_error_trap+0x6a/0x90 [589.566] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.566] ? exc_invalid_op+0x4e/0x70 [589.566] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.567] ? asm_exc_invalid_op+0x16/0x20 [589.567] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.567] ? btrfs_free_block_groups+0x449/0x4a0 [btrfs] [589.567] close_ctree+0x35d/0x560 [btrfs] [589.568] ? fsnotify_sb_delete+0x13e/0x1d0 [589.568] ? dispose_list+0x3a/0x50 [589.568] ? evict_inodes+0x151/0x1a0 [589.568] generic_shutdown_super+0x73/0x1a0 [589.569] kill_anon_super+0x14/0x30 [589.569] btrfs_kill_super+0x12/0x20 [btrfs] [589.569] deactivate_locked ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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.2%
EPSS %ILE
5th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Patch available.
Web page

btrfs: fix use-after-free of new block group that became unused - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7569c4294ba6ff9f194635b14876198f8a687c4a
Web page

btrfs: fix use-after-free of new block group that became unused - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6297644db23f77c02ae7961cc542d162629ae2c4
Web page

btrfs: fix use-after-free of new block group that became unused - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0657b20c5a76c938612f8409735a8830d257866e

Vendor Advisories for CVE-2023-53187(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.13-1: fixed in 6.4.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.13-1: fixed in 6.4.13-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 93 of 194 refreshes 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 101 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-28 19:22 UTCEG score recompute
  7. 2026-10-28 19:22 UTCGHSA enrichmentGHSA-4xcf-q92v-qp8c · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-28 18:55 UTCOSV refresh
  9. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-25 17:28 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-20 21:16 UTCEG score recompute
  19. 2026-10-20 21:16 UTCVendor advisory
  20. 2026-10-20 21:16 UTCGHSA enrichmentGHSA-4xcf-q92v-qp8c · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-19 14:55 UTCOSV refresh
  24. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-18 07:41 UTCEG score recompute
Show 68 more
  1. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-12 18:12 UTCEG score recompute
  6. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-11 21:38 UTCEG score recompute
  8. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-09-30 16:37 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-09-26 21:11 UTCOSV refresh
  22. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  27. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  34. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-09-07 06:48 UTCOSV refresh
  37. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-08-20 16:31 UTCOSV refresh
  54. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  57. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  58. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  59. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  61. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  62. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  63. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  64. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  65. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  66. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  67. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  68. 2026-08-05 10:20 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-53187?
CVE-2023-53187 is a high-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix use-after-free of new block group that became unused If a task creates a new block group and that block group becomes unused before we finish its creation, at btrfs_create_pending_block_groups(), then when…
When was the CVE record for CVE-2023-53187 published?
The CVE record for CVE-2023-53187 was published on September 15, 2025. 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53187 actively exploited?
CVE-2023-53187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53187?
CVE-2023-53187 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53187?
A fix for CVE-2023-53187 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53187 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-2023-53187

Explore →

Is Your Infrastructure Affected by CVE-2023-53187?

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

Book a Demo →Browse All CVEs