CVE-2026-93172 Affecting bpftool6.12-debuginfo package, versions <1:6.12.110-135.201.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.2% (11th 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-BPFTOOL612DEBUGINFO-20865376
  • published13 Oct 2026
  • disclosed17 Sept 2026

Introduced: 17 Sep 2026

CVE-2026-93172  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 bpftool6.12-debuginfo to version 1:6.12.110-135.201.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3196.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bpftool6.12-debuginfo package and not the bpftool6.12-debuginfo 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:

mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug

We miss a failed allocation check for pgdat->per_cpu_nodestats, which results in a NULL deref when we offset into the per-cpu area.

Propagate -ENOMEM up the stack and leave per_cpu_nodestats pointing at boot_nodestats so a later online can retry the allocation.

hotadd_init_pgdat() returns NULL on failure, which __try_online_node() already maps to -ENOMEM.

On failure nothing needs to be unwound:

  • the node is never marked online
  • per_cpu_nodestats is left pointing at boot_nodestats
  • __add_memory_resource() cleans up pending memblock resources
  • later online attempts retry the per_cpu_nodestats allocation