In the Linux kernel, the following vulnerability has been resolved:
pwm: lpc32xx: Remove handling of PWM channels
Because LPC32xx PWM controllers have only a single output which is registered as the only PWM device/channel per controller, it is known in advance that pwm->hwpwm value is always 0. On basis of this fact simplify the code by removing operations with pwm->hwpwm, there is no controls which require channel number as input.
Even though I wasn't aware at the time when I forward ported that patch, this fixes a null pointer dereference as lpc32xx->chip.pwms is NULL before devm_pwmchip_add() is called.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Oct 3, 2025 | Oct 3, 2025 |
| Ubuntu | — | Upgrade linux-ibm-5.15Upgrade linuxUpgrade linux-nvidia-tegra-igxUpgrade linux-riscv-5.15Upgrade linux-gkeopUpgrade linux-gcp-5.4Upgrade linux-nvidia-tegraUpgrade linux-hwe-5.4Upgrade linux-azure-5.15Upgrade linux-ibm-5.4Upgrade linux-aws-fipsUpgrade linux-azure-fipsUpgrade linux-ibmUpgrade linux-nvidia-tegra-5.15Upgrade linux-gcpUpgrade linux-gcp-fipsUpgrade linux-intel-iot-realtimeUpgrade linux-oracle-5.15Upgrade linux-realtimeUpgrade linux-xilinx-zynqmpUpgrade linux-oracleUpgrade linux-bluefieldUpgrade linux-azure-5.4Upgrade linux-fipsUpgrade linux-raspi-5.4Upgrade linux-gkeUpgrade linux-kvmUpgrade linux-azure-fdeUpgrade linux-lowlatency-hwe-5.15Upgrade linux-lowlatencyUpgrade linux-aws-5.4Upgrade linux-azureUpgrade linux-nvidiaUpgrade linux-hwe-5.15Upgrade linux-aws-5.15Upgrade linux-oracle-5.4Upgrade linux-intel-iotgUpgrade linux-intel-iotg-5.15Upgrade linux-awsUpgrade linux-iotUpgrade linux-gcp-5.15Upgrade linux-raspi | Oct 10, 2025 | Oct 1, 2025 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | May 27, 2026 | Oct 1, 2025 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub