https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T07:07:42.645150+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-68259 BELL-CVE-2026-68259 2026-10-03T07:07:43.614668+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069 certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p… 2026-10-03T07:07:43.614749+00:00 certfr-2026-avi-1069 https://cve.radiocsirt.org/vuln/euvd-2026-356157 EUVD-2026-356157 2026-10-03T07:07:43.614773+00:00 EUVD-2026-356157 https://cve.radiocsirt.org/vuln/fkie_cve-2026-68259 fkie_cve-2026-68259 2026-10-03T07:07:43.614786+00:00

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

drm/amdkfd: Check bounds in allocate_event_notification_slot

The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT

allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value.

Check them.

v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist

(cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)

 https://cve.radiocsirt.org/vuln/ghsa-3gmf-h2jg-hwv2 GHSA-3gmf-h2jg-hwv2 2026-10-03T07:07:43.614822+00:00

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

drm/amdkfd: Check bounds in allocate_event_notification_slot

The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT

allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value.

Check them.

v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist

(cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-68259 msrc_CVE-2026-68259 — drm/amdkfd: Check bounds in allocate_event_notification_slot 2026-10-03T07:07:43.614845+00:00 msrc_CVE-2026-68259 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1 openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel 2026-10-03T07:07:43.614863+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:23477-1 SUSE-SU-2026:23477-1 — Security update for the Linux Kernel 2026-10-03T07:07:43.615445+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68259 UBUNTU-CVE-2026-68259 2026-10-03T07:07:43.615798+00:00

Affected: 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 246 more

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds in allocate_event_notification_slot The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We weren't checking the bounds on that value. Check them. v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist (cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730 WID-SEC-W-2026-2730 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T07:07:43.616100+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.