https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 10:57:37 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-09409 bdu:2026-09409 https://cve.radiocsirt.org/vuln/bdu:2026-09409 https://cve.radiocsirt.org/vuln/bell-cve-2024-38592 <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-2024-38592 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0632 certfr-2024-avi-0632 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0632 https://cve.radiocsirt.org/vuln/euvd-2026-345824 EUVD-2026-345824 https://cve.radiocsirt.org/vuln/euvd-2026-345824 https://cve.radiocsirt.org/vuln/fkie_cve-2024-38592 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/mediatek: Init `ddp_comp` with devm_kcalloc()</p> <p>In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn&#39;t reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0.</p> <p>It really doesn&#39;t hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it&#39;s suggested to only use the non-initting alloc functions if you really need to.</p> <p>Let&#39;s switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/mediatek: Init `ddp_comp` with devm_kcalloc()</p> <p>In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn&#39;t reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0.</p> <p>It really doesn&#39;t hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it&#39;s suggested to only use the non-initting alloc functions if you really need to.</p> <p>Let&#39;s switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-38592 https://cve.radiocsirt.org/vuln/ghsa-9mq7-fm24-r296 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/mediatek: Init `ddp_comp` with devm_kcalloc()</p> <p>In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn&#39;t reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0.</p> <p>It really doesn&#39;t hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it&#39;s suggested to only use the non-initting alloc functions if you really need to.</p> <p>Let&#39;s switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/mediatek: Init `ddp_comp` with devm_kcalloc()</p> <p>In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn&#39;t reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0.</p> <p>It really doesn&#39;t hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it&#39;s suggested to only use the non-initting alloc functions if you really need to.</p> <p>Let&#39;s switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.</p> https://cve.radiocsirt.org/vuln/ghsa-9mq7-fm24-r296 https://cve.radiocsirt.org/vuln/suse-su-2024:2571-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:2571-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-38592 <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 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Init `ddp_comp` with devm_kcalloc() In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn&#39;t reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0. It really doesn&#39;t hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it&#39;s suggested to only use the non-initting alloc functions if you really need to. Let&#39;s switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.</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 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Init `ddp_comp` with devm_kcalloc() In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn&#39;t reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0. It really doesn&#39;t hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it&#39;s suggested to only use the non-initting alloc functions if you really need to. Let&#39;s switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-38592 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418