CVE-2023-53472: pwm: lpc32xx: Remove handling of PWM channels
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 04301da4d87067a989f70ee56942bf9d97cd2a45, 4.10, 4.14.326.
Low priority for now. Upgrade to Linux Linux 04301da4d87067a989f70ee56942bf9d97cd2a45, 4.10, 4.14.326 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9.284 and later · before 4.10
- linux linux kernel4.14.248 and later · before 4.14.326
- linux linux kernel4.19.208 and later · before 4.19.295
- linux linux kernel5.4.149 and later · before 5.4.257
- linux linux kernel5.10.69 and later · before 5.10.195
- linux linux kernel5.14.8 and later · before 5.15.132
- linux linux kernel5.16 and later · before 6.1.54
- linux linux kernel6.2 and later · before 6.5.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 7fc2172ad4e701d3c6e7dcb7b2efd8df71d2417b, 1c90a357cef4219cb436e59cc7463888103e104b, 5.15affected
- bb4de81eb940e7027f37a6fd3b7ddcb4403deb56 and later · before abd9b2ee4047ccd980decbf26d61f9637604b1d5affected · git
- 4459118977665f681017e1299933895d54b6e87b and later · before a9a505f5b39d8fff1a55963a5e524c84639e98b2affected · git
- 81e6b51709da162b94e40a445bb60856406beaa1 and later · before 04301da4d87067a989f70ee56942bf9d97cd2a45affected · git
- 322b70b522abe03cd59712bb47a72eddd835d19d and later · before a2d9d884e84bfd37892219b1f55847f36d8e9901affected · git
- 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e and later · before 5e22217c11424ef958ba28d03ff7167b4d7a8914affected · git
- 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e and later · before 523f6268e86552a048975749251184c4e9a4b38faffected · git
- 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e and later · before e3a0ddbaf7f1f9ffc070718b417461ced3268758affected · git
- 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e and later · before 4aae44f65827f0213a7361cf9c32cfe06114473faffected · git
- 4.14.248 and later · before 4.14.326affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.55-1 | 6.1.55-1 |
| Debian:13 | linux | before 6.5.6-1 | 6.5.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53470Oct 1, 2025 · ionic: catch failure from devlink_alloc22Monitor
- ← EarlierCVE-2023-53471Oct 1, 2025 · drm/amdgpu/gfx: disable gfx9 cp_ecc_error_irq only when enabling legacy gfx ras31Monitor
- Later →CVE-2023-53475Oct 1, 2025 · usb: xhci: tegra: fix sleep in atomic call22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 04301da4d87067a989f70ee56942bf9d97cd2a45 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.14.326 | Vendor (CNA) |
| Linux Linux | 4.19.295 | Vendor (CNA) |
| Linux Linux | 4aae44f65827f0213a7361cf9c32cfe06114473f | Vendor (CNA) |
| Linux Linux | 5.10.195 | Vendor (CNA) |
| Linux Linux | 5.15 | Vendor (CNA) |
| Linux Linux | 5.4.257 | Vendor (CNA) |
| Linux Linux | 523f6268e86552a048975749251184c4e9a4b38f | Vendor (CNA) |
| Linux Linux | 5e22217c11424ef958ba28d03ff7167b4d7a8914 | Vendor (CNA) |
| Linux Linux | a2d9d884e84bfd37892219b1f55847f36d8e9901 | Vendor (CNA) |
| Linux Linux | a9a505f5b39d8fff1a55963a5e524c84639e98b2 | Vendor (CNA) |
| Linux Linux | abd9b2ee4047ccd980decbf26d61f9637604b1d5 | Vendor (CNA) |
| Linux Linux | e3a0ddbaf7f1f9ffc070718b417461ced3268758 | Vendor (CNA) |
| debian:linux | 6.1.55-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4aae44f65827f0213a7361cf9c32cfe06114473f
- git.kernel.org/stable/c/523f6268e86552a048975749251184c4e9a4b38f
- git.kernel.org/stable/c/5e22217c11424ef958ba28d03ff7167b4d7a8914
- git.kernel.org/stable/c/a2d9d884e84bfd37892219b1f55847f36d8e9901
- git.kernel.org/stable/c/a9a505f5b39d8fff1a55963a5e524c84639e98b2
- git.kernel.org/stable/c/abd9b2ee4047ccd980decbf26d61f9637604b1d5
- git.kernel.org/stable/c/e3a0ddbaf7f1f9ffc070718b417461ced3268758
Vendor advisories and official records. Exploit/PoC links are deliberately left out.