gpio: mt7621: avoid corruption of shared interrupt trigger state
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4ba9c3afda41213ec98c30053e32963892e6dc7c · < 1781172526d1092323af443fa03f00e6de560401| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gpio: mt7621: avoid corruption of shared interrupt trigger state
The bank-shared fields like 'rising' and 'falling' are modified using non-atomic read-modify-write operations. Since every gpio chip instance represents an entire bank of 32 pins, if 'mediatek_gpio_irq_type()' is called concurrently for different IRQs on the same bank a possible overwrite of each other's configuration is possible. Thus, protect this state with 'gpio_generic_lock_irqsave' lock in the same way it is handled in irp_chip 'mediatek_gpio_irq_mask()' and 'mediatek_gpio_irq_unmask()' callbacks.
From the CVE record · Linux
The Linux kernel’s mt7621 GPIO driver can corrupt shared interrupt trigger settings when interrupt types are configured concurrently for different pins in the same bank. The input does not identify an attacker path or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel with the mt7621 GPIO driver should check their installations; affected versions are not specified.