{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54209 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54209 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-54209 and fix it if it is affected.\n\nWhat it is: CVE-2023-54209 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-54209 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-54209/ (Markdown: https://insights.sbomify.com/CVE-2023-54209/index.md)","id":"CVE-2023-54209","markdown":"https://insights.sbomify.com/CVE-2023-54209/index.md","name":"CVE-2023-54209","record":{"aliases":["BELL-CVE-2023-54209","DEBIAN-CVE-2023-54209","GHSA-mxfp-7rqw-mqhc","UBUNTU-CVE-2023-54209"],"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 leak debugfs entries by enabling blktrace via ioctl after disk deletion, potentially causing resource exhaustion.","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\nblock: fix blktrace debugfs entries leakage\n\nCommit 99d055b4fd4b (\"block: remove per-disk debugfs files in\nblk_unregister_queue\") moves blk_trace_shutdown() from\nblk_release_queue() to blk_unregister_queue(), this is safe if blktrace\nis created through sysfs, however, there is a regression in corner\ncase.\n\nblktrace can still be enabled after del_gendisk() through ioctl if\nthe disk is opened before del_gendisk(), and if blktrace is not shutdown\nthrough ioctl before closing the disk, debugfs entries will be leaked.\n\nFix this problem by shutdown blktrace in disk_release(), this is safe\nbecause blk_trace_remove() is reentrant.","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":"block: fix blktrace debugfs entries leakage","id":"CVE-2023-54209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor()","id":"CVE-2023-54210"},"packages":[],"prev":{"headline":"media: ov5675: Fix memleak in ov5675_init_controls()","id":"CVE-2023-54208"},"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 leak debugfs entries by enabling blktrace via ioctl after disk deletion, potentially causing resource exhaustion.","url":"https://insights.sbomify.com/CVE-2023-54209/"}