Количество 15
Количество 15
CVE-2025-38428
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);"
CVE-2025-38428
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);"
CVE-2025-38428
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);"
CVE-2025-38428
Input: ims-pcu - check record size in ims_pcu_flash_firmware()
CVE-2025-38428
In the Linux kernel, the following vulnerability has been resolved: I ...
GHSA-733g-xvvm-2g6j
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);"
BDU:2025-10953
Уязвимость функции ims_pcu_flash_firmware ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20250902-01
Множественные уязвимости kernel-lt
SUSE-SU-2025:03023-1
Security update for the Linux Kernel
SUSE-SU-2025:02996-1
Security update for the Linux Kernel
SUSE-SU-2025:02969-1
Security update for the Linux Kernel
SUSE-SU-2025:02853-1
Security update for the Linux Kernel
SUSE-SU-2025:02997-1
Security update for the Linux Kernel
SUSE-SU-2025:03011-1
Security update for the Linux Kernel
SUSE-SU-2025:02923-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2025-38428 In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);" | 0% Низкий | 4 месяца назад | |
 | CVE-2025-38428 In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);" | CVSS3: 5.5 | 0% Низкий | 4 месяца назад |
 | CVE-2025-38428 In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);" | 0% Низкий | 4 месяца назад | |
 | CVE-2025-38428 Input: ims-pcu - check record size in ims_pcu_flash_firmware() | CVSS3: 7.8 | 0% Низкий | 3 месяца назад |
| CVE-2025-38428 In the Linux kernel, the following vulnerability has been resolved: I ... | 0% Низкий | 4 месяца назад | |
| GHSA-733g-xvvm-2g6j In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);" | 0% Низкий | 4 месяца назад | |
 | BDU:2025-10953 Уязвимость функции ims_pcu_flash_firmware ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 4 месяца назад |
 | ROS-20250902-01 Множественные уязвимости kernel-lt | CVSS3: 5.5 | 2 месяца назад | |
 | SUSE-SU-2025:03023-1 Security update for the Linux Kernel | 2 месяца назад | ||
| SUSE-SU-2025:02996-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:02969-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:02853-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:02997-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:03011-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:02923-1 Security update for the Linux Kernel | 3 месяца назад |
Уязвимостей на страницу