CVE-2021-47044
published 2024-02-28CVE-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…
PriorityP335high7.7CVSS 3.1
AVLACLPRNUINSUCHINAH
EPSS
0.27%
18.7th percentile
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.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.38-1 (bookworm) | linux 5.10.38-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 5a7f555904671c0737819fe4d19bd6143de3f6c0 < 80862cbf76c2646f709a57c4517aefe0b094c774 | 80862cbf76c2646f709a57c4517aefe0b094c774 |
| linux | linux | >= 5a7f555904671c0737819fe4d19bd6143de3f6c0 < 2f3eab368e313dba35fc2f51ede778bf7b030b54 | 2f3eab368e313dba35fc2f51ede778bf7b030b54 |
| linux | linux | >= 5a7f555904671c0737819fe4d19bd6143de3f6c0 < 805cea93e66ca7deaaf6ad3b67224ce47c104c2f | 805cea93e66ca7deaaf6ad3b67224ce47c104c2f |
| linux | linux | >= 5a7f555904671c0737819fe4d19bd6143de3f6c0 < 39a2a6eb5c9b66ea7c8055026303b3aa681b49a5 | 39a2a6eb5c9b66ea7c8055026303b3aa681b49a5 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 5.10 < 5.10.37 | 5.10.37 |
| linux | linux_kernel | >= 5.11 < 5.11.21 | 5.11.21 |
| linux | linux_kernel | >= 5.12 < 5.12.4 | 5.12.4 |
CVSS provenance
nvdv3.17.7HIGHCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
osv7.7HIGH
vendor_debian7.7HIGH
vendor_redhat7.7HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: sched/fair: Fix shift-out-of-bounds in load_balance()
vendor_redhat·2024-02-28·CVSS 7.7
CVE-2021-47044 [HIGH] CWE-125 kernel: sched/fair: Fix shift-out-of-bounds in load_balance()
kernel: sched/fair: Fix shift-out-of-bounds in load_balance()
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). Vinc
Debian
CVE-2021-47044: linux - In the Linux kernel, the following vulnerability has been resolved: sched/fair:...
vendor_debian·2021·CVSS 7.7
CVE-2021-47044 [HIGH] CVE-2021-47044: linux - In the Linux kernel, the following vulnerability has been resolved: sched/fair:...
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,
GHSA
GHSA-8g29-7ww6-62wf: In the Linux kernel, the following vulnerability has been resolved:
sched/fair: Fix shift-out-of-bounds in load_balance()
Syzbot reported a handful
ghsa_unreviewed·2024-02-28
CVE-2021-47044 [HIGH] CWE-125 GHSA-8g29-7ww6-62wf: In the Linux kernel, the following vulnerability has been resolved:
sched/fair: Fix shift-out-of-bounds in load_balance()
Syzbot reported a handful
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 g
OSV
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
osv·2024-02-28·CVSS 7.7
CVE-2021-47044 [HIGH] 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
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,
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/2f3eab368e313dba35fc2f51ede778bf7b030b54https://git.kernel.org/stable/c/39a2a6eb5c9b66ea7c8055026303b3aa681b49a5https://git.kernel.org/stable/c/805cea93e66ca7deaaf6ad3b67224ce47c104c2fhttps://git.kernel.org/stable/c/80862cbf76c2646f709a57c4517aefe0b094c774https://git.kernel.org/stable/c/2f3eab368e313dba35fc2f51ede778bf7b030b54https://git.kernel.org/stable/c/39a2a6eb5c9b66ea7c8055026303b3aa681b49a5https://git.kernel.org/stable/c/805cea93e66ca7deaaf6ad3b67224ce47c104c2fhttps://git.kernel.org/stable/c/80862cbf76c2646f709a57c4517aefe0b094c774
2024-02-28
Published