https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:39:50 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-72062 <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://vulnerability.circl.lu/vuln/bell-cve-2026-72062 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069 certfr-2026-avi-1069 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069 https://vulnerability.circl.lu/vuln/fkie_cve-2026-72062 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gpio: mt7621: avoid corruption of shared interrupt trigger state</p> <p>The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gpio: mt7621: avoid corruption of shared interrupt trigger state</p> <p>The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-72062 https://vulnerability.circl.lu/vuln/ghsa-hvv6-qvxj-4xmv <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gpio: mt7621: avoid corruption of shared interrupt trigger state</p> <p>The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>gpio: mt7621: avoid corruption of shared interrupt trigger state</p> <p>The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> https://vulnerability.circl.lu/vuln/ghsa-hvv6-qvxj-4xmv https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72062 <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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: gpio: mt7621: avoid corruption of shared interrupt trigger state The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 219 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: gpio: mt7621: avoid corruption of shared interrupt trigger state The bank-shared fields like &#39;rising&#39; and &#39;falling&#39; are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if &#39;mediatek_gpio_irq_type()&#39; is called concurrently for different IRQs on the same bank a possible overwrite of each other&#39;s configuration is possible. Thus, protect this state with &#39;gpio_generic_lock_irqsave&#39; lock in the same way it is handled in irp_chip &#39;mediatek_gpio_irq_mask()&#39; and &#39;mediatek_gpio_irq_unmask()&#39; callbacks.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72062 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852