GHSA-XC5V-WWW3-4JVJ
Vulnerability from github – Published: 2025-01-19 12:31 – Updated: 2025-01-19 12:31In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: wq_release signals dma_fence only when available
kfd_process_wq_release() signals eviction fence by dma_fence_signal() which wanrs if dma_fence is NULL.
kfd_process->ef is initialized by kfd_process_device_init_vm() through ioctl. That means the fence is NULL for a new created kfd_process, and close a kfd_process right after open it will trigger the warning.
This commit conditionally signals the eviction fence in kfd_process_wq_release() only when it is available.
[ 503.660882] WARNING: CPU: 0 PID: 9 at drivers/dma-buf/dma-fence.c:467 dma_fence_signal+0x74/0xa0 [ 503.782940] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu] [ 503.789640] RIP: 0010:dma_fence_signal+0x74/0xa0 [ 503.877620] Call Trace: [ 503.880066] [ 503.882168] ? __warn+0xcd/0x260 [ 503.885407] ? dma_fence_signal+0x74/0xa0 [ 503.889416] ? report_bug+0x288/0x2d0 [ 503.893089] ? handle_bug+0x53/0xa0 [ 503.896587] ? exc_invalid_op+0x14/0x50 [ 503.900424] ? asm_exc_invalid_op+0x16/0x20 [ 503.904616] ? dma_fence_signal+0x74/0xa0 [ 503.908626] kfd_process_wq_release+0x6b/0x370 [amdgpu] [ 503.914081] process_one_work+0x654/0x10a0 [ 503.918186] worker_thread+0x6c3/0xe70 [ 503.921943] ? srso_alias_return_thunk+0x5/0xfbef5 [ 503.926735] ? srso_alias_return_thunk+0x5/0xfbef5 [ 503.931527] ? __kthread_parkme+0x82/0x140 [ 503.935631] ? __pfx_worker_thread+0x10/0x10 [ 503.939904] kthread+0x2a8/0x380 [ 503.943132] ? __pfx_kthread+0x10/0x10 [ 503.946882] ret_from_fork+0x2d/0x70 [ 503.950458] ? __pfx_kthread+0x10/0x10 [ 503.954210] ret_from_fork_asm+0x1a/0x30 [ 503.958142] [ 503.960328] ---[ end trace 0000000000000000 ]---
(cherry picked from commit 2774ef7625adb5fb9e9265c26a59dca7b8fd171e)
{
"affected": [],
"aliases": [
"CVE-2024-57920"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-19T12:15:26Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: wq_release signals dma_fence only when available\n\nkfd_process_wq_release() signals eviction fence by\ndma_fence_signal() which wanrs if dma_fence\nis NULL.\n\nkfd_process-\u003eef is initialized by kfd_process_device_init_vm()\nthrough ioctl. That means the fence is NULL for a new\ncreated kfd_process, and close a kfd_process right\nafter open it will trigger the warning.\n\nThis commit conditionally signals the eviction fence\nin kfd_process_wq_release() only when it is available.\n\n[ 503.660882] WARNING: CPU: 0 PID: 9 at drivers/dma-buf/dma-fence.c:467 dma_fence_signal+0x74/0xa0\n[ 503.782940] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[ 503.789640] RIP: 0010:dma_fence_signal+0x74/0xa0\n[ 503.877620] Call Trace:\n[ 503.880066] \u003cTASK\u003e\n[ 503.882168] ? __warn+0xcd/0x260\n[ 503.885407] ? dma_fence_signal+0x74/0xa0\n[ 503.889416] ? report_bug+0x288/0x2d0\n[ 503.893089] ? handle_bug+0x53/0xa0\n[ 503.896587] ? exc_invalid_op+0x14/0x50\n[ 503.900424] ? asm_exc_invalid_op+0x16/0x20\n[ 503.904616] ? dma_fence_signal+0x74/0xa0\n[ 503.908626] kfd_process_wq_release+0x6b/0x370 [amdgpu]\n[ 503.914081] process_one_work+0x654/0x10a0\n[ 503.918186] worker_thread+0x6c3/0xe70\n[ 503.921943] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 503.926735] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 503.931527] ? __kthread_parkme+0x82/0x140\n[ 503.935631] ? __pfx_worker_thread+0x10/0x10\n[ 503.939904] kthread+0x2a8/0x380\n[ 503.943132] ? __pfx_kthread+0x10/0x10\n[ 503.946882] ret_from_fork+0x2d/0x70\n[ 503.950458] ? __pfx_kthread+0x10/0x10\n[ 503.954210] ret_from_fork_asm+0x1a/0x30\n[ 503.958142] \u003c/TASK\u003e\n[ 503.960328] ---[ end trace 0000000000000000 ]---\n\n(cherry picked from commit 2774ef7625adb5fb9e9265c26a59dca7b8fd171e)",
"id": "GHSA-xc5v-www3-4jvj",
"modified": "2025-01-19T12:31:26Z",
"published": "2025-01-19T12:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-57920"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a993d319aebb7cce8a10c6e685344b7c2ad5c4c2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c8243def299793ac6c85fdc1086089c800c1051a"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.