dbcve.org
Linux KernelOperating system · Linux

CVE-2023-53472

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-01
Fix available
A fix is available. Upgrade to 4.10 / 4.14.326 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-476

The code follows a pointer that is null, crashing the process. An attacker who can reliably trigger it turns the crash into a denial of service. The fix is checking for null before use and handling the failure path gracefully.

General guidance for the null pointer dereference class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.9.284, < 4.10>= 4.14.248, < 4.14.326>= 4.19.208, < 4.19.295>= 5.4.149, < 5.4.257>= 5.10.69, < 5.10.195>= 5.14.8, < 5.15.132>= 5.16, < 6.1.54>= 6.2, < 6.5.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.10 / 4.14.326 / 4.19.295 or later
Fixed in 4.104.14.3264.19.295
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to the next stable kernel release in your branch series (4.10+, 4.14.326+, 4.19.295+, or 5.4.257+)

  1. Identify the currently running kernel version using `uname -r`
  2. Determine which version branch your current kernel belongs to (4.9.x, 4.14.x, 4.19.x, or 5.4.x)
  3. Upgrade to a kernel version that includes the fix: For 4.9.x branch -> 4.10 or later; For 4.14.x branch -> 4.14.326 or later; For 4.19.x branch -> 4.19.295 or later; For 5.4.x branch -> 5.4.257 or later
  4. Apply the upgrade via package manager (e.g., `apt-get dist-upgrade`, `yum update`, or distribution-specific kernel update)
  5. Reboot the system to load the patched kernel
  6. Verify the new kernel version is running with `uname -r` and confirm the vulnerability is addressed
Caveat Standard kernel upgrade risks apply - verify hardware compatibility and required kernel modules are available in the new version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-53472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-53472 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data