https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T12:41:00.409610+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-01794 bdu:2026-01794 2026-10-04T12:41:00.954562+00:00 bdu:2026-01794 https://cve.radiocsirt.org/vuln/bell-cve-2025-68750 BELL-CVE-2025-68750 2026-10-04T12:41:00.954637+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-04T12:41:00.954675+00:00 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-315161 EUVD-2026-315161 2026-10-04T12:41:00.954693+00:00 EUVD-2026-315161 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68750 fkie_cve-2025-68750 2026-10-04T12:41:00.954705+00:00

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

usb: potential integer overflow in usbg_make_tpg()

The variable tpgt in usbg_make_tpg() is defined as unsigned long and is assigned to tpgt->tport_tpgt, which is defined as u16. This may cause an integer overflow when tpgt is greater than USHRT_MAX (65535). I haven't tried to trigger it myself, but it is possible to trigger it by calling usbg_make_tpg() with a large value for tpgt.

I modified the type of tpgt to match tpgt->tport_tpgt and adjusted the relevant code accordingly.

This patch is similar to commit 59c816c1f24d ("vhost/scsi: potential memory corruption").

 https://cve.radiocsirt.org/vuln/ghsa-475m-mm7r-j479 GHSA-475m-mm7r-j479 2026-10-04T12:41:00.954740+00:00

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

usb: potential integer overflow in usbg_make_tpg()

The variable tpgt in usbg_make_tpg() is defined as unsigned long and is assigned to tpgt->tport_tpgt, which is defined as u16. This may cause an integer overflow when tpgt is greater than USHRT_MAX (65535). I haven't tried to trigger it myself, but it is possible to trigger it by calling usbg_make_tpg() with a large value for tpgt.

I modified the type of tpgt to match tpgt->tport_tpgt and adjusted the relevant code accordingly.

This patch is similar to commit 59c816c1f24d ("vhost/scsi: potential memory corruption").

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1 openSUSE-SU-2026:20145-1 — Security update for the Linux Kernel 2026-10-04T12:41:00.954762+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 SUSE-SU-2026:0278-1 — Security update for the Linux Kernel 2026-10-04T12:41:00.954901+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68750 UBUNTU-CVE-2025-68750 2026-10-04T12:41:00.955148+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 213 more

In the Linux kernel, the following vulnerability has been resolved: usb: potential integer overflow in usbg_make_tpg() The variable tpgt in usbg_make_tpg() is defined as unsigned long and is assigned to tpgt->tport_tpgt, which is defined as u16. This may cause an integer overflow when tpgt is greater than USHRT_MAX (65535). I haven't tried to trigger it myself, but it is possible to trigger it by calling usbg_make_tpg() with a large value for tpgt. I modified the type of tpgt to match tpgt->tport_tpgt and adjusted the relevant code accordingly. This patch is similar to commit 59c816c1f24d ("vhost/scsi: potential memory corruption").

 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2929 WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen 2026-10-04T12:41:00.955415+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.