Поиск уязвимостей
Количество 35
Количество 35
BDU:2025-10727
Уязвимость функции mmap() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260324-80-0003
Уязвимость kernel-lt
ROS-20260324-73-0003
Уязвимость kernel-lt
CVE-2025-38563
In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to be...
CVE-2025-38563
In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to be...
CVE-2025-38563
In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to b
CVE-2025-38563
perf/core: Prevent VMA split of buffer mappings
CVE-2025-38563
In the Linux kernel, the following vulnerability has been resolved: p ...
GHSA-722p-jvv6-w5fv
In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have t...
ALT-PU-2025-16599
ALT-PU-2025-16599: package `kernel-image-un-def` update to version 6.1.148-alt1
ALT-PU-2025-10524
ALT-PU-2025-10524: package `kernel-image-rt` update to version 6.12.42-alt1
ALT-PU-2025-10497
ALT-PU-2025-10497: package `kernel-image-6.12` update to version 6.12.42-alt1
ALT-PU-2025-16619
ALT-PU-2025-16619: package `kernel-image-rt` update to version 5.10.241-alt1.rt135
ALT-PU-2025-16606
ALT-PU-2025-16606: package `kernel-image-std-def` update to version 5.10.241-alt1
SUSE-SU-2025:03314-1
Security update for the Linux Kernel
SUSE-SU-2025:03310-1
Security update for the Linux Kernel
SUSE-SU-2025:03344-1
Security update for the Linux Kernel
SUSE-SU-2026:0474-1
Security update for the Linux Kernel
SUSE-SU-2025:03204-1
Security update for the Linux Kernel
ALT-PU-2026-1529
ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2025-10727 Уязвимость функции mmap() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260324-80-0003 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
ROS-20260324-73-0003 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
CVE-2025-38563 In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to be... | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
CVE-2025-38563 In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to be... | CVSS3: 4.4 | 0% Низкий | около 1 года назад | |
CVE-2025-38563 In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have to b | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
CVE-2025-38563 perf/core: Prevent VMA split of buffer mappings | CVSS3: 7.8 | 0% Низкий | 10 месяцев назад | |
CVE-2025-38563 In the Linux kernel, the following vulnerability has been resolved: p ... | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
GHSA-722p-jvv6-w5fv In the Linux kernel, the following vulnerability has been resolved: perf/core: Prevent VMA split of buffer mappings The perf mmap code is careful about mmap()'ing the user page with the ringbuffer and additionally the auxiliary buffer, when the event supports it. Once the first mapping is established, subsequent mapping have to use the same offset and the same size in both cases. The reference counting for the ringbuffer and the auxiliary buffer depends on this being correct. Though perf does not prevent that a related mapping is split via mmap(2), munmap(2) or mremap(2). A split of a VMA results in perf_mmap_open() calls, which take reference counts, but then the subsequent perf_mmap_close() calls are not longer fulfilling the offset and size checks. This leads to reference count leaks. As perf already has the requirement for subsequent mappings to match the initial mapping, the obvious consequence is that VMA splits, caused by resizing of a mapping or partial unmapping, have t... | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
ALT-PU-2025-16599 ALT-PU-2025-16599: package `kernel-image-un-def` update to version 6.1.148-alt1 | CVSS3: 8.1 | около 1 года назад | ||
ALT-PU-2025-10524 ALT-PU-2025-10524: package `kernel-image-rt` update to version 6.12.42-alt1 | CVSS3: 8.1 | около 1 года назад | ||
ALT-PU-2025-10497 ALT-PU-2025-10497: package `kernel-image-6.12` update to version 6.12.42-alt1 | CVSS3: 8.1 | около 1 года назад | ||
ALT-PU-2025-16619 ALT-PU-2025-16619: package `kernel-image-rt` update to version 5.10.241-alt1.rt135 | CVSS3: 8.1 | около 1 года назад | ||
ALT-PU-2025-16606 ALT-PU-2025-16606: package `kernel-image-std-def` update to version 5.10.241-alt1 | CVSS3: 8.1 | около 1 года назад | ||
SUSE-SU-2025:03314-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03310-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03344-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2026:0474-1 Security update for the Linux Kernel | 9 месяцев назад | |||
SUSE-SU-2025:03204-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2026-1529 ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1 | CVSS3: 9.8 | 10 месяцев назад |
Уязвимостей на страницу