https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T15:30:35.387237+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-64238 Withdrawn: BELL-CVE-2026-64238 — CVE-2026-64238 does not affect BellSoft software 2026-10-02T15:30:35.521825+00:00

Withdrawn by the publisher.

https://cve.radiocsirt.org/vuln/certfr-2026-avi-0954 certfr-2026-avi-0954 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a… 2026-10-02T15:30:35.521868+00:00 certfr-2026-avi-0954 https://cve.radiocsirt.org/vuln/euvd-2026-340786 EUVD-2026-340786 2026-10-02T15:30:35.521887+00:00 EUVD-2026-340786 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64238 fkie_cve-2026-64238 2026-10-02T15:30:35.521900+00:00

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

gpio: shared: fix deadlock on shared proxy's parent removal

Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set") used the mutex embedded in struct gpio_shared_entry to protect the offset field which now can be modified after assignment. The critical section however is too wide and introduced a potential deadlock on the removal of the shared GPIO proxy's parent.

Make the critical section shorter - only protect the offset when it's being read.

While at it: mention the fact that the entry lock is now also used to protect against concurrent access to the offset field in the structure's documentation.

 https://cve.radiocsirt.org/vuln/ghsa-3qfm-27pw-9j46 GHSA-3qfm-27pw-9j46 2026-10-02T15:30:35.521937+00:00

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

gpio: shared: fix deadlock on shared proxy's parent removal

Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set") used the mutex embedded in struct gpio_shared_entry to protect the offset field which now can be modified after assignment. The critical section however is too wide and introduced a potential deadlock on the removal of the shared GPIO proxy's parent.

Make the critical section shorter - only protect the offset when it's being read.

While at it: mention the fact that the entry lock is now also used to protect against concurrent access to the offset field in the structure's documentation.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64238 UBUNTU-CVE-2026-64238 2026-10-02T15:30:35.521960+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 111 more

In the Linux kernel, the following vulnerability has been resolved: gpio: shared: fix deadlock on shared proxy's parent removal Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set") used the mutex embedded in struct gpio_shared_entry to protect the offset field which now can be modified after assignment. The critical section however is too wide and introduced a potential deadlock on the removal of the shared GPIO proxy's parent. Make the critical section shorter - only protect the offset when it's being read. While at it: mention the fact that the entry lock is now also used to protect against concurrent access to the offset field in the structure's documentation.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2527 WID-SEC-W-2026-2527 — Linux Kernel: Mehrere Schwachstellen 2026-10-02T15:30:35.522130+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.