https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T01:56:34.473439+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2024-09179 bdu:2024-09179 2026-10-03T01:56:35.102156+00:00 bdu:2024-09179 https://cve.radiocsirt.org/vuln/bell-cve-2024-26832 BELL-CVE-2024-26832 2026-10-03T01:56:35.102228+00:00

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

 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0526 certfr-2024-avi-0526 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent une élé… 2026-10-03T01:56:35.102264+00:00 certfr-2024-avi-0526 https://cve.radiocsirt.org/vuln/euvd-2026-320555 EUVD-2026-320555 2026-10-03T01:56:35.102283+00:00 EUVD-2026-320555 https://cve.radiocsirt.org/vuln/fkie_cve-2024-26832 fkie_cve-2024-26832 2026-10-03T01:56:35.102294+00:00

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

mm: zswap: fix missing folio cleanup in writeback race path

In zswap_writeback_entry(), after we get a folio from __read_swap_cache_async(), we grab the tree lock again to check that the swap entry was not invalidated and recycled. If it was, we delete the folio we just added to the swap cache and exit.

However, __read_swap_cache_async() returns the folio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock and put the folio before returning.

This was discovered by code inspection, probably because this path handles a race condition that should not happen often, and the bug would not crash the system, it will only strand the folio indefinitely.

 https://cve.radiocsirt.org/vuln/ghsa-fpqf-cxvg-rf89 GHSA-fpqf-cxvg-rf89 2026-10-03T01:56:35.102329+00:00

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

mm: zswap: fix missing folio cleanup in writeback race path

In zswap_writeback_entry(), after we get a folio from __read_swap_cache_async(), we grab the tree lock again to check that the swap entry was not invalidated and recycled. If it was, we delete the folio we just added to the swap cache and exit.

However, __read_swap_cache_async() returns the folio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock and put the folio before returning.

This was discovered by code inspection, probably because this path handles a race condition that should not happen often, and the bug would not crash the system, it will only strand the folio indefinitely.

 https://cve.radiocsirt.org/vuln/gsd-2024-26832 gsd-2024-26832 2026-10-03T01:56:35.102351+00:00 gsd-2024-26832 https://cve.radiocsirt.org/vuln/suse-su-2024:2135-1 SUSE-SU-2024:2135-1 — Security update for the Linux Kernel 2026-10-03T01:56:35.102362+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26832 UBUNTU-CVE-2024-26832 2026-10-03T01:56:35.102625+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 66 more

In the Linux kernel, the following vulnerability has been resolved: mm: zswap: fix missing folio cleanup in writeback race path In zswap_writeback_entry(), after we get a folio from __read_swap_cache_async(), we grab the tree lock again to check that the swap entry was not invalidated and recycled. If it was, we delete the folio we just added to the swap cache and exit. However, __read_swap_cache_async() returns the folio locked when it is newly allocated, which is always true for this path, and the folio is ref'd. Make sure to unlock and put the folio before returning. This was discovered by code inspection, probably because this path handles a race condition that should not happen often, and the bug would not crash the system, it will only strand the folio indefinitely.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920 WID-SEC-W-2024-0920 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T01:56:35.102728+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.