{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54045 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54045 is a denial of service vulnerability in Linux, published on 24 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-54045 and fix it if it is affected.\n\nWhat it is: CVE-2023-54045 is a denial of service vulnerability in Linux, published on 24 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-54045 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-54045/ (Markdown: https://insights.sbomify.com/CVE-2023-54045/index.md)","id":"CVE-2023-54045","markdown":"https://insights.sbomify.com/CVE-2023-54045/index.md","name":"CVE-2023-54045","record":{"aliases":["BELL-CVE-2023-54045","DEBIAN-CVE-2023-54045","GHSA-857x-v7jh-w473","UBUNTU-CVE-2023-54045"],"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":"low_privilege","summary":"A local attacker can cause a kernel soft lockup and system crash by creating tracefs instances when audit logging is configured.","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\naudit: fix possible soft lockup in __audit_inode_child()\n\nTracefs or debugfs maybe cause hundreds to thousands of PATH records,\ntoo many PATH records maybe cause soft lockup.\n\nFor example:\n  1. CONFIG_KASAN=y \u0026\u0026 CONFIG_PREEMPTION=n\n  2. auditctl -a exit,always -S open -k key\n  3. sysctl -w kernel.watchdog_thresh=5\n  4. mkdir /sys/kernel/debug/tracing/instances/test\n\nThere may be a soft lockup as follows:\n  watchdog: BUG: soft lockup - CPU#45 stuck for 7s! [mkdir:15498]\n  Kernel panic - not syncing: softlockup: hung tasks\n  Call trace:\n   dump_backtrace+0x0/0x30c\n   show_stack+0x20/0x30\n   dump_stack+0x11c/0x174\n   panic+0x27c/0x494\n   watchdog_timer_fn+0x2bc/0x390\n   __run_hrtimer+0x148/0x4fc\n   __hrtimer_run_queues+0x154/0x210\n   hrtimer_interrupt+0x2c4/0x760\n   arch_timer_handler_phys+0x48/0x60\n   handle_percpu_devid_irq+0xe0/0x340\n   __handle_domain_irq+0xbc/0x130\n   gic_handle_irq+0x78/0x460\n   el1_irq+0xb8/0x140\n   __audit_inode_child+0x240/0x7bc\n   tracefs_create_file+0x1b8/0x2a0\n   trace_create_file+0x18/0x50\n   event_create_dir+0x204/0x30c\n   __trace_add_new_event+0xac/0x100\n   event_trace_add_tracer+0xa0/0x130\n   trace_array_create_dir+0x60/0x140\n   trace_array_create+0x1e0/0x370\n   instance_mkdir+0x90/0xd0\n   tracefs_syscall_mkdir+0x68/0xa0\n   vfs_mkdir+0x21c/0x34c\n   do_mkdirat+0x1b4/0x1d4\n   __arm64_sys_mkdirat+0x4c/0x60\n   el0_svc_common.constprop.0+0xa8/0x240\n   do_el0_svc+0x8c/0xc0\n   el0_svc+0x20/0x30\n   el0_sync_handler+0xb0/0xb4\n   el0_sync+0x160/0x180\n\nTherefore, we add cond_resched() to __audit_inode_child() to fix it.","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":"audit: fix possible soft lockup in __audit_inode_child()","id":"CVE-2023-54045","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":9,"next":{"headline":"crypto: essiv - Handle EBUSY correctly","id":"CVE-2023-54046"},"packages":[],"prev":{"headline":"spmi: Add a check for remove callback when removing a SPMI driver","id":"CVE-2023-54044"},"products":["Linux"],"published":"2025-12-24","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 cause a kernel soft lockup and system crash by creating tracefs instances when audit logging is configured.","url":"https://insights.sbomify.com/CVE-2023-54045/"}