https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:05:09 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-12243 bdu:2026-12243 https://cve.radiocsirt.org/vuln/bdu:2026-12243 https://cve.radiocsirt.org/vuln/bell-cve-2026-31435 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-31435 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0697 certfr-2026-avi-0697 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0697 https://cve.radiocsirt.org/vuln/euvd-2026-347679 EUVD-2026-347679 https://cve.radiocsirt.org/vuln/euvd-2026-347679 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31435 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix read abandonment during retry</p> <p>Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the &#39;subreq&#39; variable to be set to the place to start abandonment from, but it doesn&#39;t always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes).</p> <p>Fix the first jump to &#34;abandon:&#34; to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set).</p> <p>Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix read abandonment during retry</p> <p>Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the &#39;subreq&#39; variable to be set to the place to start abandonment from, but it doesn&#39;t always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes).</p> <p>Fix the first jump to &#34;abandon:&#34; to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set).</p> <p>Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-31435 https://cve.radiocsirt.org/vuln/ghsa-qfvq-ggc7-jqgw <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix read abandonment during retry</p> <p>Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the &#39;subreq&#39; variable to be set to the place to start abandonment from, but it doesn&#39;t always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes).</p> <p>Fix the first jump to &#34;abandon:&#34; to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set).</p> <p>Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix read abandonment during retry</p> <p>Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the &#39;subreq&#39; variable to be set to the place to start abandonment from, but it doesn&#39;t always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes).</p> <p>Fix the first jump to &#34;abandon:&#34; to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set).</p> <p>Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.</p> https://cve.radiocsirt.org/vuln/ghsa-qfvq-ggc7-jqgw https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20826-1 https://cve.radiocsirt.org/vuln/suse-su-2026:21834-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:21834-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31435 <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 106 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: netfs: Fix read abandonment during retry Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the &#39;subreq&#39; variable to be set to the place to start abandonment from, but it doesn&#39;t always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes). Fix the first jump to &#34;abandon:&#34; to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set). Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.</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 106 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: netfs: Fix read abandonment during retry Under certain circumstances, all the remaining subrequests from a read request will get abandoned during retry. The abandonment process expects the &#39;subreq&#39; variable to be set to the place to start abandonment from, but it doesn&#39;t always have a useful value (it will be uninitialised on the first pass through the loop and it may point to a deleted subrequest on later passes). Fix the first jump to &#34;abandon:&#34; to set subreq to the start of the first subrequest expected to need retry (which, in this abandonment case, turned out unexpectedly to no longer have NEED_RETRY set). Also clear the subreq pointer after discarding superfluous retryable subrequests to cause an oops if we do try to access it.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31435 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1252 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1252