Поиск уязвимостей
Количество 26
Количество 26
CVE-2025-38538
In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it wil...
CVE-2025-38538
In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it wil...
CVE-2025-38538
In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it wi
CVE-2025-38538
dmaengine: nbpfaxi: Fix memory corruption in probe()
CVE-2025-38538
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-646r-2h84-3p3v
In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it...
BDU:2025-14978
Уязвимость компонента dmaengine ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260323-80-0027
Уязвимость kernel-lt
ROS-20260323-73-0019
Уязвимость kernel-lt
ALT-PU-2025-16598
ALT-PU-2025-16598: package `kernel-image-un-def` update to version 6.1.147-alt1
SUSE-SU-2025:03272-1
Security update for the Linux Kernel
SUSE-SU-2025:03301-1
Security update for the Linux Kernel
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
openSUSE-SU-2026:20287-1
Security update for the Linux Kernel
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
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-38538 In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it wil... | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
CVE-2025-38538 In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it wil... | 0% Низкий | около 1 года назад | ||
CVE-2025-38538 In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it wi | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
CVE-2025-38538 dmaengine: nbpfaxi: Fix memory corruption in probe() | 0% Низкий | 10 месяцев назад | ||
CVE-2025-38538 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
GHSA-646r-2h84-3p3v In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf->chan[] array is allocated earlier in the nbpf_probe() function and it has "num_channels" elements. These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved. In this case, we're copying data from the irqbuf[] array into the nbpf->chan[] array. If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync. I added a check to ensure that we don't go beyond the end of the irqbuf[] array. I'm pretty sure this can't happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the "chan" iterator is where we expect it to be. In the original code we went one element beyond the end of the array so the iterator wasn't in the correct place and it would always return -EINVAL. However, now it... | CVSS3: 7.8 | 0% Низкий | около 1 года назад | |
BDU:2025-14978 Уязвимость компонента dmaengine ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
ROS-20260323-80-0027 Уязвимость kernel-lt | CVSS3: 4.7 | 0% Низкий | 8 месяцев назад | |
ROS-20260323-73-0019 Уязвимость kernel-lt | CVSS3: 4.7 | 0% Низкий | 8 месяцев назад | |
ALT-PU-2025-16598 ALT-PU-2025-16598: package `kernel-image-un-def` update to version 6.1.147-alt1 | CVSS3: 8.4 | больше 1 года назад | ||
SUSE-SU-2025:03272-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03301-1 Security update for the Linux Kernel | около 1 года назад | |||
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) | около 1 года назад | |||
SUSE-SU-2025:03602-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03633-1 Security update for the Linux Kernel | около 1 года назад | |||
openSUSE-SU-2026:20287-1 Security update for the Linux Kernel | 8 месяцев назад | |||
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 года назад |
Уязвимостей на страницу