CVE-2023-53472

pwm: lpc32xx: Remove handling of PWM channels

MEDIUM
5.5
CVSS Score
Published: October 1, 2025 at 11:42 AM UTC
Updated: June 17, 2026 at 06:45 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.9.284v ≥ 5.14.84.14.248 ≤ v < 4.14.3264.19.208 ≤ v < 4.19.2954.9.284 ≤ v < 4.105.10.69 ≤ v < 5.10.1955.14.8 ≤ v < 5.155.14.8 ≤ v < 5.15.1325.15 ≤ v < 5.15.1325.15 ≤ v < 6.1.545.15 ≤ v < 6.5.45.15 ≤ v < 6.65.16 ≤ v < 6.1.545.4.149 ≤ v < 5.4.2576.2 ≤ v < 6.5.41c90a357cef4219cb436e59cc7463888103e104b322b70b522abe03cd59712bb47a72eddd835d19d3d2813fb17e5fd0d73c1d1442ca0192bde4af10e4.14.2484.19.2084.9.2844459118977665f681017e1299933895d54b6e87b5.10.695.14.85.155.4.1497fc2172ad4e701d3c6e7dcb7b2efd8df71d2417b81e6b51709da162b94e40a445bb60856406beaa1bb4de81eb940e7027f37a6fd3b7ddcb4403deb56
Vendor states this is fixed in 04301da4d87067a989f70ee56942bf9d97cd2a45 (fixed)
Vendor states this is fixed in 4aae44f65827f0213a7361cf9c32cfe06114473f (fixed)
Vendor states this is fixed in 523f6268e86552a048975749251184c4e9a4b38f (fixed)
Vendor states this is fixed in 5e22217c11424ef958ba28d03ff7167b4d7a8914 (fixed)
Vendor states this is fixed in a2d9d884e84bfd37892219b1f55847f36d8e9901 (fixed)
Vendor states this is fixed in a9a505f5b39d8fff1a55963a5e524c84639e98b2 (fixed)
Vendor states this is fixed in abd9b2ee4047ccd980decbf26d61f9637604b1d5 (fixed)
Vendor states this is fixed in e3a0ddbaf7f1f9ffc070718b417461ced3268758 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14.326 (unaffected)
Vendor states this is fixed in 4.19.295 (unaffected)
Vendor states this is fixed in 5.10.195 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.132 (unaffected)
Vendor states this is fixed in 5.4.257 (unaffected)
Vendor states this is fixed in 6.1.54 (unaffected)
Vendor states this is fixed in 6.5.4 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card