https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:27:53 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-64516 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2026-64516 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0954 certfr-2026-avi-0954 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0954 https://cve.radiocsirt.org/vuln/euvd-2026-348456 EUVD-2026-348456 https://cve.radiocsirt.org/vuln/euvd-2026-348456 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64516 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets</p> <p>The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.</p> <p>Make sure the stack and data offsets are aligned to the 32K TLB size.</p> <p>Check that the FW microcode actually fits in the space that is reserved for it.</p> <p>(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets</p> <p>The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.</p> <p>Make sure the stack and data offsets are aligned to the 32K TLB size.</p> <p>Check that the FW microcode actually fits in the space that is reserved for it.</p> <p>(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-64516 https://cve.radiocsirt.org/vuln/ghsa-q3hq-vwmg-m826 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets</p> <p>The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.</p> <p>Make sure the stack and data offsets are aligned to the 32K TLB size.</p> <p>Check that the FW microcode actually fits in the space that is reserved for it.</p> <p>(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets</p> <p>The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.</p> <p>Make sure the stack and data offsets are aligned to the 32K TLB size.</p> <p>Check that the FW microcode actually fits in the space that is reserved for it.</p> <p>(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)</p> https://cve.radiocsirt.org/vuln/ghsa-q3hq-vwmg-m826 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64516 <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 111 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access. Make sure the stack and data offsets are aligned to the 32K TLB size. Check that the FW microcode actually fits in the space that is reserved for it. (cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)</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 111 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access. Make sure the stack and data offsets are aligned to the 32K TLB size. Check that the FW microcode actually fits in the space that is reserved for it. (cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64516 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