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:37:08 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-98155 <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-98155 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/euvd-2026-375859 EUVD-2026-375859 https://cve.radiocsirt.org/vuln/euvd-2026-375859 https://cve.radiocsirt.org/vuln/fkie_cve-2026-98155 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>accel/qaic: Address potential out-of-bounds read in resp_worker()</p> <p>Although &#39;commit 2feec5ae5df7 (&#34;accel/qaic: Handle DBC deactivation if the owner went away&#34;)&#39; fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation&#39;s end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device.</p> <p>Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>accel/qaic: Address potential out-of-bounds read in resp_worker()</p> <p>Although &#39;commit 2feec5ae5df7 (&#34;accel/qaic: Handle DBC deactivation if the owner went away&#34;)&#39; fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation&#39;s end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device.</p> <p>Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-98155 https://cve.radiocsirt.org/vuln/ghsa-fp97-66mw-5q4h <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>accel/qaic: Address potential out-of-bounds read in resp_worker()</p> <p>Although &#39;commit 2feec5ae5df7 (&#34;accel/qaic: Handle DBC deactivation if the owner went away&#34;)&#39; fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation&#39;s end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device.</p> <p>Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>accel/qaic: Address potential out-of-bounds read in resp_worker()</p> <p>Although &#39;commit 2feec5ae5df7 (&#34;accel/qaic: Handle DBC deactivation if the owner went away&#34;)&#39; fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation&#39;s end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device.</p> <p>Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().</p> https://cve.radiocsirt.org/vuln/ghsa-fp97-66mw-5q4h https://cve.radiocsirt.org/vuln/msrc_cve-2026-98155 msrc_CVE-2026-98155 https://cve.radiocsirt.org/vuln/msrc_cve-2026-98155 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98155 <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 152 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Address potential out-of-bounds read in resp_worker() Although &#39;commit 2feec5ae5df7 (&#34;accel/qaic: Handle DBC deactivation if the owner went away&#34;)&#39; fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation&#39;s end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device. Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().</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 152 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Address potential out-of-bounds read in resp_worker() Although &#39;commit 2feec5ae5df7 (&#34;accel/qaic: Handle DBC deactivation if the owner went away&#34;)&#39; fixes the scenario it was intended for by walking the message and only decoding QAIC_TRANS_DEACTIVATE_FROM_DEV, if present, it skipped over the bounds checking code that is included in decode_message(). This could lead to issues such as reading past the slab allocation&#39;s end, infinite loops or kernel panics. For those issues to happen, a malformed wire message is needed to be sent from the device. Instead of duplicating the bounds checking code already present in decode_message(), use the function inside resp_worker().</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98155 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3579 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3579