Количество 31
Количество 31
GHSA-2cq7-86qp-4xjx
In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'.
CVE-2023-53995
In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'.
CVE-2023-53995
In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'.
CVE-2023-53995
In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'.
CVE-2023-53995
In the Linux kernel, the following vulnerability has been resolved: n ...
SUSE-SU-2026:3829-1
Security update for the Linux Kernel (Live Patch 57 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:3807-1
Security update for the Linux Kernel (Live Patch 43 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:3808-1
Security update for the Linux Kernel (Live Patch 84 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3749-1
Security update for the Linux Kernel (Live Patch 83 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3826-1
Security update for the Linux Kernel (Live Patch 79 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3757-1
Security update for the Linux Kernel (Live Patch 55 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:3743-1
Security update for the Linux Kernel (Live Patch 75 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3740-1
Security update for the Linux Kernel (Live Patch 76 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3809-1
Security update for the Linux Kernel
SUSE-SU-2026:3723-1
Security update for the Linux Kernel (Live Patch 72 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3706-1
Security update for the Linux Kernel (Live Patch 71 for SUSE Linux Enterprise 12 SP5)
SUSE-SU-2026:3721-1
Security update for the Linux Kernel (Live Patch 54 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:3759-1
Security update for the Linux Kernel (Live Patch 40 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:3747-1
Security update for the Linux Kernel (Live Patch 53 for SUSE Linux Enterprise 15 SP4)
SUSE-SU-2026:3766-1
Security update for the Linux Kernel (Live Patch 49 for SUSE Linux Enterprise 15 SP4)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-2cq7-86qp-4xjx In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'. | 0% Низкий | 9 месяцев назад | ||
CVE-2023-53995 In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'. | 0% Низкий | 9 месяцев назад | ||
CVE-2023-53995 In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'. | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2023-53995 In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'. | 0% Низкий | 9 месяцев назад | ||
CVE-2023-53995 In the Linux kernel, the following vulnerability has been resolved: n ... | 0% Низкий | 9 месяцев назад | ||
SUSE-SU-2026:3829-1 Security update for the Linux Kernel (Live Patch 57 for SUSE Linux Enterprise 15 SP4) | 14 дней назад | |||
SUSE-SU-2026:3807-1 Security update for the Linux Kernel (Live Patch 43 for SUSE Linux Enterprise 15 SP5) | 15 дней назад | |||
SUSE-SU-2026:3808-1 Security update for the Linux Kernel (Live Patch 84 for SUSE Linux Enterprise 12 SP5) | 15 дней назад | |||
SUSE-SU-2026:3749-1 Security update for the Linux Kernel (Live Patch 83 for SUSE Linux Enterprise 12 SP5) | 16 дней назад | |||
SUSE-SU-2026:3826-1 Security update for the Linux Kernel (Live Patch 79 for SUSE Linux Enterprise 12 SP5) | 14 дней назад | |||
SUSE-SU-2026:3757-1 Security update for the Linux Kernel (Live Patch 55 for SUSE Linux Enterprise 15 SP4) | 16 дней назад | |||
SUSE-SU-2026:3743-1 Security update for the Linux Kernel (Live Patch 75 for SUSE Linux Enterprise 12 SP5) | 16 дней назад | |||
SUSE-SU-2026:3740-1 Security update for the Linux Kernel (Live Patch 76 for SUSE Linux Enterprise 12 SP5) | 17 дней назад | |||
SUSE-SU-2026:3809-1 Security update for the Linux Kernel | 15 дней назад | |||
SUSE-SU-2026:3723-1 Security update for the Linux Kernel (Live Patch 72 for SUSE Linux Enterprise 12 SP5) | 17 дней назад | |||
SUSE-SU-2026:3706-1 Security update for the Linux Kernel (Live Patch 71 for SUSE Linux Enterprise 12 SP5) | 18 дней назад | |||
SUSE-SU-2026:3721-1 Security update for the Linux Kernel (Live Patch 54 for SUSE Linux Enterprise 15 SP4) | 17 дней назад | |||
SUSE-SU-2026:3759-1 Security update for the Linux Kernel (Live Patch 40 for SUSE Linux Enterprise 15 SP5) | 16 дней назад | |||
SUSE-SU-2026:3747-1 Security update for the Linux Kernel (Live Patch 53 for SUSE Linux Enterprise 15 SP4) | 16 дней назад | |||
SUSE-SU-2026:3766-1 Security update for the Linux Kernel (Live Patch 49 for SUSE Linux Enterprise 15 SP4) | 16 дней назад |
Уязвимостей на страницу