CVE-2023-54067

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 race when deleting free space root from the dirty cow roots list

When deleting the free space tree we are deleting the free space root from the list fs_info->dirty_cowonly_roots without taking the lock that protects it, which is struct btrfs_fs_info::trans_lock. This unsynchronized list manipulation may cause chaos if there's another concurrent manipulation of this list, such as when adding a root to it with ctree.c:add_root_to_dirty_list().

This can result in all sorts of weird failures caused by a race, such as the following crash:

[337571.278245] general protection fault, probably for non-canonical address 0xdead000000000108: 0000 [#1] PREEMPT SMP PTI [337571.278933] CPU: 1 PID: 115447 Comm: btrfs Tainted: G W 6.4.0-rc6-btrfs-next-134+ #1 [337571.279153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [337571.279572] RIP: 0010:commit_cowonly_roots+0x11f/0x250 [btrfs] [337571.279928] Code: 85 38 06 00 (...) [337571.280363] RSP: 0018:ffff9f63446efba0 EFLAGS: 00010206 [337571.280582] RAX: ffff942d98ec2638 RBX: ffff9430b82b4c30 RCX: 0000000449e1c000 [337571.280798] RDX: dead000000000100 RSI: ffff9430021e4900 RDI: 0000000000036070 [337571.281015] RBP: ffff942d98ec2000 R08: ffff942d98ec2000 R09: 000000000000015b [337571.281254] R10: 0000000000000009 R11: 0000000000000001 R12: ffff942fe8fbf600 [337571.281476] R13: ffff942dabe23040 R14: ffff942dabe20800 R15: ffff942d92cf3b48 [337571.281723] FS: 00007f478adb7340(0000) GS:ffff94349fa40000(0000) knlGS:0000000000000000 [337571.281950] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [337571.282184] CR2: 00007f478ab9a3d5 CR3: 000000001e02c001 CR4: 0000000000370ee0 [337571.282416] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [337571.282647] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [337571.282874] Call Trace: [337571.283101] [337571.283327] ? __die_body+0x1b/0x60 [337571.283570] ? die_addr+0x39/0x60 [337571.283796] ? exc_general_protection+0x22e/0x430 [337571.284022] ? asm_exc_general_protection+0x22/0x30 [337571.284251] ? commit_cowonly_roots+0x11f/0x250 [btrfs] [337571.284531] btrfs_commit_transaction+0x42e/0xf90 [btrfs] [337571.284803] ? _raw_spin_unlock+0x15/0x30 [337571.285031] ? release_extent_buffer+0x103/0x130 [btrfs] [337571.285305] reset_balance_state+0x152/0x1b0 [btrfs] [337571.285578] btrfs_balance+0xa50/0x11e0 [btrfs] [337571.285864] ? __kmem_cache_alloc_node+0x14a/0x410 [337571.286086] btrfs_ioctl+0x249a/0x3320 [btrfs] [337571.286358] ? mod_objcg_state+0xd2/0x360 [337571.286577] ? refill_obj_stock+0xb0/0x160 [337571.286798] ? seq_release+0x25/0x30 [337571.287016] ? __rseq_handle_notify_resume+0x3ba/0x4b0 [337571.287235] ? percpu_counter_add_batch+0x2e/0xa0 [337571.287455] ? __x64_sys_ioctl+0x88/0xc0 [337571.287675] __x64_sys_ioctl+0x88/0xc0 [337571.287901] do_syscall_64+0x38/0x90 [337571.288126] entry_SYSCALL_64_after_hwframe+0x72/0xdc [337571.288352] RIP: 0033:0x7f478aaffe9b

So fix this by locking struct btrfs_fs_info::trans_lock before deleting the free space root from that list.

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
7%
KEV
Not listed

Published

December 24, 2025

Last Modified

April 15, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.39—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 7× in last 7d / 42× 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 126 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2023-54067?
CVE-2023-54067 is a publicly disclosed vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race when deleting free space root from the dirty cow roots list When deleting the free space tree we are deleting the free space root from the list fsinfo->dirtycowonly_roots without taking the lock that protects it,…
When was CVE-2023-54067 disclosed?
CVE-2023-54067 was first published in the National Vulnerability Database on December 24, 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-54067 actively exploited?
CVE-2023-54067 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 93.1% of all scored CVEs.
How do I remediate CVE-2023-54067?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54067, 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-54067

Explore →

Is Your Infrastructure Affected by CVE-2023-54067?

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

Start Free Scan →Browse All CVEs