Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46173: exit: prevent preemption of oopsing TASK_DEAD task

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3d6fb8a7690c23e3213c4b008f64d89a44b98737, 640b4c00fb0e2920327435f6176cbefc3c546165, 6f49f94f3b11fe8bff1bf2a054143789e76aaf17; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3d6fb8a7690c23e3213c4b008f64d89a44b98737, 640b4c00fb0e2920327435f6176cbefc3c546165, 6f49f94f3b11fe8bff1bf2a054143789e76aaf17; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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)

Published
May 28, 2026
Updated
Nov 10, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46173

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.17affected
    • 7f80a2fd7db9a55894fd841915236aca611291b5 and later · before 3d6fb8a7690c23e3213c4b008f64d89a44b98737affected · git
    • 7f80a2fd7db9a55894fd841915236aca611291b5 and later · before 640b4c00fb0e2920327435f6176cbefc3c546165affected · git
    • 7f80a2fd7db9a55894fd841915236aca611291b5 and later · before 7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34affected · git
    • 7f80a2fd7db9a55894fd841915236aca611291b5 and later · before 6f49f94f3b11fe8bff1bf2a054143789e76aaf17affected · git
    • 7f80a2fd7db9a55894fd841915236aca611291b5 and later · before 9756b3db5db6c2f5eccb32dddbd88eb4c54f575eaffected · git
    • 7f80a2fd7db9a55894fd841915236aca611291b5 and later · before c1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891affected · git
    • before 5.17not affected · semver
    • 6.1.175 and later · up to and including 6.1.*not affected · semver
    • 6.6.140 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.26.1.el10_26.12.0-211.26.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46171May 28, 2026 · riscv: kvm: fix vector context allocation leak
    22Monitor
  • ← EarlierCVE-2026-46172May 28, 2026 · ipv6: xfrm6: release dst on error in xfrm6_rcv_encap()
    22Monitor
  • Later →CVE-2026-46174May 28, 2026 · x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3d6fb8a7690c23e3213c4b008f64d89a44b98737Vendor (CNA)
Linux Linux640b4c00fb0e2920327435f6176cbefc3c546165Vendor (CNA)
Linux Linux6f49f94f3b11fe8bff1bf2a054143789e76aaf17Vendor (CNA)
Linux Linux7b2800ba5f5f77a8ee7f4cbadb19cf1264597a34Vendor (CNA)
Linux Linux9756b3db5db6c2f5eccb32dddbd88eb4c54f575eVendor (CNA)
Linux Linuxc1fa0bb633e4a6b11e83ffc57fa5abe8ebb87891Vendor (CNA)
azl3 kernel 6.6.139.1-1 on Azure Linux 3.06.6.141.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.26.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.26.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+15

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records