CVE-2026-99524: Linux kernel · sched_ext: Fix use-after-free of a local reenq node left on an inactive cpu
Source GCVE Database
Not known to be exploited : upgrade to 43e1ef14a47257ebf7e3bb3ab9a6df9c6f817c5f or 0b5282963734a51b6dad978ccfe0fa22c4d4fb17 soon.
Data as of 19 Nov 2026, 16:49 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
The vulnerability has been resolved by ignoring reenq requests for inactive CPUs' local DSQs. No additional mitigation steps are indicated. Since the fix is published, applying the official kernel update containing this patch is recommended to remediate the issue.
Description
CVE-2026-99524 is a use-after-free vulnerability in the Linux kernel scheduler extension (sched_ext) related to handling of local deferred scheduler queue (DSQ) reenq nodes on inactive CPUs. The flaw occurs when reenq nodes remain linked on the runqueue (rq) list after a CPU goes offline, potentially leading to use-after-free conditions. The issue arises because reenq callbacks requested from a CPU that is going offline or already offline may never run, leaving nodes linked and later accessed after memory is freed. The fix involves ignoring reenq requests for inactive CPUs' local DSQs to prevent this condition.