https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T11:21:49.905144+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-92522 BELL-CVE-2026-92522 2026-10-04T11:21:49.925221+00:00

Affected: Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un… 2026-10-04T11:21:49.925293+00:00 certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/euvd-2026-372180 EUVD-2026-372180 2026-10-04T11:21:49.925314+00:00 EUVD-2026-372180 https://cve.radiocsirt.org/vuln/fkie_cve-2026-92522 fkie_cve-2026-92522 2026-10-04T11:21:49.925327+00:00

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

ACPI: processor: validate MADT IOAPIC entry bounds

The IOAPIC hotplug lookup parses both MADT and _MAT records directly. The MADT walk previously used a subtable's declared length to advance the cursor after only locating a generic header. The _MAT path likewise passed a generic header to the IOAPIC helper.

Validate that a current record has a complete generic header, that its declared length is contained in the available record range, and that a typed IOAPIC record contains the full fixed IOAPIC body before reading its fields. Use the same relation for both MADT and _MAT provider paths.

 https://cve.radiocsirt.org/vuln/ghsa-jg3q-2vpp-2763 GHSA-jg3q-2vpp-2763 2026-10-04T11:21:49.925358+00:00

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

ACPI: processor: validate MADT IOAPIC entry bounds

The IOAPIC hotplug lookup parses both MADT and _MAT records directly. The MADT walk previously used a subtable's declared length to advance the cursor after only locating a generic header. The _MAT path likewise passed a generic header to the IOAPIC helper.

Validate that a current record has a complete generic header, that its declared length is contained in the available record range, and that a typed IOAPIC record contains the full fixed IOAPIC body before reading its fields. Use the same relation for both MADT and _MAT provider paths.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-92522 msrc_CVE-2026-92522 — ACPI: processor: validate MADT IOAPIC entry bounds 2026-10-04T11:21:49.925378+00:00 msrc_CVE-2026-92522 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11893-1 openSUSE-SU-2026:11893-1 — kernel-devel-7.2.8-1.1 on GA media 2026-10-04T11:21:49.925395+00:00

kernel-devel-7.2.8-1.1 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-92522 UBUNTU-CVE-2026-92522 2026-10-04T11:21:49.925550+00:00

Affected: 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, Ubuntu:16.04:LTS: linux-hwe-edge and 245 more

In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: validate MADT IOAPIC entry bounds The IOAPIC hotplug lookup parses both MADT and _MAT records directly. The MADT walk previously used a subtable's declared length to advance the cursor after only locating a generic header. The _MAT path likewise passed a generic header to the IOAPIC helper. Validate that a current record has a complete generic header, that its declared length is contained in the available record range, and that a typed IOAPIC record contains the full fixed IOAPIC body before reading its fields. Use the same relation for both MADT and _MAT provider paths.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444 WID-SEC-W-2026-3444 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T11:21:49.925828+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.