https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 01:43:19 +0000 https://vulnerability.circl.lu/vuln/bdu:2026-12730 bdu:2026-12730 https://vulnerability.circl.lu/vuln/bdu:2026-12730 https://vulnerability.circl.lu/vuln/bell-cve-2026-43098 <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://vulnerability.circl.lu/vuln/bell-cve-2026-43098 https://vulnerability.circl.lu/vuln/certfr-2026-avi-0862 certfr-2026-avi-0862 https://vulnerability.circl.lu/vuln/certfr-2026-avi-0862 https://vulnerability.circl.lu/vuln/fkie_cve-2026-43098 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: s3fwrn5: allocate rx skb before consuming bytes</p> <p>s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete frame before allocating a fresh receive buffer.</p> <p>If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8().</p> <p>Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: s3fwrn5: allocate rx skb before consuming bytes</p> <p>s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete frame before allocating a fresh receive buffer.</p> <p>If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8().</p> <p>Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-43098 https://vulnerability.circl.lu/vuln/ghsa-qjxf-6753-vc9p <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: s3fwrn5: allocate rx skb before consuming bytes</p> <p>s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete frame before allocating a fresh receive buffer.</p> <p>If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8().</p> <p>Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: s3fwrn5: allocate rx skb before consuming bytes</p> <p>s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete frame before allocating a fresh receive buffer.</p> <p>If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8().</p> <p>Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.</p> https://vulnerability.circl.lu/vuln/ghsa-qjxf-6753-vc9p https://vulnerability.circl.lu/vuln/opensuse-su-2026:21555-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:21555-1 https://vulnerability.circl.lu/vuln/suse-su-2026:23066-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://vulnerability.circl.lu/vuln/suse-su-2026:23066-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-43098 <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 182 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: s3fwrn5: allocate rx skb before consuming bytes s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete frame before allocating a fresh receive buffer. If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8(). Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.</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 182 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: s3fwrn5: allocate rx skb before consuming bytes s3fwrn82_uart_read() reports the number of accepted bytes to the serdev core. The current code consumes bytes into recv_skb and may already deliver a complete frame before allocating a fresh receive buffer. If that alloc_skb() fails, the callback returns 0 even though it has already consumed bytes, and it leaves recv_skb as NULL for the next receive callback. That breaks the receive_buf() accounting contract and can also lead to a NULL dereference on the next skb_put_u8(). Allocate the receive skb lazily before consuming the next byte instead. If allocation fails, return the number of bytes already accepted.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-43098 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-1385 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-1385