Количество 20
Количество 20
BDU:2025-10727
Уязвимость функции mmap() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
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...
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-2025:03204-1
Security update for the Linux Kernel
SUSE-SU-2025:03272-1
Security update for the Linux Kernel
SUSE-SU-2025:03301-1
Security update for the Linux Kernel
ELSA-2025-20662
ELSA-2025-20662: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:03382-1
Security update for the Linux Kernel
SUSE-SU-2025:03290-1
Security update for the Linux Kernel
ELSA-2025-20663
ELSA-2025-20663: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:03602-1
Security update for the Linux Kernel
SUSE-SU-2025:03633-1
Security update for the Linux Kernel
SUSE-SU-2025:03634-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2025-10727 Уязвимость функции mmap() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
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... | 0% Низкий | 3 месяца назад | ||
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: 5.5 | 0% Низкий | 3 месяца назад | |
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 | 0% Низкий | 3 месяца назад | ||
CVE-2025-38563 perf/core: Prevent VMA split of buffer mappings | CVSS3: 7.8 | 0% Низкий | 2 месяца назад | |
CVE-2025-38563 In the Linux kernel, the following vulnerability has been resolved: p ... | 0% Низкий | 3 месяца назад | ||
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... | 0% Низкий | 3 месяца назад | ||
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-2025:03204-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
SUSE-SU-2025:03272-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
SUSE-SU-2025:03301-1 Security update for the Linux Kernel | около 1 месяца назад | |||
ELSA-2025-20662 ELSA-2025-20662: Unbreakable Enterprise kernel security update (IMPORTANT) | 23 дня назад | |||
SUSE-SU-2025:03382-1 Security update for the Linux Kernel | около 1 месяца назад | |||
SUSE-SU-2025:03290-1 Security update for the Linux Kernel | около 1 месяца назад | |||
ELSA-2025-20663 ELSA-2025-20663: Unbreakable Enterprise kernel security update (IMPORTANT) | 26 дней назад | |||
SUSE-SU-2025:03602-1 Security update for the Linux Kernel | 21 день назад | |||
SUSE-SU-2025:03633-1 Security update for the Linux Kernel | 19 дней назад | |||
SUSE-SU-2025:03634-1 Security update for the Linux Kernel | 19 дней назад |
Уязвимостей на страницу