Количество 112
Количество 112
CVE-2025-38332
scsi: lpfc: Use memcpy() for BIOS version
CVE-2025-38332
In the Linux kernel, the following vulnerability has been resolved: s ...
CVE-2025-38464
In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Google Comp...
CVE-2025-38464
In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Google Comp...
CVE-2025-38464
In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Googl
CVE-2025-38464
tipc: Fix use-after-free in tipc_conn_close().
CVE-2025-38464
In the Linux kernel, the following vulnerability has been resolved: t ...
SUSE-SU-2025:03572-1
Security update for the Linux Kernel (Live Patch 1 for SLE 15 SP7)
SUSE-SU-2025:03567-1
Security update for the Linux Kernel (Live Patch 12 for SLE 15 SP6)
SUSE-SU-2025:03561-1
Security update for the Linux Kernel (Live Patch 26 for SLE 15 SP5)
SUSE-SU-2025:03551-1
Security update for the Linux Kernel (Live Patch 40 for SLE 15 SP4)
SUSE-SU-2025:03515-1
Security update for the Linux Kernel (Live Patch 57 for SLE 15 SP3)
SUSE-SU-2025:03498-1
Security update for the Linux Kernel (Live Patch 68 for SLE 12 SP5)
SUSE-SU-2025:03495-1
Security update for the Linux Kernel RT (Live Patch 10 for SLE 15 SP6)
SUSE-SU-2025:03483-1
Security update for the Linux Kernel (Live Patch 67 for SLE 12 SP5)
SUSE-SU-2025:03480-1
Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP7)
SUSE-SU-2025:03470-1
Security update for the Linux Kernel RT (Live Patch 11 for SLE 15 SP6)
ELSA-2025-20552
ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:02923-1
Security update for the Linux Kernel
SUSE-SU-2025:03578-1
Security update for the Linux Kernel (Live Patch 39 for SLE 15 SP4)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-38332 scsi: lpfc: Use memcpy() for BIOS version | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2025-38332 In the Linux kernel, the following vulnerability has been resolved: s ... | 0% Низкий | 4 месяца назад | ||
CVE-2025-38464 In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Google Comp... | 0% Низкий | 3 месяца назад | ||
CVE-2025-38464 In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Google Comp... | CVSS3: 7.3 | 0% Низкий | 3 месяца назад | |
CVE-2025-38464 In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn. The problem is that tipc_conn_close() is called after releasing the IDR lock. At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref. Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive. Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop(). [0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435 CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Googl | 0% Низкий | 3 месяца назад | ||
CVE-2025-38464 tipc: Fix use-after-free in tipc_conn_close(). | CVSS3: 7.1 | 0% Низкий | 2 месяца назад | |
CVE-2025-38464 In the Linux kernel, the following vulnerability has been resolved: t ... | 0% Низкий | 3 месяца назад | ||
SUSE-SU-2025:03572-1 Security update for the Linux Kernel (Live Patch 1 for SLE 15 SP7) | 24 дня назад | |||
SUSE-SU-2025:03567-1 Security update for the Linux Kernel (Live Patch 12 for SLE 15 SP6) | 24 дня назад | |||
SUSE-SU-2025:03561-1 Security update for the Linux Kernel (Live Patch 26 for SLE 15 SP5) | 24 дня назад | |||
SUSE-SU-2025:03551-1 Security update for the Linux Kernel (Live Patch 40 for SLE 15 SP4) | 25 дней назад | |||
SUSE-SU-2025:03515-1 Security update for the Linux Kernel (Live Patch 57 for SLE 15 SP3) | 27 дней назад | |||
SUSE-SU-2025:03498-1 Security update for the Linux Kernel (Live Patch 68 for SLE 12 SP5) | 28 дней назад | |||
SUSE-SU-2025:03495-1 Security update for the Linux Kernel RT (Live Patch 10 for SLE 15 SP6) | 28 дней назад | |||
SUSE-SU-2025:03483-1 Security update for the Linux Kernel (Live Patch 67 for SLE 12 SP5) | 28 дней назад | |||
SUSE-SU-2025:03480-1 Security update for the Linux Kernel RT (Live Patch 0 for SLE 15 SP7) | 28 дней назад | |||
SUSE-SU-2025:03470-1 Security update for the Linux Kernel RT (Live Patch 11 for SLE 15 SP6) | 29 дней назад | |||
ELSA-2025-20552 ELSA-2025-20552: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 месяцев назад | |||
SUSE-SU-2025:02923-1 Security update for the Linux Kernel | 3 месяца назад | |||
SUSE-SU-2025:03578-1 Security update for the Linux Kernel (Live Patch 39 for SLE 15 SP4) | 23 дня назад |
Уязвимостей на страницу