https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T18:48:20.477848+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2024-03935 bdu:2024-03935 2026-10-03T18:48:21.325704+00:00 bdu:2024-03935 https://cve.radiocsirt.org/vuln/bell-cve-2024-27400 BELL-CVE-2024-27400 2026-10-03T18:48:21.325777+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496 certfr-2024-avi-0496 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-03T18:48:21.325811+00:00 certfr-2024-avi-0496 https://cve.radiocsirt.org/vuln/euvd-2026-345631 EUVD-2026-345631 2026-10-03T18:48:21.325829+00:00 EUVD-2026-345631 https://cve.radiocsirt.org/vuln/fkie_cve-2024-27400 fkie_cve-2024-27400 2026-10-03T18:48:21.325841+00:00

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't update the eviction counter before the move.

v2: add missing NULL check

 https://cve.radiocsirt.org/vuln/ghsa-ww8p-33xg-gvhc GHSA-ww8p-33xg-gvhc 2026-10-03T18:48:21.325872+00:00

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't update the eviction counter before the move.

v2: add missing NULL check

 https://cve.radiocsirt.org/vuln/gsd-2024-27400 gsd-2024-27400 2026-10-03T18:48:21.325893+00:00 gsd-2024-27400 https://cve.radiocsirt.org/vuln/msrc_cve-2024-27400 msrc_CVE-2024-27400 — drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2 2026-10-03T18:48:21.325904+00:00 msrc_CVE-2024-27400 https://cve.radiocsirt.org/vuln/suse-su-2024:2008-1 SUSE-SU-2024:2008-1 — Security update for the Linux Kernel 2026-10-03T18:48:21.325921+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-27400 UBUNTU-CVE-2024-27400 2026-10-03T18:48:21.326341+00:00

Affected: 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

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't update the eviction counter before the move. v2: add missing NULL check

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1108 WID-SEC-W-2024-1108 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T18:48:21.326513+00:00

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.