https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:51:53 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-13236 bdu:2026-13236 https://cve.radiocsirt.org/vuln/bdu:2026-13236 https://cve.radiocsirt.org/vuln/bell-cve-2025-71272 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-71272 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/euvd-2026-315255 EUVD-2026-315255 https://cve.radiocsirt.org/vuln/euvd-2026-315255 https://cve.radiocsirt.org/vuln/fkie_cve-2025-71272 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>most: core: fix resource leak in most_register_interface error paths</p> <p>The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface.</p> <p>Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths.</p> <p>The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller.</p> <p>Switch to using device_add() instead of device_register() to handle the split initialization.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>most: core: fix resource leak in most_register_interface error paths</p> <p>The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface.</p> <p>Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths.</p> <p>The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller.</p> <p>Switch to using device_add() instead of device_register() to handle the split initialization.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-71272 https://cve.radiocsirt.org/vuln/ghsa-hgp5-3fhg-p5cf <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>most: core: fix resource leak in most_register_interface error paths</p> <p>The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface.</p> <p>Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths.</p> <p>The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller.</p> <p>Switch to using device_add() instead of device_register() to handle the split initialization.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>most: core: fix resource leak in most_register_interface error paths</p> <p>The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface.</p> <p>Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths.</p> <p>The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller.</p> <p>Switch to using device_add() instead of device_register() to handle the split initialization.</p> https://cve.radiocsirt.org/vuln/ghsa-hgp5-3fhg-p5cf https://cve.radiocsirt.org/vuln/msrc_cve-2025-71272 msrc_CVE-2025-71272 https://cve.radiocsirt.org/vuln/msrc_cve-2025-71272 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71272 <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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: most: core: fix resource leak in most_register_interface error paths The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface. Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths. The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller. Switch to using device_add() instead of device_register() to handle the split initialization.</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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: most: core: fix resource leak in most_register_interface error paths The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface. Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths. The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller. Switch to using device_add() instead of device_register() to handle the split initialization.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71272 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1405