CVE-2026-99524: Linux kernel · sched_ext: Fix use-after-free of a local reenq node left on an inactive cpu
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to 43e1ef14a47257ebf7e3bb3ab9a6df9c6f817c5f or 0b5282963734a51b6dad978ccfe0fa22c4d4fb17 soon.
Data as of 19 Nov 2026, 15:20 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 43e1ef14a47257ebf7e3bb3ab9a6df9c6f817c5f, 0b5282963734a51b6dad978ccfe0fa22c4d4fb17
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
Upgrade Linux kernel to 43e1ef14a47257ebf7e3bb3ab9a6df9c6f817c5f or 0b5282963734a51b6dad978ccfe0fa22c4d4fb17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the specified commits. Users should update their Linux kernel to a version including these fixes to remediate the vulnerability. No additional mitigation steps are indicated.
Description
CVE-2026-99524 is a use-after-free vulnerability in the Linux kernel scheduler extension (sched_ext) related to handling of local deferred scheduling queue (DSQ) reenqueue nodes on inactive CPUs. The flaw occurs when a reenq node remains linked on a runqueue (rq) list after the CPU goes offline, potentially leading to freeing memory that is still referenced. The issue is fixed by ignoring reenqs of an inactive CPU's local DSQ.