Поиск уязвимостей
Количество 19
Количество 19
CVE-2022-49067
In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 dev_ioctl+0x5d0/0x770 sock_do_ioctl+0xf0/0x1d...
CVE-2022-49067
In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 dev_ioctl+0x5d0/0x770 sock_do_ioctl+0xf0/0x1d...
CVE-2022-49067
In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 de
CVE-2022-49067
In the Linux kernel, the following vulnerability has been resolved: p ...
GHSA-3vm4-73fj-2j43
In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 ...
BDU:2025-06039
Уязвимость функции virt_addr_valid() модуля arch/powerpc/include/asm/page.h ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20250522-01
Множественные уязвимости kernel-lt
ALT-PU-2022-1735
ALT-PU-2022-1735: package `kernel-image-std-def` update to version 5.10.111-alt1
ALT-PU-2022-7802
ALT-PU-2022-7802: package `kernel-image-std-def` update to version 5.15.34-alt1
ALT-PU-2022-7696
ALT-PU-2022-7696: package `kernel-image-un-def` update to version 5.15.34-alt1
ALT-PU-2022-1692
ALT-PU-2022-1692: package `kernel-image-un-def` update to version 5.16.20-alt1
ALT-PU-2022-1830
ALT-PU-2022-1830: package `kernel-image-rpi-def` update to version 5.15.36-alt1
ALT-PU-2022-1881
ALT-PU-2022-1881: package `kernel-image-rt` update to version 5.10.115-alt1.rt67
ALT-PU-2022-1880
ALT-PU-2022-1880: package `kernel-image-rt` update to version 5.10.115-alt1.rt67
ALT-PU-2022-1907
ALT-PU-2022-1907: package `kernel-image-std-kvm` update to version 5.10.117-alt1
ALT-PU-2022-1730
ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1
ALT-PU-2022-1833
ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1
ALT-PU-2022-2152
ALT-PU-2022-2152: package `kernel-image-rpi-un` update to version 5.18.7-alt1
ALT-PU-2022-2155
ALT-PU-2022-2155: package `kernel-image-rpi-un` update to version 5.18.7-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-49067 In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 dev_ioctl+0x5d0/0x770 sock_do_ioctl+0xf0/0x1d... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2022-49067 In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 dev_ioctl+0x5d0/0x770 sock_do_ioctl+0xf0/0x1d... | 0% Низкий | больше 1 года назад | ||
CVE-2022-49067 In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 de | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2022-49067 In the Linux kernel, the following vulnerability has been resolved: p ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-3vm4-73fj-2j43 In the Linux kernel, the following vulnerability has been resolved: powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit mpe: On 64-bit Book3E vmalloc space starts at 0x8000000000000000. Because of the way __pa() works we have: __pa(0x8000000000000000) == 0, and therefore virt_to_pfn(0x8000000000000000) == 0, and therefore virt_addr_valid(0x8000000000000000) == true Which is wrong, virt_addr_valid() should be false for vmalloc space. In fact all vmalloc addresses that alias with a valid PFN will return true from virt_addr_valid(). That can cause bugs with hardened usercopy as described below by Kefeng Wang: When running ethtool eth0 on 64-bit Book3E, a BUG occurred: usercopy: Kernel memory exposure attempt detected from SLUB object not in SLUB page?! (offset 0, size 1048)! kernel BUG at mm/usercopy.c:99 ... usercopy_abort+0x64/0xa0 (unreliable) __check_heap_object+0x168/0x190 __check_object_size+0x1a0/0x200 dev_ethtool+0x2494/0x2b20 ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
BDU:2025-06039 Уязвимость функции virt_addr_valid() модуля arch/powerpc/include/asm/page.h ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 4 лет назад | |
ROS-20250522-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2022-1735 ALT-PU-2022-1735: package `kernel-image-std-def` update to version 5.10.111-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-7802 ALT-PU-2022-7802: package `kernel-image-std-def` update to version 5.15.34-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-7696 ALT-PU-2022-7696: package `kernel-image-un-def` update to version 5.15.34-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1692 ALT-PU-2022-1692: package `kernel-image-un-def` update to version 5.16.20-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1830 ALT-PU-2022-1830: package `kernel-image-rpi-def` update to version 5.15.36-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1881 ALT-PU-2022-1881: package `kernel-image-rt` update to version 5.10.115-alt1.rt67 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1880 ALT-PU-2022-1880: package `kernel-image-rt` update to version 5.10.115-alt1.rt67 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1907 ALT-PU-2022-1907: package `kernel-image-std-kvm` update to version 5.10.117-alt1 | CVSS3: 8.8 | больше 4 лет назад | ||
ALT-PU-2022-1730 ALT-PU-2022-1730: package `kernel-image-mp` update to version 5.17.4-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-1833 ALT-PU-2022-1833: package `kernel-image-rpi-def` update to version 5.15.36-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-2152 ALT-PU-2022-2152: package `kernel-image-rpi-un` update to version 5.18.7-alt1 | CVSS3: 9.8 | больше 4 лет назад | ||
ALT-PU-2022-2155 ALT-PU-2022-2155: package `kernel-image-rpi-un` update to version 5.18.7-alt1 | CVSS3: 9.8 | больше 4 лет назад |
Уязвимостей на страницу