# CVE-2023-54144: drm/amdkfd: Fix kernel warning during topology setup
> A null pointer dereference in the AMD KFD driver during topology setup can cause a kernel warning and potential system instability.
- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54144, DEBIAN-CVE-2023-54144, GHSA-vjmx-q9jh-3hmp, UBUNTU-CVE-2023-54144
## What is CVE-2023-54144?
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.
### Official description
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Fix kernel warning during topology setup
This patch fixes the following kernel warning seen during
driver load by correctly initializing the p2plink attr before
creating the sysfs file:
[ +0.002865] ------------[ cut here ]------------
[ +0.002327] kobject: '(null)' (0000000056260cfb): is not initialized, yet kobject_put() is being called.
[ +0.004780] WARNING: CPU: 32 PID: 1006 at lib/kobject.c:718 kobject_put+0xaa/0x1c0
[ +0.001361] Call Trace:
[ +0.001234]
[ +0.001067] kfd_remove_sysfs_node_entry+0x24a/0x2d0 [amdgpu]
[ +0.003147] kfd_topology_update_sysfs+0x3d/0x750 [amdgpu]
[ +0.002890] kfd_topology_add_device+0xbd7/0xc70 [amdgpu]
[ +0.002844] ? lock_release+0x13c/0x2e0
[ +0.001936] ? smu_cmn_send_smc_msg_with_param+0x1e8/0x2d0 [amdgpu]
[ +0.003313] ? amdgpu_dpm_get_mclk+0x54/0x60 [amdgpu]
[ +0.002703] kgd2kfd_device_init.cold+0x39f/0x4ed [amdgpu]
[ +0.002930] amdgpu_amdkfd_device_init+0x13d/0x1f0 [amdgpu]
[ +0.002944] amdgpu_device_init.cold+0x1464/0x17b4 [amdgpu]
[ +0.002970] ? pci_bus_read_config_word+0x43/0x80
[ +0.002380] amdgpu_driver_load_kms+0x15/0x100 [amdgpu]
[ +0.002744] amdgpu_pci_probe+0x147/0x370 [amdgpu]
[ +0.002522] local_pci_probe+0x40/0x80
[ +0.001896] work_for_cpu_fn+0x10/0x20
[ +0.001892] process_one_work+0x26e/0x5a0
[ +0.002029] worker_thread+0x1fd/0x3e0
[ +0.001890] ? process_one_work+0x5a0/0x5a0
[ +0.002115] kthread+0xea/0x110
[ +0.001618] ? kthread_complete_and_exit+0x20/0x20
[ +0.002422] ret_from_fork+0x1f/0x30
[ +0.001808]
[ +0.001103] irq event stamp: 59837
[ +0.001718] hardirqs last enabled at (59849): [] __up_console_sem+0x52/0x60
[ +0.004414] hardirqs last disabled at (59860): [] __up_console_sem+0x37/0x60
[ +0.004414] softirqs last enabled at (59654): [] irq_exit_rcu+0xd7/0x130
[ +0.004205] softirqs last disabled at (59649): [] irq_exit_rcu+0xd7/0x130
[ +0.004203] ---[ end trace 0000000000000000 ]---
## Which versions are affected by CVE-2023-54144?
## How do I fix CVE-2023-54144?
Apply the vendor's patch.
## Is CVE-2023-54144 being exploited?
There is no known exploitation of CVE-2023-54144 in the wild and no public exploit code.
## Fix prompt for AI coding agents
```text
Check this codebase for CVE-2023-54144 and fix it if it is affected.
What 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.
Exploitation: There is no known exploitation of CVE-2023-54144 in the wild and no public exploit code.
Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2023-54144/ (Markdown: https://insights.sbomify.com/CVE-2023-54144/index.md)
```
## Sources
- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54144
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54144
- OSV: https://osv.dev/vulnerability/CVE-2023-54144
---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54144/
Summaries are generated and may contain mistakes; the official description above is the record.