https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 09:19:59 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-09382 bdu:2026-09382 https://cve.radiocsirt.org/vuln/bdu:2026-09382 https://cve.radiocsirt.org/vuln/bell-cve-2025-68339 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-68339 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0057 certfr-2026-avi-0057 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0057 https://cve.radiocsirt.org/vuln/euvd-2026-315121 EUVD-2026-315121 https://cve.radiocsirt.org/vuln/euvd-2026-315121 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68339 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>atm/fore200e: Fix possible data race in fore200e_open()</p> <p>Protect access to fore200e-&gt;available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race.</p> <p>The field fore200e-&gt;available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos().</p> <p>In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc-&gt;qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock.</p> <p>This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs.</p> <p>Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>atm/fore200e: Fix possible data race in fore200e_open()</p> <p>Protect access to fore200e-&gt;available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race.</p> <p>The field fore200e-&gt;available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos().</p> <p>In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc-&gt;qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock.</p> <p>This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs.</p> <p>Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68339 https://cve.radiocsirt.org/vuln/ghsa-p5pr-v4m5-r2vj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>atm/fore200e: Fix possible data race in fore200e_open()</p> <p>Protect access to fore200e-&gt;available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race.</p> <p>The field fore200e-&gt;available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos().</p> <p>In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc-&gt;qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock.</p> <p>This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs.</p> <p>Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>atm/fore200e: Fix possible data race in fore200e_open()</p> <p>Protect access to fore200e-&gt;available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race.</p> <p>The field fore200e-&gt;available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos().</p> <p>In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc-&gt;qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock.</p> <p>This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs.</p> <p>Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.</p> https://cve.radiocsirt.org/vuln/ghsa-p5pr-v4m5-r2vj https://cve.radiocsirt.org/vuln/msrc_cve-2025-68339 msrc_CVE-2025-68339 https://cve.radiocsirt.org/vuln/msrc_cve-2025-68339 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20145-1 https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68339 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 231 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: atm/fore200e: Fix possible data race in fore200e_open() Protect access to fore200e-&gt;available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race. The field fore200e-&gt;available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos(). In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc-&gt;qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock. This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs. Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 231 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: atm/fore200e: Fix possible data race in fore200e_open() Protect access to fore200e-&gt;available_cell_rate with rate_mtx lock in the error handling path of fore200e_open() to prevent a data race. The field fore200e-&gt;available_cell_rate is a shared resource used to track available bandwidth. It is concurrently accessed by fore200e_open(), fore200e_close(), and fore200e_change_qos(). In fore200e_open(), the lock rate_mtx is correctly held when subtracting vcc-&gt;qos.txtp.max_pcr from available_cell_rate to reserve bandwidth. However, if the subsequent call to fore200e_activate_vcin() fails, the function restores the reserved bandwidth by adding back to available_cell_rate without holding the lock. This introduces a race condition because available_cell_rate is a global device resource shared across all VCCs. If the error path in fore200e_open() executes concurrently with operations like fore200e_close() or fore200e_change_qos() on other VCCs, a read-modify-write race occurs. Specifically, the error path reads the rate without the lock. If another CPU acquires the lock and modifies the rate (e.g., releasing bandwidth in fore200e_close()) between this read and the subsequent write, the error path will overwrite the concurrent update with a stale value. This results in incorrect bandwidth accounting.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68339 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2915 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2915