CVE-2026-89518 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 7.2.4
- Linux Linux: fixed in 7.3
- Debian, openSUSE: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-89518 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89518?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89518?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-89518 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.19 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 7.2 | 7.2.4 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-89518 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-89518 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-89518 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-89518 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-89518 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-aws-7.0, linux-gcp-7.0 and 31 more | no fix listed | UBUNTU-CVE-2026-89518 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-89518 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime-6.14, linux-realtime-6.17 | no fix listed | UBUNTU-CVE-2026-89518 |
| openSUSE | Tumbleweed | kernel-source | 7.2.7-1.1 | openSUSE-SU-2026:11880-1 |
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. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat
Red Hat rates this Moderate.
A moderate-impact denial of service flaw was found in the Linux kernel's sched_ext scheduler framework. Under core scheduling, dispatch runs from within the core-wide pick and can target a sibling run queue (rq), so ops.dispatch() may execute on a CPU different from the dispatched rq's. Several sched_ext dispatch kfuncs incorrectly assumed the two always coincide: scx_dsq_move() could acquire the source rq lock while the dispatched rq lock was already held, resulting in a deadlock; scx_bpf_sub_dispatch() could dispatch this_rq() with a NULL sub_dispatch_prev; and finish_dispatch(), scx_bpf_dsq_reenq(), and scx_bpf_dsq_nr_queued() resolved SCX_DSQ_LOCAL to the executing CPU's local DSQ rather than the dispatched rq's. A local attacker able to run a sched_ext BPF scheduler on an affected kernel operating under core scheduling could trigger this deadlock and make the system unresponsive. Red Hat rated this flaw Moderate impact with a CVSS 3.1 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), affecting availability only. The vulnerable sched_ext dispatch kfunc code is not present in the kernel versions shipped in any Red Hat Enterprise Linux or Red Hat OpenShift (RHCOS) builds, so all Red Hat products are marked NOT AFFECTED for this CVE.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not 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-89518.