https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T17:27:30.855105+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2024-08981 bdu:2024-08981 2026-10-03T17:27:31.093299+00:00 bdu:2024-08981 https://cve.radiocsirt.org/vuln/bell-cve-2024-49854 Withdrawn: BELL-CVE-2024-49854 — CVE-2024-49854 does not affect BellSoft software 2026-10-03T17:27:31.093358+00:00

Withdrawn by the publisher.

https://cve.radiocsirt.org/vuln/certfr-2025-avi-0002 certfr-2025-avi-0002 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p… 2026-10-03T17:27:31.093379+00:00 certfr-2025-avi-0002 https://cve.radiocsirt.org/vuln/euvd-2026-346201 EUVD-2026-346201 2026-10-03T17:27:31.093396+00:00 EUVD-2026-346201 https://cve.radiocsirt.org/vuln/fkie_cve-2024-49854 fkie_cve-2024-49854 2026-10-03T17:27:31.093408+00:00

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

block, bfq: fix uaf for accessing waker_bfqq after splitting

After commit 42c306ed7233 ("block, bfq: don't break merge chain in bfq_split_bfqq()"), if the current procress is the last holder of bfqq, the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and then access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq may in the merge chain of bfqq, hence just recored waker_bfqq is still not safe.

Fix the problem by adding a helper bfq_waker_bfqq() to check if bfqq->waker_bfqq is in the merge chain, and current procress is the only holder.

 https://cve.radiocsirt.org/vuln/ghsa-8qj8-qf9j-579x GHSA-8qj8-qf9j-579x 2026-10-03T17:27:31.093445+00:00

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

block, bfq: fix uaf for accessing waker_bfqq after splitting

After commit 42c306ed7233 ("block, bfq: don't break merge chain in bfq_split_bfqq()"), if the current procress is the last holder of bfqq, the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and then access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq may in the merge chain of bfqq, hence just recored waker_bfqq is still not safe.

Fix the problem by adding a helper bfq_waker_bfqq() to check if bfqq->waker_bfqq is in the merge chain, and current procress is the only holder.

 https://cve.radiocsirt.org/vuln/msrc_cve-2024-49854 msrc_CVE-2024-49854 — block bfq: fix uaf for accessing waker_bfqq after splitting 2026-10-03T17:27:31.093466+00:00 msrc_CVE-2024-49854 https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media 2026-10-03T17:27:31.093489+00:00

kernel-devel-6.11.8-1.1 on GA media

 https://cve.radiocsirt.org/vuln/suse-su-2025:0117-1 SUSE-SU-2025:0117-1 — Security update for the Linux Kernel 2026-10-03T17:27:31.093766+00:00

Security update for the Linux Kernel

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49854 UBUNTU-CVE-2024-49854 2026-10-03T17:27:31.093842+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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 88 more

In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for accessing waker_bfqq after splitting After commit 42c306ed7233 ("block, bfq: don't break merge chain in bfq_split_bfqq()"), if the current procress is the last holder of bfqq, the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and then access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq may in the merge chain of bfqq, hence just recored waker_bfqq is still not safe. Fix the problem by adding a helper bfq_waker_bfqq() to check if bfqq->waker_bfqq is in the merge chain, and current procress is the only holder.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251 WID-SEC-W-2024-3251 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service 2026-10-03T17:27:31.093967+00:00

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..