- Vulnerability/
- CVE-2024-57888
CVE-2024-57888: workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker
First published: Wed Jan 15 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker After commit 746ae46c1113 ("drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM") amdgpu started seeing the following warning: [ ] workqueue: WQ_MEM_RECLAIM sdma0:drm_sched_run_job_work [gpu_sched] is flushing !WQ_MEM_RECLAIM events:amdgpu_device_delay_enable_gfx_off [amdgpu] ... [ ] Workqueue: sdma0 drm_sched_run_job_work [gpu_sched] ... [ ] Call Trace: [ ] <TASK> ... [ ] ? check_flush_dependency+0xf5/0x110 ... [ ] cancel_delayed_work_sync+0x6e/0x80 [ ] amdgpu_gfx_off_ctrl+0xab/0x140 [amdgpu] [ ] amdgpu_ring_alloc+0x40/0x50 [amdgpu] [ ] amdgpu_ib_schedule+0xf4/0x810 [amdgpu] [ ] ? drm_sched_run_job_work+0x22c/0x430 [gpu_sched] [ ] amdgpu_job_run+0xaa/0x1f0 [amdgpu] [ ] drm_sched_run_job_work+0x257/0x430 [gpu_sched] [ ] process_one_work+0x217/0x720 ... [ ] </TASK> The intent of the verifcation done in check_flush_depedency is to ensure forward progress during memory reclaim, by flagging cases when either a memory reclaim process, or a memory reclaim work item is flushed from a context not marked as memory reclaim safe. This is correct when flushing, but when called from the cancel(_delayed)_work_sync() paths it is a false positive because work is either already running, or will not be running at all. Therefore cancelling it is safe and we can relax the warning criteria by letting the helper know of the calling context. References: 746ae46c1113 ("drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM")
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Kernel-devel | ||
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.128-1 | 6.12.20-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/1fd2a57dcb4de3cb40844a29c71b5d7b46a84334
- https://git.kernel.org/stable/c/de35994ecd2dd6148ab5a6c5050a1670a04dec77
- https://git.kernel.org/stable/c/ffb231471a407c96e114070bf828cd2378fdf431
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57888
- https://nvd.nist.gov/vuln/detail/CVE-2024-57888
- https://launchpad.net/bugs/cve/CVE-2024-57888
- https://security-tracker.debian.org/tracker/CVE-2024-57888
- https://ubuntu.com/security/CVE-2024-57888
- https://git.kernel.org/linus/de35994ecd2dd6148ab5a6c5050a1670a04dec77
Frequently Asked Questions
What is the severity of CVE-2024-57888?
CVE-2024-57888 has not been assigned a severity score yet.
How do I fix CVE-2024-57888?
To fix CVE-2024-57888, update the Linux kernel to the latest patched version.
What systems are affected by CVE-2024-57888?
CVE-2024-57888 affects systems running vulnerable versions of the Linux kernel.
What type of vulnerability is CVE-2024-57888?
CVE-2024-57888 is a workqueue cancellation warning issue in the Linux kernel.
Is there a workaround for CVE-2024-57888?
As of now, there are no known workarounds for CVE-2024-57888 other than applying the kernel update.
- agent/title
- agent/severity
- agent/type
- agent/first-publish-date
- agent/author
- collector/nvd-api
- source/NVD
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/red hat kernel-devel
- package-manager/debian