cve.bz

CVE-2026-98147 linux linux kernel: Reachable Assertion

5.5 mediumEPSS 0.1%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-617 Reachable Assertion
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-98147 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98147?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98147?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98147 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98147

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98147](https://cve.bz/cve/badge/CVE-2026-98147.svg)](https://cve.bz/cve/CVE-2026-98147)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98147"><img src="https://cve.bz/cve/badge/CVE-2026-98147.svg" alt="CVE-2026-98147"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.12 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.114
Linux6.186.18.57
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-98147
Debian13linux6.12.115-2DEBIAN-CVE-2026-98147
Debian14linux7.2.7-1DEBIAN-CVE-2026-98147
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98147
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98147
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98147
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-98147
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-98147 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-98147 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-98147 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-98147 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-98147 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 moreno fix listedUBUNTU-CVE-2026-98147
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-98147
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-98147 USN-8959-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-98147
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-98147

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A flaw was found in the Linux kernel printk subsystem where the creation of the background printing thread was guarded by WARN_ON(), so a kthread_run() failure triggered a kernel warning. Because __kthread_create_on_node() legitimately returns -EINTR when the creating task receives SIGKILL, a local user who terminates the thread-creation process can provoke this warning. The impact on Red Hat products is rated LOW: under the default kernel configuration this only produces a warning message and stack trace in the system log, and a system crash (kernel panic) causing denial of service is possible only when the non-default panic_on_warn setting is enabled, which also makes the crash scenario dependent on precise timing of signal delivery. The kernel in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2 is affected, and the fix has been deferred for these streams given the low security impact and the warning-only nature of the flaw under default configurations; the residual risk is a log-only kernel warning on default installations and a potential panic only on systems configured with panic_on_warn. Earlier Red Hat Enterprise Linux versions and the OpenShift Container Platform RHEL CoreOS kernels are not affected because the vulnerable code is not present. The Red Hat impact rating of LOW is lower than the CVSS 3.1 base score of 5.5 (MODERATE) recorded for this flaw, reflecting that a denial of service requires a non-default kernel configuration.

Red Hat's mitigation

The exposure to a system crash can be mitigated by disabling the panic-on-warning behavior: run 'sysctl -w kernel.panic_on_warn=0' and make the setting persistent by adding 'kernel.panic_on_warn = 0' to /etc/sysctl.conf or another sysctl configuration file. With panic_on_warn disabled, triggering this flaw produces only a kernel warning message and stack trace in the system log rather than a panic. panic_on_warn is not enabled by default, so default installations are exposed only to the log-only warning. Updating to a kernel release that contains the upstream fix also resolves the issue.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98147.

References

Check your stackJSON