CVE-2023-53865

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

btrfs: fix warning when putting transaction with qgroups enabled after abort

If we have a transaction abort with qgroups enabled we get a warning triggered when doing the final put on the transaction, like this:

[552.6789] ------------[ cut here ]------------ [552.6815] WARNING: CPU: 4 PID: 81745 at fs/btrfs/transaction.c:144 btrfs_put_transaction+0x123/0x130 [btrfs] [552.6817] Modules linked in: btrfs blake2b_generic xor (...) [552.6819] CPU: 4 PID: 81745 Comm: btrfs-transacti Tainted: G W 6.4.0-rc6-btrfs-next-134+ #1 [552.6819] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014 [552.6819] RIP: 0010:btrfs_put_transaction+0x123/0x130 [btrfs] [552.6821] Code: bd a0 01 00 (...) [552.6821] RSP: 0018:ffffa168c0527e28 EFLAGS: 00010286 [552.6821] RAX: ffff936042caed00 RBX: ffff93604a3eb448 RCX: 0000000000000000 [552.6821] RDX: ffff93606421b028 RSI: ffffffff92ff0878 RDI: ffff93606421b010 [552.6821] RBP: ffff93606421b000 R08: 0000000000000000 R09: ffffa168c0d07c20 [552.6821] R10: 0000000000000000 R11: ffff93608dc52950 R12: ffffa168c0527e70 [552.6821] R13: ffff93606421b000 R14: ffff93604a3eb420 R15: ffff93606421b028 [552.6821] FS: 0000000000000000(0000) GS:ffff93675fb00000(0000) knlGS:0000000000000000 [552.6821] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [552.6821] CR2: 0000558ad262b000 CR3: 000000014feda005 CR4: 0000000000370ee0 [552.6822] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [552.6822] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [552.6822] Call Trace: [552.6822] [552.6822] ? __warn+0x80/0x130 [552.6822] ? btrfs_put_transaction+0x123/0x130 [btrfs] [552.6824] ? report_bug+0x1f4/0x200 [552.6824] ? handle_bug+0x42/0x70 [552.6824] ? exc_invalid_op+0x14/0x70 [552.6824] ? asm_exc_invalid_op+0x16/0x20 [552.6824] ? btrfs_put_transaction+0x123/0x130 [btrfs] [552.6826] btrfs_cleanup_transaction+0xe7/0x5e0 [btrfs] [552.6828] ? _raw_spin_unlock_irqrestore+0x23/0x40 [552.6828] ? try_to_wake_up+0x94/0x5e0 [552.6828] ? __pfx_process_timeout+0x10/0x10 [552.6828] transaction_kthread+0x103/0x1d0 [btrfs] [552.6830] ? __pfx_transaction_kthread+0x10/0x10 [btrfs] [552.6832] kthread+0xee/0x120 [552.6832] ? __pfx_kthread+0x10/0x10 [552.6832] ret_from_fork+0x29/0x50 [552.6832] [552.6832] ---[ end trace 0000000000000000 ]---

This corresponds to this line of code:

void btrfs_put_transaction(struct btrfs_transaction *transaction) { (...) WARN_ON(!RB_EMPTY_ROOT( &transaction->delayed_refs.dirty_extent_root)); (...) }

The warning happens because btrfs_qgroup_destroy_extent_records(), called in the transaction abort path, we free all entries from the rbtree "dirty_extent_root" with rbtree_postorder_for_each_entry_safe(), but we don't actually empty the rbtree - it's still pointing to nodes that were freed.

So set the rbtree's root node to NULL to avoid this warning (assign RB_ROOT).

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

December 9, 2025

Last Modified

April 15, 2026

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.251—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.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-08-05 19:15 UTCEPSS rescore
  2. 2026-08-05 19:15 UTCEPSS rescore
  3. 2026-08-04 10:36 UTCEPSS rescore
  4. 2026-08-03 10:34 UTCEPSS rescore
  5. 2026-08-02 02:25 UTCEPSS rescore
  6. 2026-08-02 02:25 UTCEPSS rescore
  7. 2026-08-01 04:14 UTCEPSS rescore
  8. 2026-07-30 16:26 UTCEPSS rescore
  9. 2026-07-30 01:29 UTCEPSS rescore
  10. 2026-07-28 15:34 UTCEPSS rescore
  11. 2026-07-28 15:34 UTCEPSS rescore
  12. 2026-07-27 05:39 UTCOSV refresh
  13. 2026-07-26 14:53 UTCEPSS rescore
  14. 2026-07-23 14:16 UTCEPSS rescore
  15. 2026-07-23 02:30 UTCEG score recompute
  16. 2026-07-22 23:16 UTCEG score recompute
  17. 2026-07-22 14:07 UTCEPSS rescore
  18. 2026-07-22 14:07 UTCEPSS rescore
  19. 2026-07-21 15:23 UTCEPSS rescore
  20. 2026-07-20 17:06 UTCEPSS rescore
  21. 2026-07-19 14:30 UTCEPSS rescore
  22. 2026-07-19 14:29 UTCEPSS rescore
  23. 2026-07-19 02:27 UTCEPSS rescore
  24. 2026-07-19 02:27 UTCEPSS rescore
  25. 2026-07-18 10:03 UTCEPSS rescore
