<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T16:13:40.641791+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38522</id>
    <title>CVE-2025-38522 — sched/ext: Prevent update_locked_rq() calls with NULL rq</title>
    <updated>2026-10-02T16:13:40.658105+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>sched/ext: Prevent update_locked_rq() calls with NULL rq</p>
<p>Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL
in the SCX_CALL_OP and SCX_CALL_OP_RET macros.</p>
<p>Previously, calling update_locked_rq(NULL) with preemption enabled could
trigger the following warning:</p>
<p>BUG: using __this_cpu_write() in preemptible [00000000]</p>
<p>This happens because __this_cpu_write() is unsafe to use in preemptible
context.</p>
<p>rq is NULL when an ops invoked from an unlocked context. In such cases, we
don't need to store any rq, since the value should already be NULL
(unlocked). Ensure that update_locked_rq() is only called when rq is
non-NULL, preventing calling __this_cpu_write() on preemptible context.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38522"/>
  </entry>
</feed>
