Linux Kernel up to 7.1-rc3 exit make_task_dead use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.7$5k-$25k0.00

Summaryinfo

A vulnerability categorized as critical has been discovered in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc3. Affected is the function make_task_dead of the component exit. Executing a manipulation can lead to use after free. This vulnerability is registered as CVE-2026-46173. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.139/6.12.87/6.18.29/7.0.6/7.1-rc3. It has been declared as critical. This vulnerability affects the function make_task_dead of the component exit. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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)

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-46173 since 05/13/2026. The exploitation appears to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/21/2026).

The vulnerability scanner Nessus provides a plugin with the ID 321829 (RHEL 10 : kernel (RHSA-2026:27288)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc4 eliminates this vulnerability. Applying the patch 640b4c00fb0e2920327435f6176cbefc3c546165/7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34/6f49f94f3b11fe8bff1bf2a054143789e76aaf17/9756b3db5db6c2f5eccb32dddbd88eb4c54f575e/c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (321829) and EUVD (EUVD-2026-32800). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.9
VulDB Meta Temp Score: 7.7

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector (Linux): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 321829
Nessus Name: RHEL 10 : kernel (RHSA-2026:27288)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc4
Patch: 640b4c00fb0e2920327435f6176cbefc3c546165/7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34/6f49f94f3b11fe8bff1bf2a054143789e76aaf17/9756b3db5db6c2f5eccb32dddbd88eb4c54f575e/c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891

Timelineinfo

05/13/2026 CVE reserved
05/28/2026 +15 days Advisory disclosed
05/28/2026 +0 days VulDB entry created
06/21/2026 +24 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46173 (🔒)
GCVE (CVE): GCVE-0-2026-46173
GCVE (VulDB): GCVE-100-366640
EUVD: 🔒

Entryinfo

Created: 05/28/2026 13:24
Updated: 06/21/2026 18:15
Changes: 05/28/2026 13:24 (59), 05/31/2026 15:43 (1), 06/11/2026 00:46 (11), 06/21/2026 18:15 (2)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!