{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54144 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54144 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-54144 and fix it if it is affected.\n\nWhat it is: CVE-2023-54144 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-54144 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-54144/ (Markdown: https://insights.sbomify.com/CVE-2023-54144/index.md)","id":"CVE-2023-54144","markdown":"https://insights.sbomify.com/CVE-2023-54144/index.md","name":"CVE-2023-54144","record":{"aliases":["BELL-CVE-2023-54144","DEBIAN-CVE-2023-54144","GHSA-vjmx-q9jh-3hmp","UBUNTU-CVE-2023-54144"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A null pointer dereference in the AMD KFD driver during topology setup can cause a kernel warning and potential system instability.","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\ndrm/amdkfd: Fix kernel warning during topology setup\n\nThis patch fixes the following kernel warning seen during\ndriver load by correctly initializing the p2plink attr before\ncreating the sysfs file:\n\n[  +0.002865] ------------[ cut here ]------------\n[  +0.002327] kobject: '(null)' (0000000056260cfb): is not initialized, yet kobject_put() is being called.\n[  +0.004780] WARNING: CPU: 32 PID: 1006 at lib/kobject.c:718 kobject_put+0xaa/0x1c0\n[  +0.001361] Call Trace:\n[  +0.001234]  \u003cTASK\u003e\n[  +0.001067]  kfd_remove_sysfs_node_entry+0x24a/0x2d0 [amdgpu]\n[  +0.003147]  kfd_topology_update_sysfs+0x3d/0x750 [amdgpu]\n[  +0.002890]  kfd_topology_add_device+0xbd7/0xc70 [amdgpu]\n[  +0.002844]  ? lock_release+0x13c/0x2e0\n[  +0.001936]  ? smu_cmn_send_smc_msg_with_param+0x1e8/0x2d0 [amdgpu]\n[  +0.003313]  ? amdgpu_dpm_get_mclk+0x54/0x60 [amdgpu]\n[  +0.002703]  kgd2kfd_device_init.cold+0x39f/0x4ed [amdgpu]\n[  +0.002930]  amdgpu_amdkfd_device_init+0x13d/0x1f0 [amdgpu]\n[  +0.002944]  amdgpu_device_init.cold+0x1464/0x17b4 [amdgpu]\n[  +0.002970]  ? pci_bus_read_config_word+0x43/0x80\n[  +0.002380]  amdgpu_driver_load_kms+0x15/0x100 [amdgpu]\n[  +0.002744]  amdgpu_pci_probe+0x147/0x370 [amdgpu]\n[  +0.002522]  local_pci_probe+0x40/0x80\n[  +0.001896]  work_for_cpu_fn+0x10/0x20\n[  +0.001892]  process_one_work+0x26e/0x5a0\n[  +0.002029]  worker_thread+0x1fd/0x3e0\n[  +0.001890]  ? process_one_work+0x5a0/0x5a0\n[  +0.002115]  kthread+0xea/0x110\n[  +0.001618]  ? kthread_complete_and_exit+0x20/0x20\n[  +0.002422]  ret_from_fork+0x1f/0x30\n[  +0.001808]  \u003c/TASK\u003e\n[  +0.001103] irq event stamp: 59837\n[  +0.001718] hardirqs last  enabled at (59849): [\u003cffffffffb30fab12\u003e] __up_console_sem+0x52/0x60\n[  +0.004414] hardirqs last disabled at (59860): [\u003cffffffffb30faaf7\u003e] __up_console_sem+0x37/0x60\n[  +0.004414] softirqs last  enabled at (59654): [\u003cffffffffb307d9c7\u003e] irq_exit_rcu+0xd7/0x130\n[  +0.004205] softirqs last disabled at (59649): [\u003cffffffffb307d9c7\u003e] irq_exit_rcu+0xd7/0x130\n[  +0.004203] ---[ end trace 0000000000000000 ]---","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":"drm/amdkfd: Fix kernel warning during topology setup","id":"CVE-2023-54144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: drop unnecessary user-triggerable WARN_ONCE in verifierl log","id":"CVE-2023-54145"},"packages":[],"prev":{"headline":"media: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init()","id":"CVE-2023-54143"},"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 null pointer dereference in the AMD KFD driver during topology setup can cause a kernel warning and potential system instability.","url":"https://insights.sbomify.com/CVE-2023-54144/"}