Количество 29
Количество 29
GHSA-mpr4-2mm3-rwm6
In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resu...
CVE-2026-46173
In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resultin...
CVE-2026-46173
In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resultin...
CVE-2026-46173
In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulti
CVE-2026-46173
exit: prevent preemption of oopsing TASK_DEAD task
CVE-2026-46173
In the Linux kernel, the following vulnerability has been resolved: e ...
SUSE-SU-2026:2863-1
Security update for the Linux Kernel RT (Live Patch 16 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2862-1
Security update for the Linux Kernel RT (Live Patch 15 for SUSE Linux Enterprise 15 SP7)
RLSA-2026:27288
Important: kernel security, bug fix, and enhancement update
RLSA-2026:27789
Important: kernel security, bug fix, and enhancement update
ELSA-2026-27789
ELSA-2026-27789: kernel security, bug fix, and enhancement update (IMPORTANT)
SUSE-SU-2026:2888-1
Security update for the Linux Kernel (Live Patch 52 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:2910-1
Security update for the Linux Kernel (Live Patch 46 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:2889-1
Security update for the Linux Kernel (Live Patch 44 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:2867-1
Security update for the Linux Kernel (Live Patch 41 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:2864-1
Security update for the Linux Kernel (Live Patch 45 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:2887-1
Security update for the Linux Kernel (Live Patch 12 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2855-1
Security update for the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2899-1
Security update for the Linux Kernel (Live Patch 27 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2890-1
Security update for the Linux Kernel (Live Patch 31 for SUSE Linux Enterprise 15 SP5)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-mpr4-2mm3-rwm6 In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resu... | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
CVE-2026-46173 In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resultin... | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
CVE-2026-46173 In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resultin... | CVSS3: 7 | 0% Низкий | 4 месяца назад | |
CVE-2026-46173 In the Linux kernel, the following vulnerability has been resolved: exit: prevent preemption of oopsing TASK_DEAD task When an already-exiting task oopses, make_task_dead() currently calls do_task_dead() with preemption enabled. That is forbidden: do_task_dead() calls __schedule(), which has a comment saying "WARNING: must be called with preemption disabled!". If an oopsing task is preempted in do_task_dead(), between becoming TASK_DEAD and entering the scheduler explicitly, bad things happen: finish_task_switch() assumes that once the scheduler has switched away from a TASK_DEAD task, the task can never run again and its stack is no longer needed; but that assumption apparently doesn't hold if the dead task was preempted (the SM_PREEMPT case). This means that the scheduler ends up repeatedly dropping references on the dead task's stack, which can lead to use-after-free or double-free of the entire task stack; in other words, two tasks can end up running on the same stack, resulti | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
CVE-2026-46173 exit: prevent preemption of oopsing TASK_DEAD task | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
CVE-2026-46173 In the Linux kernel, the following vulnerability has been resolved: e ... | CVSS3: 7.8 | 0% Низкий | 4 месяца назад | |
SUSE-SU-2026:2863-1 Security update for the Linux Kernel RT (Live Patch 16 for SUSE Linux Enterprise 15 SP7) | 2 месяца назад | |||
SUSE-SU-2026:2862-1 Security update for the Linux Kernel RT (Live Patch 15 for SUSE Linux Enterprise 15 SP7) | 2 месяца назад | |||
RLSA-2026:27288 Important: kernel security, bug fix, and enhancement update | 3 месяца назад | |||
RLSA-2026:27789 Important: kernel security, bug fix, and enhancement update | 3 месяца назад | |||
ELSA-2026-27789 ELSA-2026-27789: kernel security, bug fix, and enhancement update (IMPORTANT) | 3 месяца назад | |||
SUSE-SU-2026:2888-1 Security update for the Linux Kernel (Live Patch 52 for SUSE Linux Enterprise 15 SP4) | около 2 месяцев назад | |||
SUSE-SU-2026:2910-1 Security update for the Linux Kernel (Live Patch 46 for SUSE Linux Enterprise 15 SP4) | около 2 месяцев назад | |||
SUSE-SU-2026:2889-1 Security update for the Linux Kernel (Live Patch 44 for SUSE Linux Enterprise 15 SP4) | около 2 месяцев назад | |||
SUSE-SU-2026:2867-1 Security update for the Linux Kernel (Live Patch 41 for SUSE Linux Enterprise 15 SP4) | около 2 месяцев назад | |||
SUSE-SU-2026:2864-1 Security update for the Linux Kernel (Live Patch 45 for SUSE Linux Enterprise 15 SP4) | 2 месяца назад | |||
SUSE-SU-2026:2887-1 Security update for the Linux Kernel (Live Patch 12 for SUSE Linux Enterprise 15 SP7) | около 2 месяцев назад | |||
SUSE-SU-2026:2855-1 Security update for the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise 15 SP7) | 2 месяца назад | |||
SUSE-SU-2026:2899-1 Security update for the Linux Kernel (Live Patch 27 for SUSE Linux Enterprise 15 SP5) | около 2 месяцев назад | |||
SUSE-SU-2026:2890-1 Security update for the Linux Kernel (Live Patch 31 for SUSE Linux Enterprise 15 SP5) | около 2 месяцев назад |
Уязвимостей на страницу