CVE-2024-56583: sched/deadline: Fix warning in migrate_enable for boosted tasks
In the Linux kernel, the following vulnerability has been resolved:
sched/deadline: Fix warning in migrateenable 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 setupnewdlentity+0x13e/0x180 ... Call Trace: <TASK> ? showtraceloglvl+0x1c4/0x2df ? enqueuedlentity+0x631/0x6e0 ? setupnewdlentity+0x13e/0x180 ? warn+0x7e/0xd0 ? reportbug+0x11a/0x1a0 ? handlebug+0x3c/0x70 ? excinvalidop+0x14/0x70 ? asmexcinvalidop+0x16/0x20 enqueuedlentity+0x631/0x6e0 enqueuetaskdl+0x7d/0x120 dosetcpusallowed+0xe3/0x280 setcpusallowedptrlocked+0x140/0x1d0 setcpusallowedptr+0x54/0xa0 migrateenable+0x7e/0x150 rtspinunlock+0x1c/0x90 groupsendsiginfo+0xf7/0x1a0 ? killpidinfo+0x1f/0x1d0 killpidinfo+0x78/0x1d0 killprocinfo+0x5b/0x110 x64syskill+0x93/0xc0 dosyscall64+0x5c/0xf0 entrySYSCALL64afterhwframe+0x6e/0x76 RIP: 0033:0x7f0dab31f92b
This warning occurs because setcpusallowed dequeues and enqueues tasks with the ENQUEUERESTORE flag set. If the task is boosted, the warning is triggered. A boosted task already had its parameters set by rtmutexsetprio, and a new call to setupnewdlentity is unnecessary, hence the WARNON call.
Check if we are requeueing a boosted task and avoid calling setupnewdlentity if that's the case.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
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.