CVE-2026-64297
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.]
Affected versions
Linux kernel versions
5.17
and later are affected. Fixed in
6.1.178,
6.6.145,
6.12.96,
6.18.39,
7.1.4,
7.2-rc1
and their respective stable series.
References
6 totalFrequently asked questions
-
What is CVE-2026-64297?
CVE-2026-64297 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.17 onward and has been patched in 6.1.178, 6.6.145, 6.12.96 and others. CVE-2026-64297 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64297?
Yes. CVE-2026-64297 has been patched. Fixed versions include 6.1.178, 6.6.145, 6.12.96 and others. If you are running Linux kernel 5.17 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64297 actively exploited?
No. CVE-2026-64297 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.