Поиск уязвимостей
Количество 21
Количество 21
BDU:2026-18265
Уязвимость ядра операционной системы Linux, связанная с ошибками разыменования указателя, позволяющая нарушителю вызвать отказ в обслуживании
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.]
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.]
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.]
CVE-2026-64297
module: decompress: check return value of module_extend_max_pages()
CVE-2026-64297
In the Linux kernel, the following vulnerability has been resolved: m ...
ROS-20261014-80-0148
Уязвимость kernel-lt
ROS-20261014-73-0149
Уязвимость kernel-lt
GHSA-5c7j-4454-42wh
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.]
ALT-PU-2026-11926
ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1
ALT-PU-2026-12325
ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1
ALT-PU-2026-11249
ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1
ALT-PU-2026-11606
ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1
ALT-PU-2026-21143
ALT-PU-2026-21143: package `kernel-image-rpi-un` update to version 6.12.115-alt1
ALT-PU-2026-20976
ALT-PU-2026-20976: package `kernel-image-rpi-un` update to version 6.12.115-alt1
ALT-PU-2026-11671
ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1
openSUSE-SU-2026:22091-1
Security update for the Linux Kernel
SUSE-SU-2026:4706-1
Security update for the Linux Kernel
SUSE-SU-2026:4640-1
Security update for the Linux Kernel
openSUSE-SU-2026:22313-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2026-18265 Уязвимость ядра операционной системы Linux, связанная с ошибками разыменования указателя, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 6 месяцев назад | |
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.] | CVSS3: 5.5 | 0% Низкий | 4 месяца назад | |
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.] | CVSS3: 5.5 | 0% Низкий | 4 месяца назад | |
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.] | CVSS3: 5.5 | 0% Низкий | 4 месяца назад | |
CVE-2026-64297 module: decompress: check return value of module_extend_max_pages() | 0% Низкий | 4 месяца назад | ||
CVE-2026-64297 In the Linux kernel, the following vulnerability has been resolved: m ... | CVSS3: 5.5 | 0% Низкий | 4 месяца назад | |
ROS-20261014-80-0148 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ROS-20261014-73-0149 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
GHSA-5c7j-4454-42wh 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.] | CVSS3: 5.5 | 0% Низкий | 4 месяца назад | |
ALT-PU-2026-11926 ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
ALT-PU-2026-12325 ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1 | CVSS3: 9.8 | 4 месяца назад | ||
ALT-PU-2026-11249 ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-11606 ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-21143 ALT-PU-2026-21143: package `kernel-image-rpi-un` update to version 6.12.115-alt1 | CVSS3: 10 | 10 дней назад | ||
ALT-PU-2026-20976 ALT-PU-2026-20976: package `kernel-image-rpi-un` update to version 6.12.115-alt1 | CVSS3: 10 | 13 дней назад | ||
ALT-PU-2026-11671 ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1 | CVSS3: 10 | 4 месяца назад | ||
openSUSE-SU-2026:22091-1 Security update for the Linux Kernel | около 1 месяца назад | |||
SUSE-SU-2026:4706-1 Security update for the Linux Kernel | около 1 месяца назад | |||
SUSE-SU-2026:4640-1 Security update for the Linux Kernel | около 1 месяца назад | |||
openSUSE-SU-2026:22313-1 Security update for the Linux Kernel | 20 дней назад |
Уязвимостей на страницу