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-52475Input: powermate - fix use-after-free in powermate_config_complete

Description

In the Linux kernel, the following vulnerability has been resolved: Input: powermate - fix use-after-free in powermate_config_complete syzbot has found a use-after-free bug [1] in the powermate driver. This happens when the device is disconnected, which leads to a memory free from the powermate_device struct. When an asynchronous control message completes after the kfree and its callback is invoked, the lock does not exist anymore and hence the bug. Use usb_kill_urb() on pm->config to cancel any in-progress requests upon device disconnection. [1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 years 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-52475, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8677575c4f39d65bf0d719b5d20e8042e550ccb9
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 67cace72606baf1758fd60feb358f4c6be92e1cc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5aa514100aaf59868d745196258269a16737c7bd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cd2fbfd8b922b7fdd50732e47d797754ab59cb06
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6a4a396386404e62fb59bc3bde48871a64a82b4f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2efe67c581a2a6122b328d4bb6f21b3f36f40d46
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e528b1b9d60743e0b26224e3fe7aa74c24b8b2f8
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5c15c60e7be615f05a45cd905093a54b11f461bc
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.14.328 – ≤ 4.14.*
    • unaffected 4.19.297 – ≤ 4.19.*
    • unaffected 5.4.259 – ≤ 5.4.*
    • unaffected 5.10.199 – ≤ 5.10.*
    • unaffected 5.15.136 – ≤ 5.15.*
    • unaffected 6.1.59 – ≤ 6.1.*
    • unaffected 6.5.8 – ≤ 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-52475 badge
[![CVE-2023-52475](https://cveledger.app/badge/CVE-2023-52475.svg)](https://cveledger.app/cve/CVE-2023-52475)

Record last updated .