Kernel warning via current-CPU scheduler rebalance
Published Sep 15, 2025 · Updated Sep 15, 2025
Improper task balancing in Linux 3.6 through 6.4 allows local users to trigger a kernel warning during scheduler load balancing. load_balance selects a migration-disabled task's current CPU from env->dst_grpmask when the requested destination is disallowed, then passes that unchanged placement to set_task_cpu. The condition requires overlapping scheduler groups and a migration-disabled task that is not running; the warning is superfluous, and no additional consequence is demonstrated.
Summary
What happened
Improper task balancing in Linux 3.6 through 6.4 allows local users to trigger a kernel warning during scheduler load balancing. load_balance selects a migration-disabled task's current CPU from env->dst_grpmask when the requested destination is disallowed, then passes that unchanged placement to set_task_cpu. The condition requires overlapping scheduler groups and a migration-disabled task that is not running; the warning is superfluous, and no additional consequence is demonstrated.
The record
- CVE
- CVE-2023-53215
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0dd37d6dd33a9c23351e6115ae8cdac7863bc7de
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32d937f94b7805d4c9028b8727a7d6241547da54
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <34eb902050d473bb2befa15714fb1d30a0991c15
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3cb43222bab8ab328fc91ed30899b3df2efbccfd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6b0c79aa33075b34c3cdcea4132c0afb3fc42d68
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <78a5f711efceb37e32c48cd6b40addb671fea9cc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a5286f4655ce2fa28f477c0b957ea7f323fe2fab
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cec1857b1ea5cc3ea2b600564f1c95d1a6f27ad1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo