https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 16:03:30 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-03935 bdu:2024-03935 https://cve.radiocsirt.org/vuln/bdu:2024-03935 https://cve.radiocsirt.org/vuln/bell-cve-2024-27400 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-27400 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496 certfr-2024-avi-0496 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496 https://cve.radiocsirt.org/vuln/euvd-2026-345631 EUVD-2026-345631 https://cve.radiocsirt.org/vuln/euvd-2026-345631 https://cve.radiocsirt.org/vuln/fkie_cve-2024-27400 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2</p> <p>This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more.</p> <p>Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well.</p> <p>Also rework the statistic handling so that we don&#39;t update the eviction counter before the move.</p> <p>v2: add missing NULL check</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2</p> <p>This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more.</p> <p>Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well.</p> <p>Also rework the statistic handling so that we don&#39;t update the eviction counter before the move.</p> <p>v2: add missing NULL check</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-27400 https://cve.radiocsirt.org/vuln/ghsa-ww8p-33xg-gvhc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2</p> <p>This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more.</p> <p>Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well.</p> <p>Also rework the statistic handling so that we don&#39;t update the eviction counter before the move.</p> <p>v2: add missing NULL check</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2</p> <p>This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more.</p> <p>Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well.</p> <p>Also rework the statistic handling so that we don&#39;t update the eviction counter before the move.</p> <p>v2: add missing NULL check</p> https://cve.radiocsirt.org/vuln/ghsa-ww8p-33xg-gvhc https://cve.radiocsirt.org/vuln/gsd-2024-27400 gsd-2024-27400 https://cve.radiocsirt.org/vuln/gsd-2024-27400 https://cve.radiocsirt.org/vuln/msrc_cve-2024-27400 msrc_CVE-2024-27400 https://cve.radiocsirt.org/vuln/msrc_cve-2024-27400 https://cve.radiocsirt.org/vuln/suse-su-2024:2008-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:2008-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-27400 <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 127 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2 This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more. Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well. Also rework the statistic handling so that we don&#39;t update the eviction counter before the move. v2: add missing NULL check</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 127 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2 This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move on same heap. The basic problem here is that after the move the old location is simply not available any more. Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well. Also rework the statistic handling so that we don&#39;t update the eviction counter before the move. v2: add missing NULL check</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-27400 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1108 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1108