https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 20:50:19 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-11837 bdu:2025-11837 https://cve.radiocsirt.org/vuln/bdu:2025-11837 https://cve.radiocsirt.org/vuln/bell-cve-2025-37978 <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-2025-37978 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529 certfr-2025-avi-0529 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0529 https://cve.radiocsirt.org/vuln/euvd-2026-314350 EUVD-2026-314350 https://cve.radiocsirt.org/vuln/euvd-2026-314350 https://cve.radiocsirt.org/vuln/fkie_cve-2025-37978 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: integrity: Do not call set_page_dirty_lock()</p> <p>Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can&#39;t be called from interrupt context.</p> <p>Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: integrity: Do not call set_page_dirty_lock()</p> <p>Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can&#39;t be called from interrupt context.</p> <p>Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-37978 https://cve.radiocsirt.org/vuln/ghsa-rvfv-rwmv-g73v <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: integrity: Do not call set_page_dirty_lock()</p> <p>Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can&#39;t be called from interrupt context.</p> <p>Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: integrity: Do not call set_page_dirty_lock()</p> <p>Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can&#39;t be called from interrupt context.</p> <p>Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().</p> https://cve.radiocsirt.org/vuln/ghsa-rvfv-rwmv-g73v https://cve.radiocsirt.org/vuln/suse-su-2025:01964-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:01964-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37978 <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 114 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: block: integrity: Do not call set_page_dirty_lock() Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can&#39;t be called from interrupt context. Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().</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 114 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: block: integrity: Do not call set_page_dirty_lock() Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can&#39;t be called from interrupt context. Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec().</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37978 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1114 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere nicht spezifizierte Angriffe durchzuführen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere nicht spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1114