https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 22:38:53 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-14067 bdu:2026-14067 https://cve.radiocsirt.org/vuln/bdu:2026-14067 https://cve.radiocsirt.org/vuln/bell-cve-2026-53261 <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-2026-53261 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/euvd-2026-330107 EUVD-2026-330107 https://cve.radiocsirt.org/vuln/euvd-2026-330107 https://cve.radiocsirt.org/vuln/fkie_cve-2026-53261 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>devlink: Release nested relation on devlink free</p> <p>devlink relation state is normally released from devl_unregister(), which calls devlink_rel_put(). This misses devlink instances that get a nested relation before registration and then fail probe before devl_register() is reached.</p> <p>That flow can happen for SFs. The child devlink gets linked to its parent before registration, then a later probe error calls devlink_free() directly. Since the instance was never registered, devl_unregister() is not called and devlink-&gt;rel is leaked.</p> <p>Release any pending relation from devlink_free() as well. The registered path is unchanged because devl_unregister() already clears devlink-&gt;rel before devlink_free() runs.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>devlink: Release nested relation on devlink free</p> <p>devlink relation state is normally released from devl_unregister(), which calls devlink_rel_put(). This misses devlink instances that get a nested relation before registration and then fail probe before devl_register() is reached.</p> <p>That flow can happen for SFs. The child devlink gets linked to its parent before registration, then a later probe error calls devlink_free() directly. Since the instance was never registered, devl_unregister() is not called and devlink-&gt;rel is leaked.</p> <p>Release any pending relation from devlink_free() as well. The registered path is unchanged because devl_unregister() already clears devlink-&gt;rel before devlink_free() runs.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-53261 https://cve.radiocsirt.org/vuln/ghsa-q96w-jfjr-xww5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>devlink: Release nested relation on devlink free</p> <p>devlink relation state is normally released from devl_unregister(), which calls devlink_rel_put(). This misses devlink instances that get a nested relation before registration and then fail probe before devl_register() is reached.</p> <p>That flow can happen for SFs. The child devlink gets linked to its parent before registration, then a later probe error calls devlink_free() directly. Since the instance was never registered, devl_unregister() is not called and devlink-&gt;rel is leaked.</p> <p>Release any pending relation from devlink_free() as well. The registered path is unchanged because devl_unregister() already clears devlink-&gt;rel before devlink_free() runs.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>devlink: Release nested relation on devlink free</p> <p>devlink relation state is normally released from devl_unregister(), which calls devlink_rel_put(). This misses devlink instances that get a nested relation before registration and then fail probe before devl_register() is reached.</p> <p>That flow can happen for SFs. The child devlink gets linked to its parent before registration, then a later probe error calls devlink_free() directly. Since the instance was never registered, devl_unregister() is not called and devlink-&gt;rel is leaked.</p> <p>Release any pending relation from devlink_free() as well. The registered path is unchanged because devl_unregister() already clears devlink-&gt;rel before devlink_free() runs.</p> https://cve.radiocsirt.org/vuln/ghsa-q96w-jfjr-xww5 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53261 <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 163 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: devlink: Release nested relation on devlink free devlink relation state is normally released from devl_unregister(), which calls devlink_rel_put(). This misses devlink instances that get a nested relation before registration and then fail probe before devl_register() is reached. That flow can happen for SFs. The child devlink gets linked to its parent before registration, then a later probe error calls devlink_free() directly. Since the instance was never registered, devl_unregister() is not called and devlink-&gt;rel is leaked. Release any pending relation from devlink_free() as well. The registered path is unchanged because devl_unregister() already clears devlink-&gt;rel before devlink_free() runs.</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 163 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: devlink: Release nested relation on devlink free devlink relation state is normally released from devl_unregister(), which calls devlink_rel_put(). This misses devlink instances that get a nested relation before registration and then fail probe before devl_register() is reached. That flow can happen for SFs. The child devlink gets linked to its parent before registration, then a later probe error calls devlink_free() directly. Since the instance was never registered, devl_unregister() is not called and devlink-&gt;rel is leaked. Release any pending relation from devlink_free() as well. The registered path is unchanged because devl_unregister() already clears devlink-&gt;rel before devlink_free() runs.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53261