Количество 112
Количество 112
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:03583-1
Security update for the Linux Kernel (Live Patch 58 for SLE 15 SP3)
SUSE-SU-2025:03576-1
Security update for the Linux Kernel (Live Patch 2 for SLE 15 SP7)
SUSE-SU-2025:03568-1
Security update for the Linux Kernel (Live Patch 13 for SLE 15 SP6)
SUSE-SU-2025:03562-1
Security update for the Linux Kernel (Live Patch 29 for SLE 15 SP5)
SUSE-SU-2025:03552-1
Security update for the Linux Kernel (Live Patch 42 for SLE 15 SP4)
SUSE-SU-2025:03550-1
Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP4)
SUSE-SU-2025:03497-1
Security update for the Linux Kernel (Live Patch 69 for SLE 12 SP5)
SUSE-SU-2025:03485-1
Security update for the Linux Kernel (Live Patch 70 for SLE 12 SP5)
SUSE-SU-2025:03479-1
Security update for the Linux Kernel RT (Live Patch 2 for SLE 15 SP7)
SUSE-SU-2025:03473-1
Security update for the Linux Kernel RT (Live Patch 13 for SLE 15 SP6)
GHSA-79vc-v8qm-8x53
In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_qfq: Fix race condition on qfq_aggregate A race condition can occur when 'agg' is modified in qfq_change_agg (called during qfq_enqueue) while other threads access it concurrently. For example, qfq_dump_class may trigger a NULL dereference, and qfq_delete_class may cause a use-after-free. This patch addresses the issue by: 1. Moved qfq_destroy_class into the critical section. 2. Added sch_tree_lock protection to qfq_dump_class and qfq_dump_class_stats.
BDU:2025-09177
Уязвимость функции qfq_aggregate() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
SUSE-SU-2025:02997-1
Security update for the Linux Kernel
SUSE-SU-2025:03011-1
Security update for the Linux Kernel
CVE-2025-38332
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.
CVE-2025-38332
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.
CVE-2025-38332
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
SUSE-SU-2025:02996-1 Security update for the Linux Kernel | 2 месяца назад | |||
SUSE-SU-2025:02969-1 Security update for the Linux Kernel | 2 месяца назад | |||
SUSE-SU-2025:02853-1 Security update for the Linux Kernel | 3 месяца назад | |||
SUSE-SU-2025:03583-1 Security update for the Linux Kernel (Live Patch 58 for SLE 15 SP3) | 0% Низкий | 23 дня назад | ||
SUSE-SU-2025:03576-1 Security update for the Linux Kernel (Live Patch 2 for SLE 15 SP7) | 0% Низкий | 24 дня назад | ||
SUSE-SU-2025:03568-1 Security update for the Linux Kernel (Live Patch 13 for SLE 15 SP6) | 0% Низкий | 24 дня назад | ||
SUSE-SU-2025:03562-1 Security update for the Linux Kernel (Live Patch 29 for SLE 15 SP5) | 0% Низкий | 24 дня назад | ||
SUSE-SU-2025:03552-1 Security update for the Linux Kernel (Live Patch 42 for SLE 15 SP4) | 0% Низкий | 25 дней назад | ||
SUSE-SU-2025:03550-1 Security update for the Linux Kernel (Live Patch 41 for SLE 15 SP4) | 0% Низкий | 25 дней назад | ||
SUSE-SU-2025:03497-1 Security update for the Linux Kernel (Live Patch 69 for SLE 12 SP5) | 0% Низкий | 28 дней назад | ||
SUSE-SU-2025:03485-1 Security update for the Linux Kernel (Live Patch 70 for SLE 12 SP5) | 0% Низкий | 28 дней назад | ||
SUSE-SU-2025:03479-1 Security update for the Linux Kernel RT (Live Patch 2 for SLE 15 SP7) | 0% Низкий | 28 дней назад | ||
SUSE-SU-2025:03473-1 Security update for the Linux Kernel RT (Live Patch 13 for SLE 15 SP6) | 0% Низкий | 29 дней назад | ||
GHSA-79vc-v8qm-8x53 In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_qfq: Fix race condition on qfq_aggregate A race condition can occur when 'agg' is modified in qfq_change_agg (called during qfq_enqueue) while other threads access it concurrently. For example, qfq_dump_class may trigger a NULL dereference, and qfq_delete_class may cause a use-after-free. This patch addresses the issue by: 1. Moved qfq_destroy_class into the critical section. 2. Added sch_tree_lock protection to qfq_dump_class and qfq_dump_class_stats. | 0% Низкий | 3 месяца назад | ||
BDU:2025-09177 Уязвимость функции qfq_aggregate() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7 | 0% Низкий | 4 месяца назад | |
SUSE-SU-2025:02997-1 Security update for the Linux Kernel | 2 месяца назад | |||
SUSE-SU-2025:03011-1 Security update for the Linux Kernel | 2 месяца назад | |||
CVE-2025-38332 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string. | 0% Низкий | 4 месяца назад | ||
CVE-2025-38332 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string. | CVSS3: 7 | 0% Низкий | 4 месяца назад | |
CVE-2025-38332 In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string. | 0% Низкий | 4 месяца назад |
Уязвимостей на страницу