https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 10:06:18 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-64260 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2026-64260 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1162 certfr-2026-avi-1162 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1162 https://vulnerability.circl.lu/vuln/fkie_cve-2026-64260 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fuse-uring: Avoid queue-&gt;stopped races and set/read that value under lock</p> <p>There are several readers of queue-&gt;stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races &#39;struct fuse_req&#39; might be freed with fuse_request_end, but another thread/cpu might already do teardown work.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fuse-uring: Avoid queue-&gt;stopped races and set/read that value under lock</p> <p>There are several readers of queue-&gt;stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races &#39;struct fuse_req&#39; might be freed with fuse_request_end, but another thread/cpu might already do teardown work.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-64260 https://vulnerability.circl.lu/vuln/ghsa-985w-mqgj-6gfr <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fuse-uring: Avoid queue-&gt;stopped races and set/read that value under lock</p> <p>There are several readers of queue-&gt;stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races &#39;struct fuse_req&#39; might be freed with fuse_request_end, but another thread/cpu might already do teardown work.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fuse-uring: Avoid queue-&gt;stopped races and set/read that value under lock</p> <p>There are several readers of queue-&gt;stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races &#39;struct fuse_req&#39; might be freed with fuse_request_end, but another thread/cpu might already do teardown work.</p> https://vulnerability.circl.lu/vuln/ghsa-985w-mqgj-6gfr https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 <p>kernel-devel-7.1.7-1.1 on GA media</p> <p>kernel-devel-7.1.7-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64260 <p><strong>Affected:</strong> 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 119 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: fuse-uring: Avoid queue-&gt;stopped races and set/read that value under lock There are several readers of queue-&gt;stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races &#39;struct fuse_req&#39; might be freed with fuse_request_end, but another thread/cpu might already do teardown work.</p> <p><strong>Affected:</strong> 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 119 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: fuse-uring: Avoid queue-&gt;stopped races and set/read that value under lock There are several readers of queue-&gt;stopped that check the value under lock, but fuse_uring_commit_fetch() did not and actually the value was not set under the lock in fuse_uring_abort_end_requests() either. Especially in fuse_uring_commit_fetch it is important to check under a lock, because due to races &#39;struct fuse_req&#39; might be freed with fuse_request_end, but another thread/cpu might already do teardown work.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64260 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527 <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527