module: decompress: check return value of module_extend_max_pages()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b1ae6dc41eaaa98bb75671e0f3665bfda248c3e7 · < 786d2d84416a9a1c1a47b71a68d679d886284be2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
module: decompress: check return value of module_extend_max_pages()
module_extend_max_pages() calls kvrealloc() internally and returns -ENOMEM on allocation failure. The return value is never checked.
If the initial allocation fails, info->pages remains NULL and info->max_pages remains 0. Subsequent calls to module_get_next_page() will attempt to dynamically grow the array by calling module_extend_max_pages(info, 0) since info->used_pages is 0. This results in kvrealloc(NULL, 0) returning ZERO_SIZE_PTR, which is treated as a success, leading to a dereference of ZERO_SIZE_PTR and a kernel oops.
Fix: add the missing error check after module_extend_max_pages() and return immediately on failure. This matches the pattern used by every other kvrealloc() caller in the module loading path.
[Sami: Corrected the analysis in the commit message.]
From the CVE record · Linux
The Linux kernel's module decompression path fails to check whether an allocation to extend its page array succeeded. If that allocation fails during module loading, a subsequent dereference can cause a kernel oops. The input does not specify an attacker access path or authentication requirements.
Engineers running Linux kernels should check whether their kernel includes the fix; affected versions are not specified.