CVE-2021-47044: sched/fair: Fix shift-out-of-bounds in load_balance()
Vulnerability summary
CVE-2021-47044 is a high (CVSS 7.7) Out-of-bounds Read vulnerability in linux. EPSS estimates a 0.27% chance of exploitation in the next 30 days, higher than 18.8% of scored vulnerabilities.
Not severe (CVSS 7.7, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 2 · Related 2Timeline
- 28-02-2024PublishedVulnerability first disclosed.
- 11-05-2026Last modifiedVulnerability information updated.
Description
In the Linux kernel, the following vulnerability has been resolved: sched/fair: Fix shift-out-of-bounds in load_balance() Syzbot reported a handful of occurrences where an sd->nr_balance_failed can grow to much higher values than one would expect. A successful load_balance() resets it to 0; a failed one increments it. Once it gets to sd->cache_nice_tries + 3, this *should* trigger an active balance, which will either set it to sd->cache_nice_tries+1 or reset it to 0. However, in case the to-be-active-balanced task is not allowed to run on env->dst_cpu, then the increment is done without any further modification. This could then be repeated ad nauseam, and would explain the absurdly high values reported by syzbot (86, 149). VincentG noted there is value in letting sd->cache_nice_tries grow, so the shift itself should be fixed. That means preventing: """ If the value of the right operand is negative or is greater than or equal to the width of the promoted left operand, the behavior is undefined. """ Thus we need to cap the shift exponent to BITS_PER_TYPE(typeof(lefthand)) - 1. I had a look around for other similar cases via coccinelle: @expr@ position pos; expression E1; expression E2; @@ ( E1 >> E2@pos | E1 >> E2@pos ) @cst depends on expr@ position pos; expression expr.E1; constant cst; @@ ( E1 >> cst@pos | E1 << cst@pos ) @script:python depends on !cst@ pos << expr.pos; exp << expr.E2; @@ # Dirty hack to ignore constexpr if exp.upper() != exp: coccilib.report.print_report(pos[0], "Possible UB shift here") The only other match in kernel/sched is rq_clock_thermal() which employs sched_thermal_decay_shift, and that exponent is already capped to 10, so that one is fine.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated7.7HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- OSV · DebianEcosystem advisory · calculated7.7HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- NVDNIST7.7HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS trend
Probability
0.27%
Chance of exploitation in the next 30 days
Percentile
19%
Versus all other CVEs
30-day change
No change 0.00 pp
From 0.27% on 04-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Known conditions: local access, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu61 products
- linux-allwinner-5.19All versions (No fix recorded)
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
- linux-aws-5.13All versions (No fix recorded)
- linux-aws-5.19All versions (No fix recorded)
Linux2 products
- linux≥ 5a7f555904671c0737819fe4d19bd6143de3f6c0, < 80862cbf76c2646f709a57c4517aefe0b094c774 | ≥ 5a7f555904671c0737819fe4d19bd6143de3f6c0, < 2f3eab368e313dba35fc2f51ede778bf7b030b54 | ≥ 5a7f555904671c0737819fe4d19bd6143de3f6c0, < 805cea93e66ca7deaaf6ad3b67224ce47c104c2f | ≥ 5a7f555904671c0737819fe4d19bd6143de3f6c0, < 39a2a6eb5c9b66ea7c8055026303b3aa681b49a5 | 5.10
- linux_kernel≥ 5.10, < 5.10.37 | ≥ 5.11, < 5.11.21 | ≥ 5.12, < 5.12.4
Debian1 product
- linux< 5.10.38-1
3 vendors · 64 products