https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T19:35:17.216770+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-00827 bdu:2025-00827 2026-10-03T19:35:17.400768+00:00 bdu:2025-00827 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0242 certfr-2024-avi-0242 — De multiples vulnérabilités ont été découvertes dans <span class="textit">le noyau Linux de SUSE</span>. Certaines d'en… 2026-10-03T19:35:17.400817+00:00 certfr-2024-avi-0242 https://cve.radiocsirt.org/vuln/euvd-2026-309460 EUVD-2026-309460 2026-10-03T19:35:17.400840+00:00 EUVD-2026-309460 https://cve.radiocsirt.org/vuln/fkie_cve-2021-46953 fkie_cve-2021-46953 2026-10-03T19:35:17.400852+00:00

In the Linux kernel, the following vulnerability has been resolved:

ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure

When failing the driver probe because of invalid firmware properties, the GTDT driver unmaps the interrupt that it mapped earlier.

However, it never checks whether the mapping of the interrupt actially succeeded. Even more, should the firmware report an illegal interrupt number that overlaps with the GIC SGI range, this can result in an IPI being unmapped, and subsequent fireworks (as reported by Dann Frazier).

Rework the driver to have a slightly saner behaviour and actually check whether the interrupt has been mapped before unmapping things.

 https://cve.radiocsirt.org/vuln/ghsa-2wwc-57w4-gp7m GHSA-2wwc-57w4-gp7m 2026-10-03T19:35:17.400889+00:00

In the Linux kernel, the following vulnerability has been resolved:

ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure

When failing the driver probe because of invalid firmware properties, the GTDT driver unmaps the interrupt that it mapped earlier.

However, it never checks whether the mapping of the interrupt actially succeeded. Even more, should the firmware report an illegal interrupt number that overlaps with the GIC SGI range, this can result in an IPI being unmapped, and subsequent fireworks (as reported by Dann Frazier).

Rework the driver to have a slightly saner behaviour and actually check whether the interrupt has been mapped before unmapping things.

 https://cve.radiocsirt.org/vuln/gsd-2021-46953 gsd-2021-46953 2026-10-03T19:35:17.400910+00:00 gsd-2021-46953 https://cve.radiocsirt.org/vuln/suse-su-2024:0856-1 SUSE-SU-2024:0856-1 — Security update for the Linux Kernel 2026-10-03T19:35:17.400922+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46953 UBUNTU-CVE-2021-46953 2026-10-03T19:35:17.400979+00:00

Affected: Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more

In the Linux kernel, the following vulnerability has been resolved: ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure When failing the driver probe because of invalid firmware properties, the GTDT driver unmaps the interrupt that it mapped earlier. However, it never checks whether the mapping of the interrupt actially succeeded. Even more, should the firmware report an illegal interrupt number that overlaps with the GIC SGI range, this can result in an IPI being unmapped, and subsequent fireworks (as reported by Dann Frazier). Rework the driver to have a slightly saner behaviour and actually check whether the interrupt has been mapped before unmapping things.