Skip to main content
VulnerabilityPublished Updated

CVE-2025-21965: Linux kernel · sched_ext: Validate prev_cpu in scx_bpf_select_cpu_dfl()

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 29 Oct 2026, 23:34 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel by validating the prev_cpu parameter in scx_bpf_select_cpu_dfl(). Users should apply the official kernel updates that include this validation.

Description

A vulnerability in the Linux kernel's sched_ext component allows a BPF scheduler to cause a kernel crash by providing an invalid CPU identifier as prev_cpu to the function scx_bpf_select_cpu_dfl(). This issue has been resolved by adding validation of the prev_cpu parameter to prevent invalid CPU values.

References

Community reviews

Loading reviews…