pwm: lpc32xx: Remove handling of PWM channels
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e · < 523f6268e86552a048975749251184c4e9a4b38f| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s LPC32xx PWM driver can dereference a null pointer before the PWM chip is registered. The input does not specify how an attacker could trigger this or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the LPC32xx PWM driver should check their systems; affected versions are not specified.