https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 04:04:59 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-08522 bdu:2026-08522 https://cve.radiocsirt.org/vuln/bdu:2026-08522 https://cve.radiocsirt.org/vuln/bell-cve-2026-43502 <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-43502 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862 certfr-2026-avi-0862 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862 https://cve.radiocsirt.org/vuln/euvd-2026-368362 EUVD-2026-368362 https://cve.radiocsirt.org/vuln/euvd-2026-368362 https://cve.radiocsirt.org/vuln/fkie_cve-2026-43502 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/rds: handle zerocopy send cleanup before the message is queued</p> <p>A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket.</p> <p>The purge path currently infers zerocopy state from rm-&gt;m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue.</p> <p>Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages.</p> <p>This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/rds: handle zerocopy send cleanup before the message is queued</p> <p>A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket.</p> <p>The purge path currently infers zerocopy state from rm-&gt;m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue.</p> <p>Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages.</p> <p>This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-43502 https://cve.radiocsirt.org/vuln/ghsa-mhq7-fqmq-29pq <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/rds: handle zerocopy send cleanup before the message is queued</p> <p>A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket.</p> <p>The purge path currently infers zerocopy state from rm-&gt;m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue.</p> <p>Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages.</p> <p>This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/rds: handle zerocopy send cleanup before the message is queued</p> <p>A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket.</p> <p>The purge path currently infers zerocopy state from rm-&gt;m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue.</p> <p>Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages.</p> <p>This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.</p> https://cve.radiocsirt.org/vuln/ghsa-mhq7-fqmq-29pq https://cve.radiocsirt.org/vuln/msrc_cve-2026-43502 msrc_CVE-2026-43502 https://cve.radiocsirt.org/vuln/msrc_cve-2026-43502 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10859-1 <p>kernel-devel-7.0.10-1.1 on GA media</p> <p>kernel-devel-7.0.10-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10859-1 https://cve.radiocsirt.org/vuln/suse-su-2026:22521-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:22521-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43502 <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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 226 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm-&gt;m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 226 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm-&gt;m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43502 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1656 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um seine Privilegien zu eskalieren oder nicht näher spezifizierte Angriffe durchzuführen, darunter möglicherweise Denial-of-Service-Angriffe, Speicherbeschädigungen oder die Offenlegung von Informationen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um seine Privilegien zu eskalieren oder nicht näher spezifizierte Angriffe durchzuführen, darunter möglicherweise Denial-of-Service-Angriffe, Speicherbeschädigungen oder die Offenlegung von Informationen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1656