LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52475: Input: powermate - fix use-after-free in powermate_config_complete

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52475 is a Linux kernel bug in the Griffin PowerMate USB input driver. Disconnecting the device can leave an asynchronous USB request running after driver memory is freed. The practical risk is most relevant to systems where this driver is present and USB device connection or disconnection is possible.

Executive priority

Prioritize routine kernel patching, with higher urgency for user-accessible Linux endpoints and embedded devices with USB access. This is not currently evidenced as internet-exploited or actively exploited, but kernel memory safety bugs deserve timely remediation.

Technical view

The powermate driver has a use-after-free in powermate_config_complete. On disconnect, powermate_device memory may be freed while an asynchronous control URB can still complete and invoke its callback. The upstream stable fix cancels in-progress requests with usb_kill_urb() during device disconnect.

Likely exposure

Exposure appears limited to Linux systems with the powermate input driver available or loaded, especially endpoints, kiosks, workstations, or embedded systems with accessible USB ports. Server exposure is likely lower unless USB devices can be attached or passed through.

Exploitation context

The source bundle cites syzbot discovery and kernel fixes, but no CVSS score, public exploitation, or KEV listing. Exploitation would likely require interaction with device disconnect behavior and the powermate USB driver. Impact is not fully characterized in the provided sources.

Researcher notes

Affected version data in the bundle is broad and commit-based, so vendor kernel backports matter. The core fix is lifecycle cleanup: cancel the configuration URB on disconnect before freeing powermate state. Avoid assuming exploitability beyond the documented use-after-free.

Mitigation direction

  • Update to a vendor or stable Linux kernel containing the referenced powermate driver fix.
  • If unused, consider disabling or preventing loading of the powermate driver per vendor guidance.
  • Restrict physical or virtual USB device attachment on sensitive systems.
  • Track your Linux distribution advisories for backported fixes.

Validation and detection

  • Identify systems running affected Linux kernel versions or vendor kernels without the fix.
  • Check whether the powermate driver is built, loadable, or currently loaded.
  • Confirm the kernel includes one of the referenced stable commits or a vendor backport.
  • Review endpoint classes with accessible USB ports for prioritization.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52475 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 4.14.328, 4.19.297, 5.4.259, 5.10.199, 5.15.136, 6.1.59, 6.5.8, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.