CVE-2024-36000 Affecting kernel-64k-modules package, versions <0:5.14.0-427.35.1.el9_4


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise 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-RHEL9-KERNEL64KMODULES-6941122
  • published21 May 2024
  • disclosed20 May 2024

Introduced: 20 May 2024

CVE-2024-36000  (opens in a new tab)

How to fix?

Upgrade RHEL:9 kernel-64k-modules to version 0:5.14.0-427.35.1.el9_4 or higher.
This issue was patched in RHSA-2024:6567.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-64k-modules package and not the kernel-64k-modules package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

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

mm/hugetlb: fix missing hugetlb_lock for resv uncharge

There is a recent report on UFFDIO_COPY over hugetlb:

https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/

350: lockdep_assert_held(&hugetlb_lock);

Should be an issue in hugetlb but triggered in an userfault context, where it goes into the unlikely path where two threads modifying the resv map together. Mike has a fix in that path for resv uncharge but it looks like the locking criteria was overlooked: hugetlb_cgroup_uncharge_folio_rsvd() will update the cgroup pointer, so it requires to be called with the lock held.

CVSS Scores

version 3.1