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:23:43 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-80797 <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-2026-80797 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163 certfr-2026-avi-1163 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163 https://cve.radiocsirt.org/vuln/euvd-2026-363815 EUVD-2026-363815 https://cve.radiocsirt.org/vuln/euvd-2026-363815 https://cve.radiocsirt.org/vuln/fkie_cve-2026-80797 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: pn533: purge fragmented skbs during cleanup</p> <p>pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded.</p> <p>If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them.</p> <p>Purge fragment_skb during cleanup alongside resp_q.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: pn533: purge fragmented skbs during cleanup</p> <p>pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded.</p> <p>If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them.</p> <p>Purge fragment_skb during cleanup alongside resp_q.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-80797 https://cve.radiocsirt.org/vuln/ghsa-4h9c-xj6x-wv3f <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: pn533: purge fragmented skbs during cleanup</p> <p>pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded.</p> <p>If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them.</p> <p>Purge fragment_skb during cleanup alongside resp_q.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>nfc: pn533: purge fragmented skbs during cleanup</p> <p>pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded.</p> <p>If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them.</p> <p>Purge fragment_skb during cleanup alongside resp_q.</p> https://cve.radiocsirt.org/vuln/ghsa-4h9c-xj6x-wv3f https://cve.radiocsirt.org/vuln/msrc_cve-2026-80797 msrc_CVE-2026-80797 https://cve.radiocsirt.org/vuln/msrc_cve-2026-80797 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1 <p>kernel-devel-7.2.5-1.1 on GA media</p> <p>kernel-devel-7.2.5-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80797 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: purge fragmented skbs during cleanup pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded. If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them. Purge fragment_skb during cleanup alongside resp_q.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: purge fragmented skbs during cleanup pn53x_common_clean() purges resp_q before freeing the common PN533 state, but it leaves fragment_skb untouched. The fragmentation helpers queue transmit fragments there while sending large initiator or target-mode frames, and those skbs remain owned by the driver until they are sent or discarded. If the device is removed while fragments are still queued, the common cleanup path frees the PN533 state without releasing the queued fragment skbs, leaking them. Purge fragment_skb during cleanup alongside resp_q.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80797 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211