NULL Pointer Dereference Affecting kernel-syms package, versions <6.4.0-150600.23.7.1
Threat Intelligence
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 ID SNYK-SLES156-KERNELSYMS-7718986
- published 20 Aug 2024
- disclosed 25 Jun 2024
Introduced: 25 Jun 2024
CVE-2024-36891 Open this link in a new tabHow to fix?
Upgrade SLES:15.6 kernel-syms to version 6.4.0-150600.23.7.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-syms package and not the kernel-syms 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:
maple_tree: fix mas_empty_area_rev() null pointer dereference
Currently the code calls mas_start() followed by mas_data_end() if the maple state is MA_START, but mas_start() may return with the maple state node == NULL. This will lead to a null pointer dereference when checking information in the NULL node, which is done in mas_data_end().
Avoid setting the offset if there is no node by waiting until after the maple state is checked for an empty or single entry state.
A user could trigger the events to cause a kernel oops by unmapping all vmas to produce an empty maple tree, then mapping a vma that would cause the scenario described above.
References
- https://www.suse.com/security/cve/CVE-2024-36891.html
- https://bugzilla.suse.com/1225710
- https://git.kernel.org/stable/c/6c9c7c1e63b198a8b979ad963eb21410f10ccb00
- https://git.kernel.org/stable/c/955a923d2809803980ff574270f81510112be9cf
- https://git.kernel.org/stable/c/f3956791cf526540addd3295e4c1e0f0442486cc
- https://git.kernel.org/stable/c/883e5d542bbdddbddeba60250cb482baf3ae2415