Cloudanix VulnDB

CVE-2026-98147

None

CVSS

—

EPSS

0.2%

Published

Sep 25, 2026

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A Linux kernel issue that could produce unneeded warnings during certain thread creation errors has been corrected.

Exploitation
Other
Attacker needs
Local User
Complexity
Theoretical
Impact
Other
Component
OS kernel
Class
Other
Remediation
Patch
Effort
Low
Patch risk
None

What it actually does

Inappropriate WARN_ON() usage on kthread_run() failure, which legitimately returns -EINTR on SIGKILL, risking spurious kernel warnings or oops handling.

Why it matters to the business

Unnecessary kernel log noise or potential stability alerts on Linux systems, increasing monitoring overhead with minimal operational disruption due to low exploitability.

How an attack unfolds

An attacker with local access sends SIGKILL during kthread creation attempts to trigger the WARN path, though no public exploits or threat actors are associated.

How to fix it

Apply the upstream kernel commit that removes WARN_ON from kthread_run failure handling; update to a patched kernel release once available.

How to confirm the fix worked

Inspect printk.c or equivalent source for absence of WARN_ON around kthread_run; verify no warning is emitted on controlled SIGKILL-induced failures in test environments.

Typical attack path

  1. Obtain local execution context on affected Linux kernel
  2. Force kthread_run failure via signal delivery
  3. Trigger WARN_ON condition

How to detect it

Search kernel logs for unexpected WARN messages tied to kthread creation; no specific post-exploitation artifacts are known.

What your security team should do

  • Monitor kernel update channels for the fix
  • Prioritize patching in environments with strict kernel warning policies
  • Review local kthread usage patterns for similar patterns

The record

In the Linux kernel, the following vulnerability has been resolved: printk: Don't WARN on kthread_run failure. Since __kthread_create_on_node() returns -EINTR upon SIGKILL, we should not use WARN_ON() in order to catch kthread_run() failure.

Affected packages

Ecosystem Package Introduced Fixed