LiveActive security incident?Get immediate response
CVE Record

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

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Validate prev_cpu in scx_bpf_select_cpu_dfl() If a BPF scheduler provides an invalid CPU (outside the nr_cpu_ids range) as prev_cpu to scx_bpf_select_cpu_dfl() it can cause a kernel crash. To prevent this, validate prev_cpu in scx_bpf_select_cpu_dfl() and trigger an scx error if an invalid CPU is specified.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A locally authorized user who can influence a Linux BPF scheduler may supply an invalid CPU identifier and crash the kernel. This can disrupt affected servers or workloads. The supplied description confirms a crash, but does not establish remote exploitation or arbitrary code execution.

Executive priority

Treat as a high-priority stability issue on multi-user or sched_ext-enabled Linux systems. Accelerate patching where untrusted local users can influence BPF schedulers. Other systems should follow normal kernel maintenance after confirming vendor applicability.

Technical view

CVE-2025-21965 affects sched_ext handling in scx_bpf_select_cpu_dfl(). An invalid prev_cpu outside nr_cpu_ids was not validated, allowing a BPF scheduler to trigger a kernel crash. The correction validates prev_cpu and raises an sched_ext error. CVSS 3.1 is 7.8 with local access and low privileges required.

Likely exposure

Exposure is most plausible where affected Linux kernels run sched_ext BPF schedulers and lower-privileged users can influence them. The bundle lists affected 6.12, 6.12.20, 6.13.8, and 6.14 entries, but does not provide reliable distribution-specific package mappings.

Exploitation context

The supplied record is not in KEV and contains no evidence of active exploitation. Exploitation requires local access, low privileges, and a BPF scheduler capable of passing an invalid CPU value. The documented result is a kernel crash.

Researcher notes

The source establishes missing bounds validation and a kernel-crash outcome. Although the CVSS vector assigns high confidentiality, integrity, and availability impacts, the supplied narrative does not demonstrate data disclosure, privilege escalation, or code execution. No CWE or public exploitation evidence is provided.

Mitigation direction

  • Install a vendor-supported kernel containing the referenced prev_cpu validation fix.
  • Check distribution security guidance for package-specific fixed versions and backports.
  • Until patched, restrict who can load, configure, or control BPF schedulers.
  • Prioritize exposed multi-user systems and hosts using sched_ext scheduling.

Validation and detection

  • Inventory kernel versions and distribution package revisions across potentially affected hosts.
  • Confirm whether vendor packages include one of the referenced fixes or an equivalent backport.
  • Identify systems where sched_ext and custom BPF schedulers are enabled or used.
  • After updating, verify the fixed kernel is running following any required reboot.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-21965 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-21965Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf0e1a0643a59bf1f922fa209cec86a170b784f3f, f0e1a0643a59bf1f922fa209cec86a170b784f3f, f0e1a0643a59bf1f922fa209cec86a170b784f3funaffected
LinuxLinux6.12, 0, 6.12.20, 6.13.8, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.