{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54073 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54073 is a 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-54073 and fix it if it is affected.\n\nWhat it is: CVE-2023-54073 is a 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-54073 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-54073/ (Markdown: https://insights.sbomify.com/CVE-2023-54073/index.md)","id":"CVE-2023-54073","markdown":"https://insights.sbomify.com/CVE-2023-54073/index.md","name":"CVE-2023-54073","record":{"aliases":["BELL-CVE-2023-54073","DEBIAN-CVE-2023-54073","GHSA-7q44-jwgv-r9jh","UBUNTU-CVE-2023-54073"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel TPM","requires_auth":"high_privilege","summary":"A local attacker with high privileges can trigger a kernel crash in the Linux TPM driver by unloading the module on defective AMD hardware.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\ntpm: Add !tpm_amd_is_rng_defective() to the hwrng_unregister() call site\n\nThe following crash was reported:\n\n[ 1950.279393] list_del corruption, ffff99560d485790-\u003enext is NULL\n[ 1950.279400] ------------[ cut here ]------------\n[ 1950.279401] kernel BUG at lib/list_debug.c:49!\n[ 1950.279405] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n[ 1950.279407] CPU: 11 PID: 5886 Comm: modprobe Tainted: G O 6.2.8_1 #1\n[ 1950.279409] Hardware name: Gigabyte Technology Co., Ltd. B550M AORUS PRO-P/B550M AORUS PRO-P,\nBIOS F15c 05/11/2022\n[ 1950.279410] RIP: 0010:__list_del_entry_valid+0x59/0xc0\n[ 1950.279415] Code: 48 8b 01 48 39 f8 75 5a 48 8b 72 08 48 39 c6 75 65 b8 01 00 00 00 c3 cc cc cc\ncc 48 89 fe 48 c7 c7 08 a8 13 9e e8 b7 0a bc ff \u003c0f\u003e 0b 48 89 fe 48 c7 c7 38 a8 13 9e e8 a6 0a bc\nff 0f 0b 48 89 fe\n[ 1950.279416] RSP: 0018:ffffa96d05647e08 EFLAGS: 00010246\n[ 1950.279418] RAX: 0000000000000033 RBX: ffff99560d485750 RCX: 0000000000000000\n[ 1950.279419] RDX: 0000000000000000 RSI: ffffffff9e107c59 RDI: 00000000ffffffff\n[ 1950.279420] RBP: ffffffffc19c5168 R08: 0000000000000000 R09: ffffa96d05647cc8\n[ 1950.279421] R10: 0000000000000003 R11: ffffffff9ea2a568 R12: 0000000000000000\n[ 1950.279422] R13: ffff99560140a2e0 R14: ffff99560127d2e0 R15: 0000000000000000\n[ 1950.279422] FS: 00007f67da795380(0000) GS:ffff995d1f0c0000(0000) knlGS:0000000000000000\n[ 1950.279424] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1950.279424] CR2: 00007f67da7e65c0 CR3: 00000001feed2000 CR4: 0000000000750ee0\n[ 1950.279426] PKRU: 55555554\n[ 1950.279426] Call Trace:\n[ 1950.279428] \u003cTASK\u003e\n[ 1950.279430] hwrng_unregister+0x28/0xe0 [rng_core]\n[ 1950.279436] tpm_chip_unregister+0xd5/0xf0 [tpm]\n\nAdd the forgotten !tpm_amd_is_rng_defective() invariant to the\nhwrng_unregister() call site inside tpm_chip_unregister().","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":"tpm: Add !tpm_amd_is_rng_defective() to the hwrng_unregister() call site","id":"CVE-2023-54073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"net/mlx5e: Use correct encap attribute during invalidation","id":"CVE-2023-54074"},"packages":[],"prev":{"headline":"ALSA: pcm: Fix potential data race at PCM memory allocation helpers","id":"CVE-2023-54072"},"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 with high privileges can trigger a kernel crash in the Linux TPM driver by unloading the module on defective AMD hardware.","url":"https://insights.sbomify.com/CVE-2023-54073/"}