Answer in brief
CVE-2026-46173 records a Unknown severity vulnerability in exit: prevent preemption of oopsing TASK_DEAD task. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46173 records a Unknown severity vulnerability in exit: prevent preemption of oopsing TASK_DEAD task. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7f80a2fd7db9a55894fd841915236aca611291b5 <3d6fb8a7690c23e3213c4b008f64d89a44b98737 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <640b4c00fb0e2920327435f6176cbefc3c546165 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <6f49f94f3b11fe8bff1bf2a054143789e76aaf17 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <9756b3db5db6c2f5eccb32dddbd88eb4c54f575e || >=7f80a2fd7db9a55894fd841915236aca611291b5 <c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891 | 3d6fb8a7690c23e3213c4b008f64d89a44b98737, 640b4c00fb0e2920327435f6176cbefc3c546165, 7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34, 6f49f94f3b11fe8bff1bf2a054143789e76aaf17, 9756b3db5db6c2f5eccb32dddbd88eb4c54f575e, c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891 |
| Linux/Linuxgeneric | 5.17 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7f80a2fd7db9a55894fd841915236aca611291b5 <3d6fb8a7690c23e3213c4b008f64d89a44b98737 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <640b4c00fb0e2920327435f6176cbefc3c546165 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <6f49f94f3b11fe8bff1bf2a054143789e76aaf17 || >=7f80a2fd7db9a55894fd841915236aca611291b5 <9756b3db5db6c2f5eccb32dddbd88eb4c54f575e || >=7f80a2fd7db9a55894fd841915236aca611291b5 <c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891 | 3d6fb8a7690c23e3213c4b008f64d89a44b98737, 640b4c00fb0e2920327435f6176cbefc3c546165, 7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34, 6f49f94f3b11fe8bff1bf2a054143789e76aaf17, 9756b3db5db6c2f5eccb32dddbd88eb4c54f575e, c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891 |
| Linux/Linuxgeneric | 5.17 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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, resulting in various kinds of memory corruption. (This does not just affect "recursively oopsing" tasks; it is enough to oops once during task exit, for example in a file_operations::release handler)
Quoted source text, attributed separately from HOL analysis.