The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2021-47044)

Note that Nessus relies on the presence of the package as reported by the vendor.

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: 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. (CVE-2021-47044)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 已解決 Linux 核心中的下列弱點：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. (CVE-2021-47044)

請注意，Nessus 依賴供應商報告的套件存在。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 已修复 Linux 内核中的下列漏洞：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. (CVE-2021-47044)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

ID	Name	Product	Family	Published	Updated	Severity
246102	Linux Distros Unpatched Vulnerability : CVE-2021-47044	Nessus	Misc.	8/8/2025	8/8/2025	high
160459	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	5/2/2022	6/23/2025	high
246102	Linux Distros のパッチ未適用の脆弱性: CVE-2021-47044	Nessus	Misc.	8/8/2025	8/8/2025	high
160459	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	5/2/2022	6/23/2025	high
246102	Linux Distros 未修補的弱點：CVE-2021-47044	Nessus	Misc.	8/8/2025	8/8/2025	high
160459	Amazon Linux 2：kernel (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	5/2/2022	6/23/2025	high
246102	Linux Distros 未修补的漏洞：CVE-2021-47044	Nessus	Misc.	8/8/2025	8/8/2025	high
160459	Amazon Linux 2：内核 (ALASKERNEL-5.10-2022-002)	Nessus	Amazon Linux Local Security Checks	5/2/2022	6/23/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high