CVE-2023-53215

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-59869 (ENISA EUVD) · GHSA-g72f-mhc5-x52v (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2025

Last Modified

January 14, 2026

Advisory Details (8)

Auto-updated Oct 11, 2026
Patch available.
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cec1857b1ea5cc3ea2b600564f1c95d1a6f27ad1
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a5286f4655ce2fa28f477c0b957ea7f323fe2fab
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78a5f711efceb37e32c48cd6b40addb671fea9cc
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b0c79aa33075b34c3cdcea4132c0afb3fc42d68
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3cb43222bab8ab328fc91ed30899b3df2efbccfd
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34eb902050d473bb2befa15714fb1d30a0991c15
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32d937f94b7805d4c9028b8727a7d6241547da54
Web page

sched/fair: Don't balance task to its current running CPU - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0dd37d6dd33a9c23351e6115ae8cdac7863bc7de

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.14.322 (fixes >=3.6.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-11-03 10:55 UTCEG score recompute
  6. 2026-11-03 10:55 UTCGHSA enrichmentGHSA-g72f-mhc5-x52v · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-27 20:25 UTCEG score recompute
  14. 2026-10-27 20:25 UTCGHSA enrichmentGHSA-g72f-mhc5-x52v · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-25 17:28 UTCEG score recompute
  17. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-20 21:16 UTCEG score recompute
  23. 2026-10-20 21:16 UTCGHSA enrichmentGHSA-g72f-mhc5-x52v · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 69 more
  1. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-18 07:41 UTCEG score recompute
  3. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-12 18:12 UTCEG score recompute
  9. 2026-10-11 21:38 UTCEG score recompute
  10. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-02 04:41 UTCOSV refresh
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-30 16:37 UTCEG score recompute
  21. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-09-13 00:36 UTCOSV refresh
  34. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  46. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-08-25 03:56 UTCOSV refresh
  53. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  59. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  60. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  62. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  63. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  64. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  66. 2026-08-08 21:19 UTCOSV refresh
  67. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  68. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Frequently asked(5)

What is CVE-2023-53215?
CVE-2023-53215 is a high-severity vulnerability; its CVE record was published on September 15, 2025. 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…
When was the CVE record for CVE-2023-53215 published?
The CVE record for CVE-2023-53215 was published on September 15, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 14, 2026; the record at its source may have been updated since.
Is CVE-2023-53215 actively exploited?
CVE-2023-53215 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53215?
CVE-2023-53215 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53215?
A fix for CVE-2023-53215 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53215

Explore →

Is Your Infrastructure Affected by CVE-2023-53215?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs