Most recent entries from all

Most recent entries from all https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:56:49 +0000 bdu:2024-08637 https://cve.radiocsirt.org/vuln/bdu:2024-08637 bdu:2024-08637 https://cve.radiocsirt.org/vuln/bdu:2024-08637 BELL-CVE-2024-26741 https://cve.radiocsirt.org/vuln/bell-cve-2024-26741 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-26741 certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans <span class="textit">le noyau Linux de Debian</span>. Elles permet… https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334 certfr-2024-avi-0334 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334 EUVD-2026-312581 https://cve.radiocsirt.org/vuln/euvd-2026-312581 EUVD-2026-312581 https://cve.radiocsirt.org/vuln/euvd-2026-312581 fkie_cve-2024-26741 https://cve.radiocsirt.org/vuln/fkie_cve-2024-26741 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().</p> <p>syzkaller reported a warning [0] in inet_csk_destroy_sock() with no repro.</p> <p>WARN_ON(inet_sk(sk)->inet_num && !inet_csk(sk)->icsk_bind_hash);</p> <p>However, the syzkaller's log hinted that connect() failed just before the warning due to FAULT_INJECTION. [1]</p> <p>When connect() is called for an unbound socket, we search for an available ephemeral port. If a bhash bucket exists for the port, we call __inet_check_established() or __inet6_check_established() to check if the bucket is reusable.</p> <p>If reusable, we add the socket into ehash and set inet_sk(sk)->inet_num.</p> <p>Later, we look up the corresponding bhash2 bucket and try to allocate it if it does not exist.</p> <p>Although it rarely occurs in real use, if the allocation fails, we must revert the changes by check_established(). Otherwise, an unconnected socket could illegally occupy an ehash entry.</p> <p>Note that we do not put tw back into ehash because sk might have already responded to a packet for tw and it would be better to free tw earlier under such memory presure.</p> <p>[0]: WARNING: CPU: 0 PID: 350830 at net/ipv4/inet_connection_sock.c:1193 inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:1193) Modules linked in: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:inet_csk_destroy_sock (net/ipv4/inet_connection_…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().</p> <p>syzkaller reported a warning [0] in inet_csk_destroy_sock() with no repro.</p> <p>WARN_ON(inet_sk(sk)->inet_num && !inet_csk(sk)->icsk_bind_hash);</p> <p>However, the syzkaller's log hinted that connect() failed just before the warning due to FAULT_INJECTION. [1]</p> <p>When connect() is called for an unbound socket, we search for an available ephemeral port. If a bhash bucket exists for the port, we call __inet_check_established() or __inet6_check_established() to check if the bucket is reusable.</p> <p>If reusable, we add the socket into ehash and set inet_sk(sk)->inet_num.</p> <p>Later, we look up the corresponding bhash2 bucket and try to allocate it if it does not exist.</p> <p>Although it rarely occurs in real use, if the allocation fails, we must revert the changes by check_established(). Otherwise, an unconnected socket could illegally occupy an ehash entry.</p> <p>Note that we do not put tw back into ehash because sk might have already responded to a packet for tw and it would be better to free tw earlier under such memory presure.</p> <p>[0]: WARNING: CPU: 0 PID: 350830 at net/ipv4/inet_connection_sock.c:1193 inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:1193) Modules linked in: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:inet_csk_destroy_sock (net/ipv4/inet_connection_…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-26741 GHSA-x4x7-9mj3-h6gw https://cve.radiocsirt.org/vuln/ghsa-x4x7-9mj3-h6gw <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().</p> <p>syzkaller reported a warning [0] in inet_csk_destroy_sock() with no repro.</p> <p>WARN_ON(inet_sk(sk)->inet_num && !inet_csk(sk)->icsk_bind_hash);</p> <p>However, the syzkaller's log hinted that connect() failed just before the warning due to FAULT_INJECTION. [1]</p> <p>When connect() is called for an unbound socket, we search for an available ephemeral port. If a bhash bucket exists for the port, we call __inet_check_established() or __inet6_check_established() to check if the bucket is reusable.</p> <p>If reusable, we add the socket into ehash and set inet_sk(sk)->inet_num.</p> <p>Later, we look up the corresponding bhash2 bucket and try to allocate it if it does not exist.</p> <p>Although it rarely occurs in real use, if the allocation fails, we must revert the changes by check_established(). Otherwise, an unconnected socket could illegally occupy an ehash entry.</p> <p>Note that we do not put tw back into ehash because sk might have already responded to a packet for tw and it would be better to free tw earlier under such memory presure.</p> <p>[0]: WARNING: CPU: 0 PID: 350830 at net/ipv4/inet_connection_sock.c:1193 inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:1193) Modules linked in: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:inet_csk_destroy_sock (net/ipv4/inet_connection_…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished().</p> <p>syzkaller reported a warning [0] in inet_csk_destroy_sock() with no repro.</p> <p>WARN_ON(inet_sk(sk)->inet_num && !inet_csk(sk)->icsk_bind_hash);</p> <p>However, the syzkaller's log hinted that connect() failed just before the warning due to FAULT_INJECTION. [1]</p> <p>When connect() is called for an unbound socket, we search for an available ephemeral port. If a bhash bucket exists for the port, we call __inet_check_established() or __inet6_check_established() to check if the bucket is reusable.</p> <p>If reusable, we add the socket into ehash and set inet_sk(sk)->inet_num.</p> <p>Later, we look up the corresponding bhash2 bucket and try to allocate it if it does not exist.</p> <p>Although it rarely occurs in real use, if the allocation fails, we must revert the changes by check_established(). Otherwise, an unconnected socket could illegally occupy an ehash entry.</p> <p>Note that we do not put tw back into ehash because sk might have already responded to a packet for tw and it would be better to free tw earlier under such memory presure.</p> <p>[0]: WARNING: CPU: 0 PID: 350830 at net/ipv4/inet_connection_sock.c:1193 inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:1193) Modules linked in: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:inet_csk_destroy_sock (net/ipv4/inet_connection_…</p> https://cve.radiocsirt.org/vuln/ghsa-x4x7-9mj3-h6gw gsd-2024-26741 https://cve.radiocsirt.org/vuln/gsd-2024-26741 gsd-2024-26741 https://cve.radiocsirt.org/vuln/gsd-2024-26741 SUSE-SU-2024:4314-1 — Security update for the Linux Kernel https://cve.radiocsirt.org/vuln/suse-su-2024:4314-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:4314-1 UBUNTU-CVE-2024-26741 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26741 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished(). syzkaller reported a warning [0] in inet_csk_destroy_sock() with no repro. WARN_ON(inet_sk(sk)->inet_num && !inet_csk(sk)->icsk_bind_hash); However, the syzkaller's log hinted that connect() failed just before the warning due to FAULT_INJECTION. [1] When connect() is called for an unbound socket, we search for an available ephemeral port. If a bhash bucket exists for the port, we call __inet_check_established() or __inet6_check_established() to check if the bucket is reusable. If reusable, we add the socket into ehash and set inet_sk(sk)->inet_num. Later, we look up the corresponding bhash2 bucket and try to allocate it if it does not exist. Although it rarely occurs in real use, if the allocation fails, we must revert the changes by check_established(). Otherwise, an unconnected socket could illegally occupy an ehash entry. Note that we do not put tw back into ehash because sk might have already responded to a packet for tw and it would be better to free tw earlier under such memory presure. [0]: WARNING: CPU: 0 PID: 350830 at net/ipv4/inet_connection_sock.c:1193 inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:1193) Modules linked in: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:119…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: dccp/tcp: Unhash sk from ehash for tb2 alloc failure after check_estalblished(). syzkaller reported a warning [0] in inet_csk_destroy_sock() with no repro. WARN_ON(inet_sk(sk)->inet_num && !inet_csk(sk)->icsk_bind_hash); However, the syzkaller's log hinted that connect() failed just before the warning due to FAULT_INJECTION. [1] When connect() is called for an unbound socket, we search for an available ephemeral port. If a bhash bucket exists for the port, we call __inet_check_established() or __inet6_check_established() to check if the bucket is reusable. If reusable, we add the socket into ehash and set inet_sk(sk)->inet_num. Later, we look up the corresponding bhash2 bucket and try to allocate it if it does not exist. Although it rarely occurs in real use, if the allocation fails, we must revert the changes by check_established(). Otherwise, an unconnected socket could illegally occupy an ehash entry. Note that we do not put tw back into ehash because sk might have already responded to a packet for tw and it would be better to free tw earlier under such memory presure. [0]: WARNING: CPU: 0 PID: 350830 at net/ipv4/inet_connection_sock.c:1193 inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:1193) Modules linked in: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:inet_csk_destroy_sock (net/ipv4/inet_connection_sock.c:119…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26741 WID-SEC-W-2024-0773 — Linux Kernel: Mehrere Schwachstellen https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0773 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, seine Privilegien eskalieren oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, seine Privilegien eskalieren oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0773