https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T12:07:08.618723+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-80859 BELL-CVE-2026-80859 2026-10-03T12:07:08.629397+00:00

Affected: Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/euvd-2026-366717 EUVD-2026-366717 2026-10-03T12:07:08.629452+00:00 EUVD-2026-366717 https://cve.radiocsirt.org/vuln/fkie_cve-2026-80859 fkie_cve-2026-80859 2026-10-03T12:07:08.629468+00:00

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

fuse: fix missing barrier when checking io-uring readiness

fuse_block_alloc() reads fch->initialized and then fch->io_uring. fch->io_uring is set before fch->initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads.

This may lead a CPU to observe fch->initialized=1 but fch->io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents.

Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.

 https://cve.radiocsirt.org/vuln/ghsa-66f3-f7p7-8q9g GHSA-66f3-f7p7-8q9g 2026-10-03T12:07:08.629502+00:00

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

fuse: fix missing barrier when checking io-uring readiness

fuse_block_alloc() reads fch->initialized and then fch->io_uring. fch->io_uring is set before fch->initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads.

This may lead a CPU to observe fch->initialized=1 but fch->io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents.

Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1 openSUSE-SU-2026:11773-1 — kernel-devel-7.2.5-1.1 on GA media 2026-10-03T12:07:08.629525+00:00

kernel-devel-7.2.5-1.1 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80859 UBUNTU-CVE-2026-80859 2026-10-03T12:07:08.629611+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 120 more

In the Linux kernel, the following vulnerability has been resolved: fuse: fix missing barrier when checking io-uring readiness fuse_block_alloc() reads fch->initialized and then fch->io_uring. fch->io_uring is set before fch->initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads. This may lead a CPU to observe fch->initialized=1 but fch->io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents. Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211 WID-SEC-W-2026-3211 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T12:07:08.629792+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.