https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 21:59:41 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-04441 bdu:2025-04441 https://cve.radiocsirt.org/vuln/bdu:2025-04441 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693 certfr-2024-avi-0693 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693 https://cve.radiocsirt.org/vuln/euvd-2026-310161 EUVD-2026-310161 https://cve.radiocsirt.org/vuln/euvd-2026-310161 https://cve.radiocsirt.org/vuln/fkie_cve-2022-48809 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: fix a memleak when uncloning an skb dst and its metadata</p> <p>When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb.</p> <p>The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak.</p> <p>Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: fix a memleak when uncloning an skb dst and its metadata</p> <p>When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb.</p> <p>The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak.</p> <p>Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-48809 https://cve.radiocsirt.org/vuln/ghsa-7jv7-gr8j-4554 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: fix a memleak when uncloning an skb dst and its metadata</p> <p>When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb.</p> <p>The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak.</p> <p>Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net: fix a memleak when uncloning an skb dst and its metadata</p> <p>When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb.</p> <p>The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak.</p> <p>Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.</p> https://cve.radiocsirt.org/vuln/ghsa-7jv7-gr8j-4554 https://cve.radiocsirt.org/vuln/suse-su-2024:2894-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:2894-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48809 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 113 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: fix a memleak when uncloning an skb dst and its metadata When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb. The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak. Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws and 113 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: net: fix a memleak when uncloning an skb dst and its metadata When uncloning an skb dst and its associated metadata, a new dst+metadata is allocated and later replaces the old one in the skb. This is helpful to have a non-shared dst+metadata attached to a specific skb. The issue is the uncloned dst+metadata is initialized with a refcount of 1, which is increased to 2 before attaching it to the skb. When tun_dst_unclone returns, the dst+metadata is only referenced from a single place (the skb) while its refcount is 2. Its refcount will never drop to 0 (when the skb is consumed), leading to a memory leak. Fix this by removing the call to dst_hold in tun_dst_unclone, as the dst+metadata refcount is already 1.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48809 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein 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-1625