CVE-2026-98147

Analyzed Analyzed - Analysis Complete

Linux Kernel printk kthread_run Failure Handling Issue

Publication date: 2026-09-25

Last updated on: 2026-10-27

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-10-27

Generated

2026-11-08

AI Q&A

2026-09-25

EPSS Evaluated

2026-11-07

NVD

CVE-2026-98147

EUVD

EUVD-2026-86978

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.19 (inc) to 7.2.7 (exc)
linux	linux_kernel	7.3
linux	linux_kernel	7.3
linux	linux_kernel	From 6.13 (inc) to 6.18.57 (exc)
linux	linux_kernel	From 6.12 (inc) to 6.12.114 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-617	The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

Attack-Flow Graph

Executive Summary

This vulnerability involves the Linux kernel improperly handling kthread_run failures. The issue occurs because __kthread_create_on_node() returns -EINTR when interrupted by SIGKILL, but the code incorrectly uses WARN_ON() to catch kthread_run() failures, which can lead to unnecessary warnings.

Detection Guidance

This vulnerability is related to a Linux kernel issue where WARN_ON() is incorrectly used in kthread_run() failure handling. Detection requires checking kernel logs for WARN_ON messages related to kthread_run failures. Examine system logs with commands like 'dmesg | grep -i warn' or 'journalctl -k | grep -i warn' to identify such warnings.

Impact Analysis

This vulnerability may cause unnecessary kernel warnings when kthread_run fails due to SIGKILL signals. While not directly exploitable, it could clutter system logs and potentially obscure other important warnings.

Compliance Impact

This vulnerability does not directly impact compliance with standards like GDPR or HIPAA as it relates to kernel logging behavior and does not involve data exposure or privacy risks.

Mitigation Strategies

Apply the latest Linux kernel update that resolves this issue. Monitor kernel logs for kthread_run-related WARN_ON messages after updating. If warnings persist, check for SIGKILL signals interrupting kernel threads or review custom kernel modules that may trigger this behavior.

Hi! I’m here to help you understand CVE-2026-98147. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...