CVE-2026-46173

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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)

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.7%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

exit: prevent preemption of oopsing TASK_DEAD task - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891
generic

exit: prevent preemption of oopsing TASK_DEAD task - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9756b3db5db6c2f5eccb32dddbd88eb4c54f575e
generic

exit: prevent preemption of oopsing TASK_DEAD task - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34
generic

exit: prevent preemption of oopsing TASK_DEAD task - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f49f94f3b11fe8bff1bf2a054143789e76aaf17
generic

exit: prevent preemption of oopsing TASK_DEAD task - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/640b4c00fb0e2920327435f6176cbefc3c546165
generic

exit: prevent preemption of oopsing TASK_DEAD task - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d6fb8a7690c23e3213c4b008f64d89a44b98737

Vendor Advisories for CVE-2026-46173(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-55.88.1.el10_02026-07-14redhat
redhatkernel-0:5.14.0-570.125.1.el9_62026-07-01redhat
redhatkernel-0:5.14.0-284.178.1.el9_22026-07-01redhat
redhatkernel-rt-0:5.14.0-284.178.1.rt14.463.el9_22026-07-01redhat
redhatkernel-0:5.14.0-687.17.1.el9_82026-06-22redhat
redhatkernel-0:5.14.0-427.134.1.el9_42026-06-22redhat
redhatkernel-0:6.12.0-211.26.1.el10_22026-06-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 10:21 UTCVendor advisory
  9. 2026-07-16 10:21 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 21:16 UTCVendor advisory
  15. 2026-07-11 21:16 UTCGHSA enrichment
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 18:24 UTCVendor advisory
  19. 2026-07-08 18:24 UTCGHSA enrichment
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 75 more
  1. 2026-07-02 14:14 UTCVendor advisory
  2. 2026-07-02 14:14 UTCGHSA enrichment
  3. 2026-07-01 16:51 UTCVendor advisory
  4. 2026-07-01 16:50 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 03:07 UTCVendor advisory
  7. 2026-07-01 03:07 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 03:08 UTCVendor advisory
  10. 2026-06-30 03:08 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 13:45 UTCVendor advisory
  14. 2026-06-29 13:45 UTCGHSA enrichment
  15. 2026-06-28 21:30 UTCVendor advisory
  16. 2026-06-28 21:30 UTCGHSA enrichment
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 08:20 UTCVendor advisory
  19. 2026-06-28 08:20 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 19:10 UTCVendor advisory
  23. 2026-06-27 19:10 UTCGHSA enrichment
  24. 2026-06-27 06:01 UTCVendor advisory
  25. 2026-06-27 06:01 UTCGHSA enrichment
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-26 16:51 UTCVendor advisory
  28. 2026-06-26 16:51 UTCGHSA enrichment
  29. 2026-06-26 02:05 UTCVendor advisory
  30. 2026-06-26 02:05 UTCGHSA enrichment
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-25 11:54 UTCVendor advisory
  33. 2026-06-25 11:54 UTCGHSA enrichment
  34. 2026-06-24 22:45 UTCVendor advisory
  35. 2026-06-24 22:45 UTCGHSA enrichment
  36. 2026-06-24 14:05 UTCEPSS rescore
  37. 2026-06-23 21:33 UTCEPSS rescore
  38. 2026-06-23 21:33 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-21 14:56 UTCEPSS rescore
  42. 2026-06-21 14:56 UTCEPSS rescore
  43. 2026-06-19 19:26 UTCEPSS rescore
  44. 2026-06-19 19:26 UTCEPSS rescore
  45. 2026-06-17 18:14 UTCGHSA enrichment
  46. 2026-06-17 17:53 UTCEPSS rescore
  47. 2026-06-17 04:53 UTCGHSA enrichment
  48. 2026-06-16 17:52 UTCEPSS rescore
  49. 2026-06-16 15:43 UTCVendor advisory
  50. 2026-06-16 15:42 UTCGHSA enrichment
  51. 2026-06-16 02:10 UTCVendor advisory
  52. 2026-06-16 02:10 UTCGHSA enrichment
  53. 2026-06-15 17:49 UTCEPSS rescore
  54. 2026-06-15 13:02 UTCVendor advisory
  55. 2026-06-15 13:02 UTCGHSA enrichment
  56. 2026-06-14 21:54 UTCVendor advisory
  57. 2026-06-14 21:54 UTCGHSA enrichment
  58. 2026-06-14 08:45 UTCVendor advisory
  59. 2026-06-14 08:45 UTCGHSA enrichment
  60. 2026-06-13 23:00 UTCEPSS rescore
  61. 2026-06-13 19:32 UTCGHSA enrichment
  62. 2026-06-13 03:57 UTCVendor advisory
  63. 2026-06-13 03:57 UTCGHSA enrichment
  64. 2026-06-12 23:12 UTCEPSS rescore
  65. 2026-06-12 23:12 UTCEPSS rescore
  66. 2026-06-12 14:47 UTCVendor advisory
  67. 2026-06-12 14:47 UTCGHSA enrichment
  68. 2026-06-12 01:37 UTCVendor advisory
  69. 2026-06-12 01:37 UTCGHSA enrichment
  70. 2026-06-11 14:00 UTCEPSS rescore
  71. 2026-06-11 12:28 UTCVendor advisory
  72. 2026-06-11 12:28 UTCGHSA enrichment
  73. 2026-06-10 23:19 UTCVendor advisory
  74. 2026-06-10 23:19 UTCGHSA enrichment
  75. 2026-06-10 22:18 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46173?
CVE-2026-46173 is a high vulnerability published on May 28, 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, maketaskdead() currently calls dotaskdead() with preemption enabled. That is forbidden: dotaskdead() calls schedule(), which has a comment…
When was CVE-2026-46173 disclosed?
CVE-2026-46173 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46173 actively exploited?
CVE-2026-46173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46173?
CVE-2026-46173 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46173, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46173

Explore →

Is Your Infrastructure Affected by CVE-2026-46173?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs