Information Exposure Affecting kernel-libbpf package, versions <0:6.12.35-55.103.amzn2023


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.04% (10th 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-12559251
  • published9 Sept 2025
  • disclosed28 Jun 2025

Introduced: 28 Jun 2025

CVE-2025-38085  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-libbpf to version 0:6.12.35-55.103.amzn2023 or higher.
This issue was patched in ALAS2023-2025-1080.

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:

mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race

huge_pmd_unshare() drops a reference on a page table that may have previously been shared across processes, potentially turning it into a normal page table used in another process in which unrelated VMAs can afterwards be installed.

If this happens in the middle of a concurrent gup_fast(), gup_fast() could end up walking the page tables of another process. While I don't see any way in which that immediately leads to kernel memory corruption, it is really weird and unexpected.

Fix it with an explicit broadcast IPI through tlb_remove_table_sync_one(), just like we do in khugepaged when removing page tables for a THP collapse.

CVSS Base Scores

version 3.1