Skip to main content
VulnerabilityPublished Updated

CVE-2025-38522: Linux kernel · sched/ext: Prevent update_locked_rq() calls with NULL rq

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 13 Nov 2026, 20:18 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 16 Aug 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 13 Nov 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to prevent update_locked_rq() from being called with a NULL rq pointer. Users should apply the official kernel updates that include this patch once available. Since this is a kernel-level issue, upgrading to a fixed kernel version is the recommended remediation.

Description

CVE-2025-38522 is a medium severity vulnerability in the Linux kernel scheduler subsystem. It involves improper handling of the update_locked_rq() function when called with a NULL runqueue (rq) pointer. This flaw could lead to a kernel warning and potential instability due to unsafe use of __this_cpu_write() in a preemptible context. The issue has been resolved by ensuring update_locked_rq() is only invoked when rq is non-NULL.

References

Community reviews

Loading reviews…