https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:56:49 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-12671 bdu:2026-12671 https://cve.radiocsirt.org/vuln/bdu:2026-12671 https://cve.radiocsirt.org/vuln/bell-cve-2026-31741 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-31741 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926 https://cve.radiocsirt.org/vuln/euvd-2026-315680 EUVD-2026-315680 https://cve.radiocsirt.org/vuln/euvd-2026-315680 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31741 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>counter: rz-mtu3-cnt: prevent counter from being toggled multiple times</p> <p>Runtime PM counter is incremented / decremented each time the sysfs enable file is written to.</p> <p>If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message.</p> <p>rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!</p> <p>At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel.</p> <p>If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0.</p> <p>If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel.</p> <p>Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>counter: rz-mtu3-cnt: prevent counter from being toggled multiple times</p> <p>Runtime PM counter is incremented / decremented each time the sysfs enable file is written to.</p> <p>If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message.</p> <p>rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!</p> <p>At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel.</p> <p>If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0.</p> <p>If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel.</p> <p>Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-31741 https://cve.radiocsirt.org/vuln/ghsa-gh23-6p4g-c667 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>counter: rz-mtu3-cnt: prevent counter from being toggled multiple times</p> <p>Runtime PM counter is incremented / decremented each time the sysfs enable file is written to.</p> <p>If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message.</p> <p>rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!</p> <p>At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel.</p> <p>If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0.</p> <p>If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel.</p> <p>Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>counter: rz-mtu3-cnt: prevent counter from being toggled multiple times</p> <p>Runtime PM counter is incremented / decremented each time the sysfs enable file is written to.</p> <p>If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message.</p> <p>rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!</p> <p>At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel.</p> <p>If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0.</p> <p>If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel.</p> <p>Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.</p> https://cve.radiocsirt.org/vuln/ghsa-gh23-6p4g-c667 https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-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:21555-1 https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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:23066-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31741 <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 141 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: counter: rz-mtu3-cnt: prevent counter from being toggled multiple times Runtime PM counter is incremented / decremented each time the sysfs enable file is written to. If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message. rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow! At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel. If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0. If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel. Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.</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 141 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: counter: rz-mtu3-cnt: prevent counter from being toggled multiple times Runtime PM counter is incremented / decremented each time the sysfs enable file is written to. If user writes 0 to the sysfs enable file multiple times, runtime PM usage count underflows, generating the following message. rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow! At the same time, hardware registers end up being accessed with clocks off in rz_mtu3_terminate_counter() to disable an already disabled channel. If user writes 1 to the sysfs enable file multiple times, runtime PM usage count will be incremented each time, requiring the same number of 0 writes to get it back to 0. If user writes 0 to the sysfs enable file while PWM is in progress, PWM is stopped without counter being the owner of the underlying MTU3 channel. Check against the cached count_is_enabled value and exit if the user is trying to set the same enable value.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31741 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1346 <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.</p> <p>Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1346