https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 19 Oct 2026 14:06:00 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-98850 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/packet: prevent TX_RING byte count overflow</p> <p>tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.</p> <p>After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.</p> <p>Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.</p> <p>A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/packet: prevent TX_RING byte count overflow</p> <p>tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.</p> <p>After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.</p> <p>Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.</p> <p>A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98850 https://db.gcve.eu/vuln/ghsa-prpm-w567-3rvc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/packet: prevent TX_RING byte count overflow</p> <p>tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.</p> <p>After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.</p> <p>Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.</p> <p>A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/packet: prevent TX_RING byte count overflow</p> <p>tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.</p> <p>After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.</p> <p>Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.</p> <p>A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.</p> https://db.gcve.eu/vuln/ghsa-prpm-w567-3rvc