Use After Free Affecting kernel-libbpf package, versions <0:6.1.66-91.160.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNELLIBBPF-8494232
  • published11 Dec 2024
  • disclosed21 May 2024

Introduced: 21 May 2024

CVE-2023-52859  (opens in a new tab)
CWE-416  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-libbpf to version 0:6.1.66-91.160.amzn2023 or higher.
This issue was patched in ALAS2023-2023-461.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-libbpf package and not the kernel-libbpf package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

perf: hisi: Fix use-after-free when register pmu fails

When we fail to register the uncore pmu, the pmu context may not been allocated. The error handing will call cpuhp_state_remove_instance() to call uncore pmu offline callback, which migrate the pmu context. Since that's liable to lead to some kind of use-after-free.

Use cpuhp_state_remove_instance_nocalls() instead of cpuhp_state_remove_instance() so that the notifiers don't execute after the PMU device has been failed to register.

CVSS Scores

version 3.1