Service interruption via touchscreen probe reference leak
Published Oct 4, 2025 · Updated Oct 4, 2025
Resource leak in the Linux kernel raspberrypi-ts driver from 5.0 allows local users to interrupt service through failed device probes. In rpi_ts_probe, error returns after rpi_firmware_get leave acquired firmware references unreleased because cleanup does not cover those paths. The driver and Raspberry Pi firmware touchscreen hardware must be present; public records do not identify how an unprivileged user forces repeated probe failures.
Summary
What happened
Resource leak in the Linux kernel raspberrypi-ts driver from 5.0 allows local users to interrupt service through failed device probes. In rpi_ts_probe, error returns after rpi_firmware_get leave acquired firmware references unreleased because cleanup does not cover those paths. The driver and Raspberry Pi firmware touchscreen hardware must be present; public records do not identify how an unprivileged user forces repeated probe failures.
The record
- CVE
- CVE-2023-53533
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <0d6a5c9489c8a3d434e685066119c4333476dccd
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <1dfa3c9dd27bdc347733d06e980395768520bc3e
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <36d087e49dabd28d2c13a7532dac72d625ce69fb
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <5bca3688bdbc3b58a2894b8671a8e2378efe28bd
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <7acad58049acc6ac148e8b613a6eceeca4bcb4a7
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <9216aa5cfd86809a2681be3683cd9ac30432de0c
- Affected versionversion=0b9f28fed3f70ff9a0380fe308739dd72a30a6f6 <9dbbe9db224c23a60dc7b1e00c701be93328c873
- Affected versionversion=5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo