Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53472pwm: lpc32xx: Remove handling of PWM channels

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53472, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected bb4de81eb940e7027f37a6fd3b7ddcb4403deb56 – < abd9b2ee4047ccd980decbf26d61f9637604b1d5
    • affected 4459118977665f681017e1299933895d54b6e87b – < a9a505f5b39d8fff1a55963a5e524c84639e98b2
    • affected 81e6b51709da162b94e40a445bb60856406beaa1 – < 04301da4d87067a989f70ee56942bf9d97cd2a45
    • affected 322b70b522abe03cd59712bb47a72eddd835d19d – < a2d9d884e84bfd37892219b1f55847f36d8e9901
    • affected 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e – < 5e22217c11424ef958ba28d03ff7167b4d7a8914
    • affected 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e – < 523f6268e86552a048975749251184c4e9a4b38f
    • affected 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e – < e3a0ddbaf7f1f9ffc070718b417461ced3268758
    • affected 3d2813fb17e5fd0d73c1d1442ca0192bde4af10e – < 4aae44f65827f0213a7361cf9c32cfe06114473f
    • affected 7fc2172ad4e701d3c6e7dcb7b2efd8df71d2417b
    • affected 1c90a357cef4219cb436e59cc7463888103e104b
    • affected 4.14.248 – < 4.14.326
    • affected 4.19.208 – < 4.19.295
    • affected 5.4.149 – < 5.4.257
    • affected 5.10.69 – < 5.10.195
    • affected 4.9.284 – < 4.10
    • affected 5.14.8 – < 5.15
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 4.14.326 – ≤ 4.14.*
    • unaffected 4.19.295 – ≤ 4.19.*
    • unaffected 5.4.257 – ≤ 5.4.*
    • unaffected 5.10.195 – ≤ 5.10.*
    • unaffected 5.15.132 – ≤ 5.15.*
    • unaffected 6.1.54 – ≤ 6.1.*
    • unaffected 6.5.4 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53472 badge
[![CVE-2023-53472](https://cveledger.app/badge/CVE-2023-53472.svg)](https://cveledger.app/cve/CVE-2023-53472)

Record last updated .