{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54180 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54180 is a denial of service 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-54180 and fix it if it is affected.\n\nWhat it is: CVE-2023-54180 is a denial of service 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-54180 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-54180/ (Markdown: https://insights.sbomify.com/CVE-2023-54180/index.md)","id":"CVE-2023-54180","markdown":"https://insights.sbomify.com/CVE-2023-54180/index.md","name":"CVE-2023-54180","record":{"aliases":["BELL-CVE-2023-54180","DEBIAN-CVE-2023-54180","GHSA-526g-75xw-f5hp","ROOT-OS-DEBIAN-11-CVE-2023-54180","ROOT-OS-UBUNTU-2204-CVE-2023-54180","UBUNTU-CVE-2023-54180"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can trigger a kernel crash in the Btrfs filesystem during device replacement, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: handle case when repair happens with dev-replace\n\n[BUG]\nThere is a bug report that a BUG_ON() in btrfs_repair_io_failure()\n(originally repair_io_failure() in v6.0 kernel) got triggered when\nreplacing a unreliable disk:\n\n  BTRFS warning (device sda1): csum failed root 257 ino 2397453 off 39624704 csum 0xb0d18c75 expected csum 0x4dae9c5e mirror 3\n  kernel BUG at fs/btrfs/extent_io.c:2380!\n  invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 9 PID: 3614331 Comm: kworker/u257:2 Tainted: G           OE      6.0.0-5-amd64 #1  Debian 6.0.10-2\n  Hardware name: Micro-Star International Co., Ltd. MS-7C60/TRX40 PRO WIFI (MS-7C60), BIOS 2.70 07/01/2021\n  Workqueue: btrfs-endio btrfs_end_bio_work [btrfs]\n  RIP: 0010:repair_io_failure+0x24a/0x260 [btrfs]\n  Call Trace:\n   \u003cTASK\u003e\n   clean_io_failure+0x14d/0x180 [btrfs]\n   end_bio_extent_readpage+0x412/0x6e0 [btrfs]\n   ? __switch_to+0x106/0x420\n   process_one_work+0x1c7/0x380\n   worker_thread+0x4d/0x380\n   ? rescuer_thread+0x3a0/0x3a0\n   kthread+0xe9/0x110\n   ? kthread_complete_and_exit+0x20/0x20\n   ret_from_fork+0x22/0x30\n\n[CAUSE]\n\nBefore the BUG_ON(), we got some read errors from the replace target\nfirst, note the mirror number (3, which is beyond RAID1 duplication,\nthus it's read from the replace target device).\n\nThen at the BUG_ON() location, we are trying to writeback the repaired\nsectors back the failed device.\n\nThe check looks like this:\n\n\t\tret = btrfs_map_block(fs_info, BTRFS_MAP_WRITE, logical,\n\t\t\t\t      \u0026map_length, \u0026bioc, mirror_num);\n\t\tif (ret)\n\t\t\tgoto out_counter_dec;\n\t\tBUG_ON(mirror_num != bioc-\u003emirror_num);\n\nBut inside btrfs_map_block(), we can modify bioc-\u003emirror_num especially\nfor dev-replace:\n\n\tif (dev_replace_is_ongoing \u0026\u0026 mirror_num == map-\u003enum_stripes + 1 \u0026\u0026\n\t    !need_full_stripe(op) \u0026\u0026 dev_replace-\u003etgtdev != NULL) {\n\t\tret = get_extra_mirror_from_replace(fs_info, logical, *length,\n\t\t\t\t\t\t    dev_replace-\u003esrcdev-\u003edevid,\n\t\t\t\t\t\t    \u0026mirror_num,\n\t\t\t\t\t    \u0026physical_to_patch_in_first_stripe);\n\t\tpatch_the_first_stripe_for_dev_replace = 1;\n\t}\n\nThus if we're repairing the replace target device, we're going to\ntrigger that BUG_ON().\n\nBut in reality, the read failure from the replace target device may be\nthat, our replace hasn't reached the range we're reading, thus we're\nreading garbage, but with replace running, the range would be properly\nfilled later.\n\nThus in that case, we don't need to do anything but let the replace\nroutine to handle it.\n\n[FIX]\nInstead of a BUG_ON(), just skip the repair if we're repairing the\ndevice replace target device.","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: handle case when repair happens with dev-replace","id":"CVE-2023-54180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: Fix issue in verifying allow_ptr_leaks","id":"CVE-2023-54181"},"packages":[],"prev":{"headline":"scsi: qla2xxx: Array index may go out of bound","id":"CVE-2023-54179"},"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 kernel crash in the Btrfs filesystem during device replacement, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2023-54180/"}