CVE-2023-54281

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: release path before inode lookup during the ino lookup ioctl

During the ino lookup ioctl we can end up calling btrfs_iget() to get an inode reference while we are holding on a root's btree. If btrfs_iget() needs to lookup the inode from the root's btree, because it's not currently loaded in memory, then it will need to lock another or the same path in the same root btree. This may result in a deadlock and trigger the following lockdep splat:

WARNING: possible circular locking dependency detected 6.5.0-rc7-syzkaller-00004-gf7757129e3de #0 Not tainted ------------------------------------------------------ syz-executor277/5012 is trying to acquire lock: ffff88802df41710 (btrfs-tree-01){++++}-{3:3}, at: __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136

but task is already holding lock: ffff88802df418e8 (btrfs-tree-00){++++}-{3:3}, at: __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #1 (btrfs-tree-00){++++}-{3:3}: down_read_nested+0x49/0x2f0 kernel/locking/rwsem.c:1645 __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136 btrfs_search_slot+0x13a4/0x2f80 fs/btrfs/ctree.c:2302 btrfs_init_root_free_objectid+0x148/0x320 fs/btrfs/disk-io.c:4955 btrfs_init_fs_root fs/btrfs/disk-io.c:1128 [inline] btrfs_get_root_ref+0x5ae/0xae0 fs/btrfs/disk-io.c:1338 btrfs_get_fs_root fs/btrfs/disk-io.c:1390 [inline] open_ctree+0x29c8/0x3030 fs/btrfs/disk-io.c:3494 btrfs_fill_super+0x1c7/0x2f0 fs/btrfs/super.c:1154 btrfs_mount_root+0x7e0/0x910 fs/btrfs/super.c:1519 legacy_get_tree+0xef/0x190 fs/fs_context.c:611 vfs_get_tree+0x8c/0x270 fs/super.c:1519 fc_mount fs/namespace.c:1112 [inline] vfs_kern_mount+0xbc/0x150 fs/namespace.c:1142 btrfs_mount+0x39f/0xb50 fs/btrfs/super.c:1579 legacy_get_tree+0xef/0x190 fs/fs_context.c:611 vfs_get_tree+0x8c/0x270 fs/super.c:1519 do_new_mount+0x28f/0xae0 fs/namespace.c:3335 do_mount fs/namespace.c:3675 [inline] __do_sys_mount fs/namespace.c:3884 [inline] __se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (btrfs-tree-01){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761 down_read_nested+0x49/0x2f0 kernel/locking/rwsem.c:1645 __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136 btrfs_tree_read_lock fs/btrfs/locking.c:142 [inline] btrfs_read_lock_root_node+0x292/0x3c0 fs/btrfs/locking.c:281 btrfs_search_slot_get_root fs/btrfs/ctree.c:1832 [inline] btrfs_search_slot+0x4ff/0x2f80 fs/btrfs/ctree.c:2154 btrfs_lookup_inode+0xdc/0x480 fs/btrfs/inode-item.c:412 btrfs_read_locked_inode fs/btrfs/inode.c:3892 [inline] btrfs_iget_path+0x2d9/0x1520 fs/btrfs/inode.c:5716 btrfs_search_path_in_tree_user fs/btrfs/ioctl.c:1961 [inline] btrfs_ioctl_ino_lookup_user+0x77a/0xf50 fs/btrfs/ioctl.c:2105 btrfs_ioctl+0xb0b/0xd40 fs/btrfs/ioctl.c:4683 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info ---truncated---

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 30, 2025

Last Modified

April 15, 2026

References (5)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.197—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 / 43× 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 127 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(4)

What is CVE-2023-54281?
CVE-2023-54281 is a publicly disclosed vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before inode lookup during the ino lookup ioctl During the ino lookup ioctl we can end up calling btrfs_iget() to get an inode reference while we are holding on a root's btree. If btrfs_iget() needs to lookup…
When was CVE-2023-54281 disclosed?
CVE-2023-54281 was first published in the National Vulnerability Database on December 30, 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-54281 actively exploited?
CVE-2023-54281 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 92.8% of all scored CVEs.
How do I remediate CVE-2023-54281?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54281, 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-54281

Explore →

Is Your Infrastructure Affected by CVE-2023-54281?

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

Start Free Scan →Browse All CVEs