Show 75 more
  1. 2026-07-18 10:03 UTCEPSS rescore
  2. 2026-07-16 17:01 UTCEPSS rescore
  3. 2026-07-15 16:56 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-15 01:59 UTCEPSS rescore
  6. 2026-07-13 22:28 UTCEPSS rescore
  7. 2026-07-13 22:28 UTCEPSS rescore
  8. 2026-07-13 06:11 UTCEPSS rescore
  9. 2026-07-12 05:45 UTCEPSS rescore
  10. 2026-07-12 05:45 UTCEPSS rescore
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-10 00:17 UTCOSV refresh
  13. 2026-07-09 19:08 UTCEPSS rescore
  14. 2026-07-08 15:13 UTCEPSS rescore
  15. 2026-07-07 13:45 UTCEPSS rescore
  16. 2026-07-07 13:44 UTCEPSS rescore
  17. 2026-07-06 16:26 UTCEPSS rescore
  18. 2026-07-06 16:26 UTCEPSS rescore
  19. 2026-07-06 02:22 UTCEPSS rescore
  20. 2026-07-06 02:22 UTCEPSS rescore
  21. 2026-07-05 02:29 UTCEPSS rescore
  22. 2026-07-04 06:29 UTCEPSS rescore
  23. 2026-07-01 15:05 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
  26. 2026-06-29 14:05 UTCEPSS rescore
  27. 2026-06-28 14:06 UTCEPSS rescore
  28. 2026-06-28 14:06 UTCEPSS rescore
  29. 2026-06-28 04:55 UTCEPSS rescore
  30. 2026-06-27 03:07 UTCEPSS rescore
  31. 2026-06-25 13:48 UTCEPSS rescore
  32. 2026-06-25 13:48 UTCEPSS rescore
  33. 2026-06-24 14:04 UTCEPSS rescore
  34. 2026-06-24 14:04 UTCEPSS rescore
  35. 2026-06-23 21:31 UTCEPSS rescore
  36. 2026-06-23 21:31 UTCEPSS rescore
  37. 2026-06-22 14:24 UTCEPSS rescore
  38. 2026-06-22 14:24 UTCEPSS rescore
  39. 2026-06-21 14:55 UTCEPSS rescore
  40. 2026-06-21 14:55 UTCEPSS rescore
  41. 2026-06-21 11:01 UTCOSV refresh
  42. 2026-06-21 01:58 UTCEPSS rescore
  43. 2026-06-21 01:58 UTCEPSS rescore
  44. 2026-06-19 19:24 UTCEPSS rescore
  45. 2026-06-19 19:24 UTCEPSS rescore
  46. 2026-06-18 17:51 UTCEPSS rescore
  47. 2026-06-17 17:51 UTCEPSS rescore
  48. 2026-06-16 17:51 UTCEPSS rescore
  49. 2026-06-16 17:51 UTCEPSS rescore
  50. 2026-06-15 17:47 UTCEPSS rescore
  51. 2026-06-14 23:16 UTCEPSS rescore
  52. 2026-06-13 22:59 UTCEPSS rescore
  53. 2026-06-13 22:59 UTCEPSS rescore
  54. 2026-06-12 23:11 UTCEPSS rescore
  55. 2026-06-11 13:59 UTCEPSS rescore
  56. 2026-06-10 22:17 UTCEPSS rescore
  57. 2026-06-10 13:21 UTCEPSS rescore
  58. 2026-06-08 14:16 UTCEPSS rescore
  59. 2026-06-08 14:16 UTCEPSS rescore
  60. 2026-06-07 15:24 UTCEPSS rescore
  61. 2026-06-07 15:24 UTCEPSS rescore
  62. 2026-06-06 13:46 UTCEPSS rescore
  63. 2026-06-06 13:46 UTCEPSS rescore
  64. 2026-06-05 22:46 UTCEPSS rescore
  65. 2026-06-05 22:46 UTCEPSS rescore
  66. 2026-06-05 06:09 UTCEPSS rescore
  67. 2026-06-05 06:09 UTCEPSS rescore
  68. 2026-06-04 13:11 UTCEPSS rescore
  69. 2026-06-04 13:11 UTCEPSS rescore
  70. 2026-06-02 20:12 UTCEPSS rescore
  71. 2026-06-02 20:12 UTCEPSS rescore
  72. 2026-06-02 02:09 UTCOSV refresh
  73. 2026-06-01 13:51 UTCEPSS rescore
  74. 2026-05-31 22:30 UTCEPSS rescore
  75. 2026-05-31 22:30 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(4)

What is CVE-2023-53865?
CVE-2023-53865 is a publicly disclosed vulnerability published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix warning when putting transaction with qgroups enabled after abort If we have a transaction abort with qgroups enabled we get a warning triggered when doing the final put on the transaction, like this: [552.6789]…
When was CVE-2023-53865 disclosed?
CVE-2023-53865 was first published in the National Vulnerability Database on December 9, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53865 actively exploited?
CVE-2023-53865 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.5% of all scored CVEs.
How do I remediate CVE-2023-53865?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53865, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-53865

Explore →

Is Your Infrastructure Affected by CVE-2023-53865?

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

Start Free Scan →Browse All CVEs