pwm: lpc32xx: Remove handling of PWM channels
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.14.326, 4.19.295, 5.4.257, 5.10.195, 4.10, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4.14.248 · fixed in 4.14.326; From 4.19.208 · fixed in 4.19.295; From 5.4.149 · fixed in 5.4.257; From 5.10.69 · fixed in 5.10.195; From 4.9.284 · fixed in 4.10; From 5.14.8 · fixed in 5.15
- Linux Linux
5.15
References 8
git.kernel.org
- stable/c/abd9b2ee4047ccd980decbf26d61f9637604b1d5
- stable/c/a9a505f5b39d8fff1a55963a5e524c84639e98b2
- stable/c/04301da4d87067a989f70ee56942bf9d97cd2a45
- stable/c/a2d9d884e84bfd37892219b1f55847f36d8e9901
- stable/c/5e22217c11424ef958ba28d03ff7167b4d7a8914
- stable/c/523f6268e86552a048975749251184c4e9a4b38f
- stable/c/e3a0ddbaf7f1f9ffc070718b417461ced3268758
- stable/c/4aae44f65827f0213a7361cf9c32cfe06114473f