https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:34:32 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-64251 <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-64251 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/euvd-2026-353170 EUVD-2026-353170 https://cve.radiocsirt.org/vuln/euvd-2026-353170 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64251 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()</p> <p>pwrseq_debugfs_seq_next() declares &#39;next&#39; with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped.</p> <p>Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&amp;pwrseq_sem) and never releases the device reference.</p> <p>Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI:</p> <p>- start(): use get_device() so it returns a referenced pointer. - next(): explicitly put_device(curr) to release the previous device&#39;s reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL). - stop(): put_device(data) to release the last iterated device&#39;s reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()</p> <p>pwrseq_debugfs_seq_next() declares &#39;next&#39; with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped.</p> <p>Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&amp;pwrseq_sem) and never releases the device reference.</p> <p>Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI:</p> <p>- start(): use get_device() so it returns a referenced pointer. - next(): explicitly put_device(curr) to release the previous device&#39;s reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL). - stop(): put_device(data) to release the last iterated device&#39;s reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-64251 https://cve.radiocsirt.org/vuln/ghsa-4mm9-h7gj-362g <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()</p> <p>pwrseq_debugfs_seq_next() declares &#39;next&#39; with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped.</p> <p>Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&amp;pwrseq_sem) and never releases the device reference.</p> <p>Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI:</p> <p>- start(): use get_device() so it returns a referenced pointer. - next(): explicitly put_device(curr) to release the previous device&#39;s reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL). - stop(): put_device(data) to release the last iterated device&#39;s reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()</p> <p>pwrseq_debugfs_seq_next() declares &#39;next&#39; with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped.</p> <p>Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&amp;pwrseq_sem) and never releases the device reference.</p> <p>Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI:</p> <p>- start(): use get_device() so it returns a referenced pointer. - next(): explicitly put_device(curr) to release the previous device&#39;s reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL). - stop(): put_device(data) to release the last iterated device&#39;s reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.</p> https://cve.radiocsirt.org/vuln/ghsa-4mm9-h7gj-362g https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1 <p>kernel-devel-7.1.7-1.1 on GA media</p> <p>kernel-devel-7.1.7-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11476-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64251 <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 119 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() pwrseq_debugfs_seq_next() declares &#39;next&#39; with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped. Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&amp;pwrseq_sem) and never releases the device reference. Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI: - start(): use get_device() so it returns a referenced pointer. - next(): explicitly put_device(curr) to release the previous device&#39;s reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL). - stop(): put_device(data) to release the last iterated device&#39;s reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.</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 119 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() pwrseq_debugfs_seq_next() declares &#39;next&#39; with __free(put_device), which causes put_device() to be called on the returned pointer when the variable goes out of scope. This results in a use-after-free since the seq_file framework receives a pointer whose reference has already been dropped. Simply removing __free(put_device) would fix the UAF but would leak the reference acquired by bus_find_next_device(), as stop() only calls up_read(&amp;pwrseq_sem) and never releases the device reference. Fix this by making the reference counting consistent across all seq_file callbacks, matching the standard pattern used by PCI and SCSI: - start(): use get_device() so it returns a referenced pointer. - next(): explicitly put_device(curr) to release the previous device&#39;s reference (no NULL check needed - the seq_file framework only calls next() while the previous return was non-NULL). - stop(): put_device(data) to release the last iterated device&#39;s reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64251 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2527 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2527