Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53215: sched/fair: Don't balance task to its current running CPU

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0dd37d6dd33a9c23351e6115ae8cdac7863bc7de, 32d937f94b7805d4c9028b8727a7d6241547da54, 34eb902050d473bb2befa15714fb1d30a0991c15.

Low priority for now. Upgrade to Linux Linux 0dd37d6dd33a9c23351e6115ae8cdac7863bc7de, 32d937f94b7805d4c9028b8727a7d6241547da54, 34eb902050d473bb2befa15714fb1d30a0991c15 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: sched/fair: Don't balance task to its current running CPU We've run into the case that the balancer tries to balance a migration disabled task and trigger the warning in set_task_cpu() like below: ------------[ cut here ]------------ WARNING: CPU: 7 PID: 0 at kernel/sched/core.c:3115 set_task_cpu+0x188/0x240 Modules linked in: hclgevf xt_CHECKSUM ipt_REJECT nf_reject_ipv4 <...snip> CPU: 7 PID: 0 Comm: swapper/7 Kdump: loaded Tainted: G O 6.1.0-rc4+ #1 Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V5.B221.01 12/09/2021 pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : set_task_cpu+0x188/0x240 lr : load_balance+0x5d0/0xc60 sp : ffff80000803bc70 x29: ffff80000803bc70 x28: ffff004089e190e8 x27: ffff004089e19040 x26: ffff007effcabc38 x25: 0000000000000000 x24: 0000000000000001 x23: ffff80000803be84 x22: 000000000000000c x21: ffffb093e79e2a78 x20: 000000000000000c x19: ffff004089e19040 x18: 0000000000000000 x17: 0000000000001fad x16: 0000000000000030 x15: 0000000000000000 x14: 0000000000000003 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000001 x10: 0000000000000400 x9 : ffffb093e4cee530 x8 : 00000000fffffffe x7 : 0000000000ce168a x6 : 000000000000013e x5 : 00000000ffffffe1 x4 : 0000000000000001 x3 : 0000000000000b2a x2 : 0000000000000b2a x1 : ffffb093e6d6c510 x0 : 0000000000000001 Call trace: set_task_cpu+0x188/0x240 load_balance+0x5d0/0xc60 rebalance_domains+0x26c/0x380 _nohz_idle_balance.isra.0+0x1e0/0x370 run_rebalance_domains+0x6c/0x80 __do_softirq+0x128/0x3d8 ____do_softirq+0x18/0x24 call_on_irq_stack+0x2c/0x38 do_softirq_own_stack+0x24/0x3c __irq_exit_rcu+0xcc/0xf4 irq_exit_rcu+0x18/0x24 el1_interrupt+0x4c/0xe4 el1h_64_irq_handler+0x18/0x2c el1h_64_irq+0x74/0x78 arch_cpu_idle+0x18/0x4c default_idle_call+0x58/0x194 do_idle+0x244/0x2b0 cpu_startup_entry+0x30/0x3c secondary_start_kernel+0x14c/0x190 __secondary_switched+0xb0/0xb4 ---[ end trace 0000000000000000 ]--- Further investigation shows that the warning is superfluous, the migration disabled task is just going to be migrated to its current running CPU. This is because that on load balance if the dst_cpu is not allowed by the task, we'll re-select a new_dst_cpu as a candidate. If no task can be balanced to dst_cpu we'll try to balance the task to the new_dst_cpu instead. In this case when the migration disabled task is not on CPU it only allows to run on its current CPU, load balance will select its current CPU as new_dst_cpu and later triggers the warning above. The new_dst_cpu is chosen from the env->dst_grpmask. Currently it contains CPUs in sched_group_span() and if we have overlapped groups it's possible to run into this case. This patch makes env->dst_grpmask of group_balance_mask() which exclude any CPUs from the busiest group and solve the issue. For balancing in a domain with no overlapped groups the behaviour keeps same as before.

Published
Sep 15, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53215

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.6affected
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before 32d937f94b7805d4c9028b8727a7d6241547da54affected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before a5286f4655ce2fa28f477c0b957ea7f323fe2fabaffected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before cec1857b1ea5cc3ea2b600564f1c95d1a6f27ad1affected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before 6b0c79aa33075b34c3cdcea4132c0afb3fc42d68affected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before 3cb43222bab8ab328fc91ed30899b3df2efbccfdaffected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before 78a5f711efceb37e32c48cd6b40addb671fea9ccaffected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before 34eb902050d473bb2befa15714fb1d30a0991c15affected · git
    • 88b8dac0a14c511ff41486b83a8c3d688936eec0 and later · before 0dd37d6dd33a9c23351e6115ae8cdac7863bc7deaffected · git
    • before 3.6not affected · semver
Affected versions · NVD (7)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.14.322
  • linux linux kernel4.15 and later · before 4.19.291
  • linux linux kernel4.20 and later · before 5.4.251
  • linux linux kernel5.5 and later · before 5.10.188
  • linux linux kernel5.11 and later · before 5.15.150
  • linux linux kernel5.16 and later · before 6.1.42
  • linux linux kernel6.2 and later · before 6.4.7

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53213Sep 15, 2025 · wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies()
    28Monitor
  • ← EarlierCVE-2023-53214Sep 15, 2025 · f2fs: fix to avoid potential memory corruption in __update_iostat_latency()
    31Monitor
  • Later →CVE-2023-53216Sep 15, 2025 · arm64: efi: Make efi_rt_lock a raw_spinlock
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0dd37d6dd33a9c23351e6115ae8cdac7863bc7deVendor (CNA)
Linux Linux32d937f94b7805d4c9028b8727a7d6241547da54Vendor (CNA)
Linux Linux34eb902050d473bb2befa15714fb1d30a0991c15Vendor (CNA)
Linux Linux3cb43222bab8ab328fc91ed30899b3df2efbccfdVendor (CNA)
Linux Linux6b0c79aa33075b34c3cdcea4132c0afb3fc42d68Vendor (CNA)
Linux Linux78a5f711efceb37e32c48cd6b40addb671fea9ccVendor (CNA)
Linux Linuxa5286f4655ce2fa28f477c0b957ea7f323fe2fabVendor (CNA)
Linux Linuxcec1857b1ea5cc3ea2b600564f1c95d1a6f27ad1Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records