{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54281 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54281 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-54281 and fix it if it is affected.\n\nWhat it is: CVE-2023-54281 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-54281 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-54281/ (Markdown: https://insights.sbomify.com/CVE-2023-54281/index.md)","id":"CVE-2023-54281","markdown":"https://insights.sbomify.com/CVE-2023-54281/index.md","name":"CVE-2023-54281","record":{"aliases":["BELL-CVE-2023-54281","DEBIAN-CVE-2023-54281","GHSA-5q4r-9x8x-8xrp","UBUNTU-CVE-2023-54281"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a deadlock in the Linux kernel's Btrfs filesystem via the ino lookup ioctl, causing a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: release path before inode lookup during the ino lookup ioctl\n\nDuring the ino lookup ioctl we can end up calling btrfs_iget() to get an\ninode reference while we are holding on a root's btree. If btrfs_iget()\nneeds to lookup the inode from the root's btree, because it's not\ncurrently loaded in memory, then it will need to lock another or the\nsame path in the same root btree. This may result in a deadlock and\ntrigger the following lockdep splat:\n\n  WARNING: possible circular locking dependency detected\n  6.5.0-rc7-syzkaller-00004-gf7757129e3de #0 Not tainted\n  ------------------------------------------------------\n  syz-executor277/5012 is trying to acquire lock:\n  ffff88802df41710 (btrfs-tree-01){++++}-{3:3}, at: __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136\n\n  but task is already holding lock:\n  ffff88802df418e8 (btrfs-tree-00){++++}-{3:3}, at: __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136\n\n  which lock already depends on the new lock.\n\n  the existing dependency chain (in reverse order) is:\n\n  -\u003e #1 (btrfs-tree-00){++++}-{3:3}:\n         down_read_nested+0x49/0x2f0 kernel/locking/rwsem.c:1645\n         __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136\n         btrfs_search_slot+0x13a4/0x2f80 fs/btrfs/ctree.c:2302\n         btrfs_init_root_free_objectid+0x148/0x320 fs/btrfs/disk-io.c:4955\n         btrfs_init_fs_root fs/btrfs/disk-io.c:1128 [inline]\n         btrfs_get_root_ref+0x5ae/0xae0 fs/btrfs/disk-io.c:1338\n         btrfs_get_fs_root fs/btrfs/disk-io.c:1390 [inline]\n         open_ctree+0x29c8/0x3030 fs/btrfs/disk-io.c:3494\n         btrfs_fill_super+0x1c7/0x2f0 fs/btrfs/super.c:1154\n         btrfs_mount_root+0x7e0/0x910 fs/btrfs/super.c:1519\n         legacy_get_tree+0xef/0x190 fs/fs_context.c:611\n         vfs_get_tree+0x8c/0x270 fs/super.c:1519\n         fc_mount fs/namespace.c:1112 [inline]\n         vfs_kern_mount+0xbc/0x150 fs/namespace.c:1142\n         btrfs_mount+0x39f/0xb50 fs/btrfs/super.c:1579\n         legacy_get_tree+0xef/0x190 fs/fs_context.c:611\n         vfs_get_tree+0x8c/0x270 fs/super.c:1519\n         do_new_mount+0x28f/0xae0 fs/namespace.c:3335\n         do_mount fs/namespace.c:3675 [inline]\n         __do_sys_mount fs/namespace.c:3884 [inline]\n         __se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861\n         do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n         do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80\n         entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\n  -\u003e #0 (btrfs-tree-01){++++}-{3:3}:\n         check_prev_add kernel/locking/lockdep.c:3142 [inline]\n         check_prevs_add kernel/locking/lockdep.c:3261 [inline]\n         validate_chain kernel/locking/lockdep.c:3876 [inline]\n         __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144\n         lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761\n         down_read_nested+0x49/0x2f0 kernel/locking/rwsem.c:1645\n         __btrfs_tree_read_lock+0x2f/0x220 fs/btrfs/locking.c:136\n         btrfs_tree_read_lock fs/btrfs/locking.c:142 [inline]\n         btrfs_read_lock_root_node+0x292/0x3c0 fs/btrfs/locking.c:281\n         btrfs_search_slot_get_root fs/btrfs/ctree.c:1832 [inline]\n         btrfs_search_slot+0x4ff/0x2f80 fs/btrfs/ctree.c:2154\n         btrfs_lookup_inode+0xdc/0x480 fs/btrfs/inode-item.c:412\n         btrfs_read_locked_inode fs/btrfs/inode.c:3892 [inline]\n         btrfs_iget_path+0x2d9/0x1520 fs/btrfs/inode.c:5716\n         btrfs_search_path_in_tree_user fs/btrfs/ioctl.c:1961 [inline]\n         btrfs_ioctl_ino_lookup_user+0x77a/0xf50 fs/btrfs/ioctl.c:2105\n         btrfs_ioctl+0xb0b/0xd40 fs/btrfs/ioctl.c:4683\n         vfs_ioctl fs/ioctl.c:51 [inline]\n         __do_sys_ioctl fs/ioctl.c:870 [inline]\n         __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:856\n         do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n         do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80\n         entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\n  other info \n---truncated---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"btrfs: release path before inode lookup during the ino lookup ioctl","id":"CVE-2023-54281","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"media: tuners: qt1010: replace BUG_ON with a regular error","id":"CVE-2023-54282"},"packages":[],"prev":{"headline":"cifs: fix potential race when tree connecting ipc","id":"CVE-2023-54280"},"products":["Linux"],"published":"2025-12-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can trigger a deadlock in the Linux kernel's Btrfs filesystem via the ino lookup ioctl, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2023-54281/"}