https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 22:07:41 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-13843 bdu:2026-13843 https://cve.radiocsirt.org/vuln/bdu:2026-13843 https://cve.radiocsirt.org/vuln/bell-cve-2026-46192 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-46192 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-327167 EUVD-2026-327167 https://cve.radiocsirt.org/vuln/euvd-2026-327167 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46192 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>spi: microchip-core-qspi: don&#39;t attempt to transmit during emulated read-only dual/quad operations</p> <p>The core will deal with reads by creating clock cycles itself, there&#39;s no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn&#39;t have a dedicated master-out line like MOSI in regular SPI. I&#39;m not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>spi: microchip-core-qspi: don&#39;t attempt to transmit during emulated read-only dual/quad operations</p> <p>The core will deal with reads by creating clock cycles itself, there&#39;s no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn&#39;t have a dedicated master-out line like MOSI in regular SPI. I&#39;m not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46192 https://cve.radiocsirt.org/vuln/ghsa-fg62-m4w4-qg3p <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>spi: microchip-core-qspi: don&#39;t attempt to transmit during emulated read-only dual/quad operations</p> <p>The core will deal with reads by creating clock cycles itself, there&#39;s no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn&#39;t have a dedicated master-out line like MOSI in regular SPI. I&#39;m not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>spi: microchip-core-qspi: don&#39;t attempt to transmit during emulated read-only dual/quad operations</p> <p>The core will deal with reads by creating clock cycles itself, there&#39;s no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn&#39;t have a dedicated master-out line like MOSI in regular SPI. I&#39;m not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.</p> https://cve.radiocsirt.org/vuln/ghsa-fg62-m4w4-qg3p https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 <p>kernel-devel-7.0.11-1.1 on GA media</p> <p>kernel-devel-7.0.11-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46192 <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 124 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: don&#39;t attempt to transmit during emulated read-only dual/quad operations The core will deal with reads by creating clock cycles itself, there&#39;s no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn&#39;t have a dedicated master-out line like MOSI in regular SPI. I&#39;m not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.</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 124 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core-qspi: don&#39;t attempt to transmit during emulated read-only dual/quad operations The core will deal with reads by creating clock cycles itself, there&#39;s no need to generate clock cycles by transmitting garbage data at the driver level. Further, transmitting garbage data just bricks the transfer since QSPI doesn&#39;t have a dedicated master-out line like MOSI in regular SPI. I&#39;m not entirely sure if the transfer is bricked because of the garbage data being transmitted on the bus or because the core loses track of whether it is supposed to be sending or receiving data.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46192 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700