https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 05:06:05 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04475 bdu:2026-04475 https://cve.radiocsirt.org/vuln/bdu:2026-04475 https://cve.radiocsirt.org/vuln/bell-cve-2025-38076 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-38076 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0828 certfr-2025-avi-0828 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0828 https://cve.radiocsirt.org/vuln/euvd-2026-314414 EUVD-2026-314414 https://cve.radiocsirt.org/vuln/euvd-2026-314414 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38076 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>alloc_tag: allocate percpu counters for module tags dynamically</p> <p>When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module&#39;s allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded.</p> <p>To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>alloc_tag: allocate percpu counters for module tags dynamically</p> <p>When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module&#39;s allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded.</p> <p>To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-38076 https://cve.radiocsirt.org/vuln/ghsa-px9x-jp5p-m4g4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>alloc_tag: allocate percpu counters for module tags dynamically</p> <p>When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module&#39;s allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded.</p> <p>To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>alloc_tag: allocate percpu counters for module tags dynamically</p> <p>When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module&#39;s allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded.</p> <p>To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.</p> https://cve.radiocsirt.org/vuln/ghsa-px9x-jp5p-m4g4 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38076 <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 79 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: alloc_tag: allocate percpu counters for module tags dynamically When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module&#39;s allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded. To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.</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 79 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: alloc_tag: allocate percpu counters for module tags dynamically When a module gets unloaded it checks whether any of its tags are still in use and if so, we keep the memory containing module&#39;s allocation tags alive until all tags are unused. However percpu counters referenced by the tags are freed by free_module(). This will lead to UAF if the memory allocated by a module is accessed after module was unloaded. To fix this we allocate percpu counters for module allocation tags dynamically and we keep it alive for tags which are still in use after module unloading. This also removes the requirement of a larger PERCPU_MODULE_RESERVE when memory allocation profiling is enabled because percpu memory for counters does not need to be reserved anymore.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38076 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1350