https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-01T22:18:36.861954+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-1073 CERTFR-2025-AVI-1073 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at… 2026-10-01T22:18:39.186329+00:00 CERTFR-2025-AVI-1073 https://vulnerability.circl.lu/vuln/bdu:2026-02684 bdu:2026-02684 2026-10-01T22:18:39.186462+00:00 bdu:2026-02684 https://vulnerability.circl.lu/vuln/bell-cve-2025-39926 BELL-CVE-2025-39926 2026-10-01T22:18:39.186490+00:00

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

 https://vulnerability.circl.lu/vuln/fkie_cve-2025-39926 fkie_cve-2025-39926 2026-10-01T22:18:39.186542+00:00

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

genetlink: fix genl_bind() invoking bind() after -EPERM

Per family bind/unbind callbacks were introduced to allow families to track multicast group consumer presence, e.g. to start or stop producing events depending on listeners.

However, in genl_bind() the bind() callback was invoked even if capability checks failed and ret was set to -EPERM. This means that callbacks could run on behalf of unauthorized callers while the syscall still returned failure to user space.

Fix this by only invoking bind() after "if (ret) break;" check i.e. after permission checks have succeeded.

 https://vulnerability.circl.lu/vuln/ghsa-f9wm-ppg2-pc92 GHSA-f9wm-ppg2-pc92 2026-10-01T22:18:39.186622+00:00

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

genetlink: fix genl_bind() invoking bind() after -EPERM

Per family bind/unbind callbacks were introduced to allow families to track multicast group consumer presence, e.g. to start or stop producing events depending on listeners.

However, in genl_bind() the bind() callback was invoked even if capability checks failed and ret was set to -EPERM. This means that callbacks could run on behalf of unauthorized callers while the syscall still returned failure to user space.

Fix this by only invoking bind() after "if (ret) break;" check i.e. after permission checks have succeeded.

 https://vulnerability.circl.lu/vuln/opensuse-su-2025-20081-1 openSUSE-SU-2025-20081-1 — Security update for the Linux Kernel 2026-10-01T22:18:39.186662+00:00

Security update for the Linux Kernel

 https://vulnerability.circl.lu/vuln/suse-su-2025:20994-1 SUSE-SU-2025:20994-1 — Security update for the Linux Kernel 2026-10-01T22:18:39.187390+00:00

Security update for the Linux Kernel

 https://vulnerability.circl.lu/vuln/ubuntu-cve-2025-39926 UBUNTU-CVE-2025-39926 2026-10-01T22:18:39.188011+00:00

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 90 more

In the Linux kernel, the following vulnerability has been resolved: genetlink: fix genl_bind() invoking bind() after -EPERM Per family bind/unbind callbacks were introduced to allow families to track multicast group consumer presence, e.g. to start or stop producing events depending on listeners. However, in genl_bind() the bind() callback was invoked even if capability checks failed and ret was set to -EPERM. This means that callbacks could run on behalf of unauthorized callers while the syscall still returned failure to user space. Fix this by only invoking bind() after "if (ret) break;" check i.e. after permission checks have succeeded.

 https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2170 WID-SEC-W-2025-2170 — Linux Kernel: Mehrere Schwachstellen 2026-10-01T22:18:39.188266+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen, möglicherweise um beliebigen Code auszuführen oder eine Speicherbeschädigung zu verursachen.