- Vulnerability/
- CVE-2024-56583
CVE-2024-56583: sched/deadline: Fix warning in migrate_enable for boosted tasks
First published: Fri Dec 27 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix warning in migrate_enable for boosted tasks When running the following command: while true; do stress-ng --cyclic 30 --timeout 30s --minimize --quiet done a warning is eventually triggered: WARNING: CPU: 43 PID: 2848 at kernel/sched/deadline.c:794 setup_new_dl_entity+0x13e/0x180 ... Call Trace: <TASK> ? show_trace_log_lvl+0x1c4/0x2df ? enqueue_dl_entity+0x631/0x6e0 ? setup_new_dl_entity+0x13e/0x180 ? __warn+0x7e/0xd0 ? report_bug+0x11a/0x1a0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 enqueue_dl_entity+0x631/0x6e0 enqueue_task_dl+0x7d/0x120 __do_set_cpus_allowed+0xe3/0x280 __set_cpus_allowed_ptr_locked+0x140/0x1d0 __set_cpus_allowed_ptr+0x54/0xa0 migrate_enable+0x7e/0x150 rt_spin_unlock+0x1c/0x90 group_send_sig_info+0xf7/0x1a0 ? kill_pid_info+0x1f/0x1d0 kill_pid_info+0x78/0x1d0 kill_proc_info+0x5b/0x110 __x64_sys_kill+0x93/0xc0 do_syscall_64+0x5c/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7f0dab31f92b This warning occurs because set_cpus_allowed dequeues and enqueues tasks with the ENQUEUE_RESTORE flag set. If the task is boosted, the warning is triggered. A boosted task already had its parameters set by rt_mutex_setprio, and a new call to setup_new_dl_entity is unnecessary, hence the WARN_ON call. Check if we are requeueing a boosted task and avoid calling setup_new_dl_entity if that's the case.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| 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/0664e2c311b9fa43b33e3e81429cd0c2d7f9c638
- https://git.kernel.org/stable/c/b600d30402854415aa57548a6b53dc6478f65517
- https://git.kernel.org/stable/c/e41074904d9ed3fe582d6e544c77b40c22043c82
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56583
- https://nvd.nist.gov/vuln/detail/CVE-2024-56583
- https://launchpad.net/bugs/cve/CVE-2024-56583
- https://security-tracker.debian.org/tracker/CVE-2024-56583
- https://ubuntu.com/security/CVE-2024-56583
- https://git.kernel.org/linus/0664e2c311b9fa43b33e3e81429cd0c2d7f9c638
Frequently Asked Questions
What is the severity of CVE-2024-56583?
The severity of CVE-2024-56583 is considered moderate, as it involves a warning condition that may affect scheduled tasks.
How do I fix CVE-2024-56583?
To fix CVE-2024-56583, update to the latest version of the Linux kernel that includes the patch addressing this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-56583?
CVE-2024-56583 affects specific versions of the Linux kernel prior to the vulnerability being patched.
What impact does CVE-2024-56583 have on system performance?
CVE-2024-56583 can lead to warning messages when running certain stress tests, potentially affecting system performance during these operations.
Is there a workaround for CVE-2024-56583?
Currently, there is no official workaround for CVE-2024-56583; the recommended approach is to apply the kernel update as soon as possible.
- agent/title
- agent/severity
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/author
- 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/linux kernel
- package-manager/debian