LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53533: Input: raspberrypi-ts - fix refcount leak in rpi_ts_probe

In the Linux kernel, the following vulnerability has been resolved: Input: raspberrypi-ts - fix refcount leak in rpi_ts_probe rpi_firmware_get() take reference, we need to release it in error paths as well. Use devm_rpi_firmware_get() helper to handling the resources. Also remove the existing rpi_firmware_put().

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53533 is a Linux kernel resource-management bug in the Raspberry Pi touchscreen input driver. The available record describes a firmware reference leak during driver probing error paths. The source bundle provides no CVSS score, CWE, business-impact detail, or active-exploitation evidence.

Executive priority

Treat this as routine kernel hygiene unless your fleet relies on Raspberry Pi touchscreen devices. There is no supplied evidence of active exploitation or severe impact, but affected embedded systems should still receive normal vendor kernel updates.

Technical view

In rpi_ts_probe, rpi_firmware_get took a reference that was not released on some error paths. The fix changes the driver to use devm_rpi_firmware_get so resource cleanup is device-managed, and removes the manual rpi_firmware_put handling.

Likely exposure

Exposure appears limited to Linux kernels that include and use the raspberrypi-ts input driver, especially Raspberry Pi touchscreen deployments. The bundle lists Linux kernel versions including 5.0 through 6.4 as affected, with stable commit references for fixes.

Exploitation context

The CVE is not marked KEV, and the provided sources do not report active exploitation or public exploit availability. The described issue is a reference-count leak in error handling, not a clearly documented remote-code-execution path.

Researcher notes

The evidence supports a narrow driver-level refcount leak in probe error paths. Impact is hard to rate because the record lacks CVSS, CWE, exploitability notes, and operational failure detail. Validate exposure by kernel version, backport status, and actual raspberrypi-ts usage.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Check Linux distribution or Raspberry Pi vendor guidance before manual backporting.
  • Prioritize systems using Raspberry Pi touchscreen hardware or this driver.
  • Plan normal kernel-update reboot and rollback procedures.

Validation and detection

  • Inventory kernel versions against the affected version list.
  • Confirm whether raspberrypi-ts is built, loaded, or required.
  • Verify the relevant stable fix is present or backported.
  • Review vendor changelogs for CVE-2023-53533 coverage.
  • After update, test touchscreen input and boot behavior.
Prepared
Confidence
medium
Sources
9

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-53533 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
0ADP providers
8Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b9f28fed3f70ff9a0380fe308739dd72a30a6f6, 0b9f28fed3f70ff9a0380fe308739dd72a30a6f6, 0b9f28fed3f70ff9a0380fe308739dd72a30a6f6, 0b9f28fed3f70ff9a0380fe308739dd72a30a6f6, 0b9f28fed3f70ff9a0380fe308739dd72a30a6f6, 0b9f28fed3f70ff9a0380fe308739dd72a30a6f6, 0b9f28fed3f70ff9a0380fe308739dd72a30a6f6unaffected
LinuxLinux5.0, 0, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

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