Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-89521

kernel: sched/core: Handle pick_task() releasing the rq lock

Overview

Published
11 Sep 2026
Modified
19 Oct 2026
High CVE
0 Registry packages
26 OS packages
3 Linux distributions
Yes Fix available

Description

In the Linux kernel, the following vulnerability has been resolved:

sched/core: Handle pick_task() releasing the rq lock

Core scheduling's pick_next_task() breaks when a ->pick_task()
implementation can release the rq lock. The selection state derived on entry
is only valid while the lock is held continuously. Once a pick can drop the
lock, an interleaving selection can invalidate all of it: the single-CPU
fast path can commit an uncookied pick although the core went cookied during
the release, and forceidle committed by the interleaving selection skews the
restarted pass's accounting.

Fix it by restarting the whole selection when a pick returns RETRY_TASK
after releasing the lock: a single restart point above the state derivation
replaces the per-loop restart labels, so a retry picks up state committed by
interleaving selections and accounts and resets forceidle like a fresh
selection would.

need_sync and fi_before latch across retries. Clock validity can't be
re-derived - there is no program-ordered way to tell whether the own and
core rq clocks are still updated after the lock was released, as other
lockers' pin cycles may or may not have invalidated them. When restarting,
clear core_clock_updated so that the sibling loop re-updates the core rq,
and update the own rq clock if invalidated.

Source: OX vulnerability database

Severity

7.3 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 22 fixes

debian 2 releases · 1 package

affected 1 fixed 1
linux
debian fixes for CVE-2026-89521
ReleasePackageFixed in
11 linux affected
14 linux 7.2.6-1

openSUSE 1 release · 1 package

fixed 1
kernel-devel
openSUSE fixes for CVE-2026-89521
ReleasePackageFixed inAdvisory
Tumbleweed kernel-devel +3 7.2.7-1.1 openSUSE-SU-2026:11880-1

ubuntu 2 releases · 19 packages

affected 2 fixed 17
linux-azure-7-0 linux-oracle-7-0 linux-aws-7-0 linux-gcp-7-0 linux-azure-fde-7-0 linux-riscv-7-0 +13
ubuntu fixes for CVE-2026-89521
ReleasePackageFixed in
24.04 linux-azure-7-0 +1 affected
24.04 linux-oracle-7-0 7.0.0-1016.18~24.04.1
24.04 linux-aws-7-0 7.0.0-1017.18~24.04.1
24.04 linux-gcp-7-0 7.0.0-1017.19~24.04.1
24.04 linux-azure-fde-7-0 7.0.0-1019.19~24.04.1
24.04 linux-riscv-7-0 7.0.0-42.42.1~24.04.1

13 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.