CVE-2024-36881 Affecting kernel-default-livepatch-devel package, versions <6.4.0-150600.23.22.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-SLES156-KERNELDEFAULTLIVEPATCHDEVEL-8074456
- published24 Sept 2024
- disclosed23 Sept 2024
Introduced: 23 Sep 2024
CVE-2024-36881 (opens in a new tab)How to fix?
Upgrade SLES:15.6 kernel-default-livepatch-devel to version 6.4.0-150600.23.22.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-default-livepatch-devel package and not the kernel-default-livepatch-devel package as distributed by SLES.
See How to fix? for SLES:15.6 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
mm/userfaultfd: reset ptes when close() for wr-protected ones
Userfaultfd unregister includes a step to remove wr-protect bits from all the relevant pgtable entries, but that only covered an explicit UFFDIO_UNREGISTER ioctl, not a close() on the userfaultfd itself. Cover that too. This fixes a WARN trace.
The only user visible side effect is the user can observe leftover wr-protect bits even if the user close()ed on an userfaultfd when releasing the last reference of it. However hopefully that should be harmless, and nothing bad should happen even if so.
This change is now more important after the recent page-table-check patch we merged in mm-unstable (446dd9ad37d0 ("mm/page_table_check: support userfault wr-protect entries")), as we'll do sanity check on uffd-wp bits without vma context. So it's better if we can 100% guarantee no uffd-wp bit leftovers, to make sure each report will be valid.
References
- https://www.suse.com/security/cve/CVE-2024-36881.html
- https://bugzilla.suse.com/1225718
- https://git.kernel.org/stable/c/377f3a9a3d032a52325a5b110379a25dd1ab1931
- https://git.kernel.org/stable/c/8d8b68a5b0c9fb23d37df06bb273ead38fd5a29d
- https://git.kernel.org/stable/c/c88033efe9a391e72ba6b5df4b01d6e628f4e734