Answer in brief
CVE-2026-46154 records a Unknown severity vulnerability in sched_ext: Read scx_root under scx_cgroup_ops_rwsem in cgroup setters. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a5bd6ba30b3364354269b81ac55c2edca9a96d6d <ce9aaa3af445c391735c9d000c4db60dfd5640d4 || >=a5bd6ba30b3364354269b81ac55c2edca9a96d6d <0f54f6355575971673d8aac7da107ec4178e45bd || >=a5bd6ba30b3364354269b81ac55c2edca9a96d6d <80afd4c84bc8f5e80145ce35279f5ce53f6043db | ce9aaa3af445c391735c9d000c4db60dfd5640d4, 0f54f6355575971673d8aac7da107ec4178e45bd, 80afd4c84bc8f5e80145ce35279f5ce53f6043db |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Read scx_root under scx_cgroup_ops_rwsem in cgroup setters scx_group_set_{weight,idle,bandwidth}() cache scx_root before acquiring scx_cgroup_ops_rwsem, so the pointer can be stale by the time the op runs. If the loaded scheduler is disabled and freed (via RCU work) and another is enabled between the naked load and the rwsem acquire, the reader sees scx_cgroup_enabled=true (the new scheduler's) but dereferences the freed one - UAF on SCX_HAS_OP(sch, ...) / SCX_CALL_OP(sch, ...). scx_cgroup_enabled is toggled only under scx_cgroup_ops_rwsem write (scx_cgroup_{init,exit}), so reading scx_root inside the rwsem read section correlates @sch with the enabled snapshot.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-46154 records a Unknown severity vulnerability in sched_ext: Read scx_root under scx_cgroup_ops_rwsem in cgroup setters. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a5bd6ba30b3364354269b81ac55c2edca9a96d6d <ce9aaa3af445c391735c9d000c4db60dfd5640d4 || >=a5bd6ba30b3364354269b81ac55c2edca9a96d6d <0f54f6355575971673d8aac7da107ec4178e45bd || >=a5bd6ba30b3364354269b81ac55c2edca9a96d6d <80afd4c84bc8f5e80145ce35279f5ce53f6043db | ce9aaa3af445c391735c9d000c4db60dfd5640d4, 0f54f6355575971673d8aac7da107ec4178e45bd, 80afd4c84bc8f5e80145ce35279f5ce53f6043db |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: sched_ext: Read scx_root under scx_cgroup_ops_rwsem in cgroup setters scx_group_set_{weight,idle,bandwidth}() cache scx_root before acquiring scx_cgroup_ops_rwsem, so the pointer can be stale by the time the op runs. If the loaded scheduler is disabled and freed (via RCU work) and another is enabled between the naked load and the rwsem acquire, the reader sees scx_cgroup_enabled=true (the new scheduler's) but dereferences the freed one - UAF on SCX_HAS_OP(sch, ...) / SCX_CALL_OP(sch, ...). scx_cgroup_enabled is toggled only under scx_cgroup_ops_rwsem write (scx_cgroup_{init,exit}), so reading scx_root inside the rwsem read section correlates @sch with the enabled snapshot.
Quoted source text, attributed separately from HOL analysis.