Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-89518

Vulnerability in Linux kernel (CVE-2026-89518)

Summary

Vulnerability in Linux kernel (CVE-2026-89518). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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

sched_ext: Fix this_rq() assumptions in dispatch kfuncs

Under core scheduling, dispatch runs from within the core-wide pick and can
target a sibling rq, so ops.dispatch() may execute on a CPU different from
the dispatched rq's. Several kfunc paths assumed the two always coincide:

  • scx_dsq_move() decided whether an rq lock is held by testing this_rq()'s
    rq flags and lock-danced accordingly. A dispatch for a sibling took the
    unlocked-context branch and acquired the source rq lock on top of the
    already held dispatched rq lock which could deadlock.

  • scx_bpf_sub_dispatch() dispatched this_rq() with its stashed
    sub_dispatch_prev, which is NULL when dispatching for a sibling.

  • finish_dispatch(), scx_bpf_dsq_reenq() and scx_bpf_dsq_nr_queued()
    resolved SCX_DSQ_LOCAL to this CPU's local DSQ rather than the dispatched
    rq's. The latter two are callable from other rq-locked operations too,
    where SCX_DSQ_LOCAL now likewise resolves to the op's rq. This changes
    behavior also without core scheduling, e.g. for ops.enqueue() running a
    remote wakeup on the waking CPU, and is intended: which CPU happens to
    execute an operation is incidental, the op's rq is what it is operating
    on, and the resolution now matches the insert side where SCX_DSQ_LOCAL
    dispatches land on the task's rq.

Use the rq tracked by scx_locked_rq(), which is set to the dispatched rq
around ops invocations and NULL in unlocked…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-89518 has been found in Linux kernel.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-89518" on the vendor's site.

CVE-2026-89518 (Linux kernel)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details