maple_tree: fix mas_empty_area_rev() null pointer dereference
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s maple_tree code can dereference a null pointer in mas_empty_area_rev(). A local user can trigger a kernel oops by unmapping all VMAs to leave an empty maple tree, then mapping a VMA that reaches the vulnerable path.
Operators running the Linux kernel should check their kernel version; affected versions are not specified in the input.