Answer in brief
CVE-2026-98147 records a Unknown severity vulnerability in printk: Don't WARN on kthread_run failure.. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=76f258bf3f2aae570209319944703a92ac64e29e <4e676279798148382497d0e38c0bd51115e64be1 || >=76f258bf3f2aae570209319944703a92ac64e29e <72dd0ec09e7cc98ed58ddeac26575e5d1ab8a93d | 4e676279798148382497d0e38c0bd51115e64be1, 72dd0ec09e7cc98ed58ddeac26575e5d1ab8a93d |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.