https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:26:12 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-04614 bdu:2026-04614 https://cve.radiocsirt.org/vuln/bdu:2026-04614 https://cve.radiocsirt.org/vuln/bell-cve-2023-53276 <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-2023-53276 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895 https://cve.radiocsirt.org/vuln/euvd-2026-311945 EUVD-2026-311945 https://cve.radiocsirt.org/vuln/euvd-2026-311945 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53276 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ubifs: Free memory for tmpfile name</p> <p>When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed.</p> <p>When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;tmpfile&#39; just opening a tmpfile:</p> <p>unreferenced object 0xffff88810178f380 (size 32): comm &#34;tmpfile&#34;, pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat</p> <p>Free this memory after it has been copied to the inode.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ubifs: Free memory for tmpfile name</p> <p>When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed.</p> <p>When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;tmpfile&#39; just opening a tmpfile:</p> <p>unreferenced object 0xffff88810178f380 (size 32): comm &#34;tmpfile&#34;, pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat</p> <p>Free this memory after it has been copied to the inode.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-53276 https://cve.radiocsirt.org/vuln/ghsa-jfrm-9rr7-r45w <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ubifs: Free memory for tmpfile name</p> <p>When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed.</p> <p>When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;tmpfile&#39; just opening a tmpfile:</p> <p>unreferenced object 0xffff88810178f380 (size 32): comm &#34;tmpfile&#34;, pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat</p> <p>Free this memory after it has been copied to the inode.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ubifs: Free memory for tmpfile name</p> <p>When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed.</p> <p>When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;tmpfile&#39; just opening a tmpfile:</p> <p>unreferenced object 0xffff88810178f380 (size 32): comm &#34;tmpfile&#34;, pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat</p> <p>Free this memory after it has been copied to the inode.</p> https://cve.radiocsirt.org/vuln/ghsa-jfrm-9rr7-r45w https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:03615-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53276 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 163 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;tmpfile&#39; just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm &#34;tmpfile&#34;, pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 163 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;tmpfile&#39; just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm &#34;tmpfile&#34;, pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53276 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053