Resource leakage via discarded driver cleanup
Published May 17, 2024 · Updated May 11, 2026
Resource leakage in affected Linux kernel releases from 5.7 allows local users to deplete resources by unbinding a built-in TPD12S015 driver. The tpd12s015_remove() function carries an __exit annotation, so built-in compilation discards the cleanup routine that driver unbinding must call. The condition requires the driver to be built into the kernel and then unbound; the public record identifies resource leakage but not the leaked resource or exact service-failure mode.
Summary
What happened
Resource leakage in affected Linux kernel releases from 5.7 allows local users to deplete resources by unbinding a built-in TPD12S015 driver. The tpd12s015_remove() function carries an __exit annotation, so built-in compilation discards the cleanup routine that driver unbinding must call. The condition requires the driver to be built into the kernel and then unbound; the public record identifies resource leakage but not the leaked resource or exact service-failure mode.
The record
- CVE
- CVE-2023-52694
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=5.7
- Affected versionversion=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c <08ccff6ece35f08e8107e975903c370d849089e5
- Affected versionversion=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c <53926e2a39629702f7f809d614b3ca89c2478205
- Affected versionversion=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c <81f1bd85960b7a089a91e679ff7cd2524390bbf1
- Affected versionversion=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c <a8657406e12aa10412134622c58977ac657f16d2
- Affected versionversion=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c <ce3e112e7ae854249d8755906acc5f27e1542114
- Affected versionversion=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c <e00ec5901954d85b39b5f10f94e60ab9af463eb1
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