https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 05:42:32 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-00830 bdu:2025-00830 https://cve.radiocsirt.org/vuln/bdu:2025-00830 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0265 certfr-2024-avi-0265 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0265 https://cve.radiocsirt.org/vuln/euvd-2026-344333 EUVD-2026-344333 https://cve.radiocsirt.org/vuln/euvd-2026-344333 https://cve.radiocsirt.org/vuln/fkie_cve-2021-46921 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>locking/qrwlock: Fix ordering in queued_write_lock_slowpath()</p> <p>While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired.</p> <p>We&#39;ve seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it.</p> <p>Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&amp;ep-&gt;lock, flags); --&gt; (observes value before unlock) | chain_epi_lockless() | | epi-&gt;next = xchg(&amp;ep-&gt;ovflist, epi); | | read_unlock_irqrestore(&amp;ep-&gt;lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep-&gt;ovflist); |</p> <p>A core can order…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>locking/qrwlock: Fix ordering in queued_write_lock_slowpath()</p> <p>While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired.</p> <p>We&#39;ve seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it.</p> <p>Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&amp;ep-&gt;lock, flags); --&gt; (observes value before unlock) | chain_epi_lockless() | | epi-&gt;next = xchg(&amp;ep-&gt;ovflist, epi); | | read_unlock_irqrestore(&amp;ep-&gt;lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep-&gt;ovflist); |</p> <p>A core can order…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-46921 https://cve.radiocsirt.org/vuln/ghsa-8j25-5vwv-hm2f <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>locking/qrwlock: Fix ordering in queued_write_lock_slowpath()</p> <p>While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired.</p> <p>We&#39;ve seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it.</p> <p>Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&amp;ep-&gt;lock, flags); --&gt; (observes value before unlock) | chain_epi_lockless() | | epi-&gt;next = xchg(&amp;ep-&gt;ovflist, epi); | | read_unlock_irqrestore(&amp;ep-&gt;lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep-&gt;ovflist); |</p> <p>A core can order…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>locking/qrwlock: Fix ordering in queued_write_lock_slowpath()</p> <p>While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired.</p> <p>We&#39;ve seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it.</p> <p>Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&amp;ep-&gt;lock, flags); --&gt; (observes value before unlock) | chain_epi_lockless() | | epi-&gt;next = xchg(&amp;ep-&gt;ovflist, epi); | | read_unlock_irqrestore(&amp;ep-&gt;lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep-&gt;ovflist); |</p> <p>A core can order…</p> https://cve.radiocsirt.org/vuln/ghsa-8j25-5vwv-hm2f https://cve.radiocsirt.org/vuln/gsd-2021-46921 gsd-2021-46921 https://cve.radiocsirt.org/vuln/gsd-2021-46921 https://cve.radiocsirt.org/vuln/suse-su-2024:0925-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:0925-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46921 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 98 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: locking/qrwlock: Fix ordering in queued_write_lock_slowpath() While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired. We&#39;ve seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it. Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&amp;ep-&gt;lock, flags); --&gt; (observes value before unlock) | chain_epi_lockless() | | epi-&gt;next = xchg(&amp;ep-&gt;ovflist, epi); | | read_unlock_irqrestore(&amp;ep-&gt;lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep-&gt;ovflist); | A core can order the rea…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 98 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: locking/qrwlock: Fix ordering in queued_write_lock_slowpath() While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired. We&#39;ve seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it. Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&amp;ep-&gt;lock, flags); --&gt; (observes value before unlock) | chain_epi_lockless() | | epi-&gt;next = xchg(&amp;ep-&gt;ovflist, epi); | | read_unlock_irqrestore(&amp;ep-&gt;lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep-&gt;ovflist); | A core can order the rea…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46921 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0488 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0488