Поиск уязвимостей
Количество 19
Количество 19
CVE-2022-48731
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_write+0x306/0x3a0 ? common_file_per...
CVE-2022-48731
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_write+0x306/0x3a0 ? common_file_per...
CVE-2022-48731
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_write
CVE-2022-48731
In the Linux kernel, the following vulnerability has been resolved: m ...
GHSA-c864-85xv-823c
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_wr...
BDU:2024-10950
Уязвимость компонентов mm/kmemleak ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2022-7798
ALT-PU-2022-7798: package `kernel-image-std-def` update to version 5.10.99-alt1
ALT-PU-2022-1228
ALT-PU-2022-1228: package `kernel-image-un-def` update to version 5.16.8-alt1
ROS-20241204-02
Множественные уязвимости kernel-lt
ALT-PU-2022-1297
ALT-PU-2022-1297: package `kernel-image-std-def` update to version 5.10.100-alt1
ALT-PU-2022-1289
ALT-PU-2022-1289: package `kernel-image-rt` update to version 5.10.100-alt1.rt62
ALT-PU-2022-1298
ALT-PU-2022-1298: package `kernel-image-un-def` update to version 5.15.23-alt1
ALT-PU-2022-1239
ALT-PU-2022-1239: package `kernel-image-mp` update to version 5.16.8-alt1
ALT-PU-2022-1432
ALT-PU-2022-1432: package `kernel-image-std-kvm` update to version 5.10.102-alt1
ALT-PU-2022-1441
ALT-PU-2022-1441: package `kernel-image-rpi-un` update to version 5.15.25-alt1
ALT-PU-2022-1540
ALT-PU-2022-1540: package `kernel-image-rpi-un` update to version 5.15.28-alt1
ALT-PU-2022-1428
ALT-PU-2022-1428: package `kernel-image-rt` update to version 5.10.100-alt1.rt62
ALT-PU-2022-1421
ALT-PU-2022-1421: package `kernel-image-rpi-def` update to version 5.15.25-alt1
ALT-PU-2022-1419
ALT-PU-2022-1419: package `kernel-image-rpi-def` update to version 5.15.25-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-48731 In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_write+0x306/0x3a0 ? common_file_per... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48731 In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_write+0x306/0x3a0 ? common_file_per... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48731 In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_write | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2022-48731 In the Linux kernel, the following vulnerability has been resolved: m ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-c864-85xv-823c In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid scanning potential huge holes When using devm_request_free_mem_region() and devm_memremap_pages() to add ZONE_DEVICE memory, if requested free mem region's end pfn were huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see move_pfn_range_to_zone()). Thus it creates a huge hole between node_start_pfn() and node_end_pfn(). We found on some AMD APUs, amdkfd requested such a free mem region and created a huge hole. In such a case, following code snippet was just doing busy test_bit() looping on the huge hole. for (pfn = start_pfn; pfn < end_pfn; pfn++) { struct page *page = pfn_to_online_page(pfn); if (!page) continue; ... } So we got a soft lockup: watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221] CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1 RIP: 0010:pfn_to_online_page+0x5/0xd0 Call Trace: ? kmemleak_scan+0x16a/0x440 kmemleak_wr... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-10950 Уязвимость компонентов mm/kmemleak ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ALT-PU-2022-7798 ALT-PU-2022-7798: package `kernel-image-std-def` update to version 5.10.99-alt1 | CVSS3: 7.8 | больше 4 лет назад | ||
ALT-PU-2022-1228 ALT-PU-2022-1228: package `kernel-image-un-def` update to version 5.16.8-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ROS-20241204-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | почти 2 года назад | ||
ALT-PU-2022-1297 ALT-PU-2022-1297: package `kernel-image-std-def` update to version 5.10.100-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1289 ALT-PU-2022-1289: package `kernel-image-rt` update to version 5.10.100-alt1.rt62 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1298 ALT-PU-2022-1298: package `kernel-image-un-def` update to version 5.15.23-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1239 ALT-PU-2022-1239: package `kernel-image-mp` update to version 5.16.8-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1432 ALT-PU-2022-1432: package `kernel-image-std-kvm` update to version 5.10.102-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1441 ALT-PU-2022-1441: package `kernel-image-rpi-un` update to version 5.15.25-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1540 ALT-PU-2022-1540: package `kernel-image-rpi-un` update to version 5.15.28-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1428 ALT-PU-2022-1428: package `kernel-image-rt` update to version 5.10.100-alt1.rt62 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1421 ALT-PU-2022-1421: package `kernel-image-rpi-def` update to version 5.15.25-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1419 ALT-PU-2022-1419: package `kernel-image-rpi-def` update to version 5.15.25-alt1 | CVSS3: 9.8 | больше 4 лет назад |
Уязвимостей на страницу