https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 21:15:23 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-98209 <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-2026-98209 https://cve.radiocsirt.org/vuln/euvd-2026-383320 EUVD-2026-383320 https://cve.radiocsirt.org/vuln/euvd-2026-383320 https://cve.radiocsirt.org/vuln/fkie_cve-2026-98209 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: sdhci-of-aspeed: Remove children before releasing SDC resources</p> <p>Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released.</p> <p>Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate().</p> <p>This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: sdhci-of-aspeed: Remove children before releasing SDC resources</p> <p>Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released.</p> <p>Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate().</p> <p>This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-98209 https://cve.radiocsirt.org/vuln/ghsa-q4rm-j75j-m3m8 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: sdhci-of-aspeed: Remove children before releasing SDC resources</p> <p>Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released.</p> <p>Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate().</p> <p>This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mmc: sdhci-of-aspeed: Remove children before releasing SDC resources</p> <p>Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released.</p> <p>Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate().</p> <p>This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> https://cve.radiocsirt.org/vuln/ghsa-q4rm-j75j-m3m8 https://cve.radiocsirt.org/vuln/msrc_cve-2026-98209 msrc_CVE-2026-98209 https://cve.radiocsirt.org/vuln/msrc_cve-2026-98209 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98209 <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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-of-aspeed: Remove children before releasing SDC resources Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released. Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate(). This issue was identified during our ongoing static-analysis research while reviewing kernel code.</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-of-aspeed: Remove children before releasing SDC resources Probe failure and removal leave SDHCI child devices registered after the parent clock and managed resources are released. Unregister the OF children in reverse order before disabling the parent clock on both paths. Use of_platform_device_destroy() because manual child creation does not set the flag required by of_platform_depopulate(). This issue was identified during our ongoing static-analysis research while reviewing kernel code.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98209