CVE-2021-47044

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.

• CWE-125

• https://git.kernel.org/stable/c/2f3eab368e313dba35fc2f51ede778bf7b030b54Patch
• https://git.kernel.org/stable/c/39a2a6eb5c9b66ea7c8055026303b3aa681b49a5Patch
• https://git.kernel.org/stable/c/805cea93e66ca7deaaf6ad3b67224ce47c104c2fPatch
• https://git.kernel.org/stable/c/80862cbf76c2646f709a57c4517aefe0b094c774Patch
• https://git.kernel.org/stable/c/2f3eab368e313dba35fc2f51ede778bf7b030b54Patch
• https://git.kernel.org/stable/c/39a2a6eb5c9b66ea7c8055026303b3aa681b49a5Patch
• https://git.kernel.org/stable/c/805cea93e66ca7deaaf6ad3b67224ce47c104c2fPatch
• https://git.kernel.org/stable/c/80862cbf76c2646f709a57c4517aefe0b094c774Patch

Published

Feb 28, 2024

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2021-47038In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2021-47039In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2021-47040In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2021-47041In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2021-47042In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2021-47043In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2021-47045In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2021-47046In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2021-47047In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2021-47048In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2021-47049In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2021-47050In the Linux kernel, the following vulnerability has been re…5.5