Description
In the Linux kernel, the following vulnerability has been resolved:

sched_ext: Don't warn on NULL cgrp_moving_from in scx_cgroup_move_task()

A WARN fires when systemd's user manager writes "+cpu +memory +pids" to
its own subtree_control while a sched_ext scheduler is loaded:

WARNING: at kernel/sched/ext.c:3227 scx_cgroup_move_task+0xa8/0xb0
scx_cgroup_move_task+0xa8/0xb0
sched_move_task+0x134/0x290
cpu_cgroup_attach+0x39/0x70
cgroup_migrate_execute+0x37d/0x450
cgroup_update_dfl_csses+0x1e3/0x270
cgroup_subtree_control_write+0x3e7/0x440

scx_cgroup_can_attach() arms cgrp_moving_from only when a task's cpu
cgroup changes. It can still be NULL when scx_cgroup_move_task() runs,
through this sequence:

Step Result
--------------------------------- ----------------------------------
1. cpu enabled on cgroup G cpu css = A
2. cpu toggled off then on for G A killed, B created (same cgroup)
3. an exiting task keeps A alive migration skips it, A now stale
4. +memory migrates G stale A vs current B pulls cpu in
5. cpu attach runs for all tasks hits a live, cpu-unchanged task
6. scx_cgroup_move_task() on it cgrp_moving_from NULL -> WARN

The mismatch is that scx_cgroup_can_attach() keys on cgroup identity
while migration drives the move on css identity, so a NULL cgrp_moving_from
here is a legitimate css-only migration, not a missing prep.

The call is already gated on cgrp_moving_from, so just drop the warning.
ops.cgroup_prep_move() and ops.cgroup_move() stay paired.
Published: 2026-07-01
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability causes the Linux kernel to emit an unnecessary WARN message when the sched_ext scheduler handles a NULL cgrp_moving_from pointer during scx_cgroup_move_task(). This represents a CWE-476 (NULL Pointer Dereference) weakness, yet the code path guards against dereferencing, so the system continues to operate normally; the warning does not result in crashes, data corruption, or privilege escalation.

Affected Systems

All installations of the Linux kernel that include the sched_ext scheduler and have not yet incorporated the upstream commit that silences the warning are affected. This includes current mainline kernels and any distribution kernels that have opted to keep sched_ext and have not applied the patch.

Risk and Exploitability

The EPSS score is less than listed in CISA’s KEV catalog, showing a very low likelihood of exploitation. Based on the description, it is inferred that an attacker would need privileged access to manipulate cgroup settings, which would only trigger harmless log entries without any tangible benefit. The likely attack vector is local privileged manipulation of cgroup configurations; no known exploitation path exists beyond generating noise in the kernel log.

Generated by OpenCVE AI on July 21, 2026 at 14:48 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the upstream commit which suppresses the warning.
  • If a patch is not yet available for your distribution, disable the sched_ext scheduler by avoiding its use (e.g., use alternative schedulers such as CFS or RT) or by removing the CONFIG_SCHED_EXT configuration from the kernel.
  • Configure log filtering to ignore the specific WARN message so that it does not clutter logs or interfere with alerting systems. This may involve adding a syslog rule or adjusting the kernel warning filter.

Generated by OpenCVE AI on July 21, 2026 at 14:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 02 Jul 2026 01:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-398
CWE-665

Thu, 02 Jul 2026 00:15:00 +0000


Wed, 01 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-398
CWE-665

Wed, 01 Jul 2026 13:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: sched_ext: Don't warn on NULL cgrp_moving_from in scx_cgroup_move_task() A WARN fires when systemd's user manager writes "+cpu +memory +pids" to its own subtree_control while a sched_ext scheduler is loaded: WARNING: at kernel/sched/ext.c:3227 scx_cgroup_move_task+0xa8/0xb0 scx_cgroup_move_task+0xa8/0xb0 sched_move_task+0x134/0x290 cpu_cgroup_attach+0x39/0x70 cgroup_migrate_execute+0x37d/0x450 cgroup_update_dfl_csses+0x1e3/0x270 cgroup_subtree_control_write+0x3e7/0x440 scx_cgroup_can_attach() arms cgrp_moving_from only when a task's cpu cgroup changes. It can still be NULL when scx_cgroup_move_task() runs, through this sequence: Step Result --------------------------------- ---------------------------------- 1. cpu enabled on cgroup G cpu css = A 2. cpu toggled off then on for G A killed, B created (same cgroup) 3. an exiting task keeps A alive migration skips it, A now stale 4. +memory migrates G stale A vs current B pulls cpu in 5. cpu attach runs for all tasks hits a live, cpu-unchanged task 6. scx_cgroup_move_task() on it cgrp_moving_from NULL -> WARN The mismatch is that scx_cgroup_can_attach() keys on cgroup identity while migration drives the move on css identity, so a NULL cgrp_moving_from here is a legitimate css-only migration, not a missing prep. The call is already gated on cgrp_moving_from, so just drop the warning. ops.cgroup_prep_move() and ops.cgroup_move() stay paired.
Title sched_ext: Don't warn on NULL cgrp_moving_from in scx_cgroup_move_task()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-01T13:32:14.030Z

Reserved: 2026-06-09T07:44:35.398Z

Link: CVE-2026-53328

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity :

Publid Date: 2026-07-01T00:00:00Z

Links: CVE-2026-53328 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-21T15:00:09Z

Weaknesses