Service interruption via probe-path memory leak
Published Sep 18, 2025 · Updated Sep 18, 2025
A memory leak in affected Linux kernel releases allows local users to interrupt service during a failed Tahvo USB PHY probe. The tahvo_usb_probe function obtains an IRQ, then returns on a later error without releasing its allocated state because the failure path lacks cleanup. Reachability requires local low-privilege access and a configured Tahvo USB PHY that reaches the post-IRQ error path; the documented impact is availability loss only.
Summary
What happened
A memory leak in affected Linux kernel releases allows local users to interrupt service during a failed Tahvo USB PHY probe. The tahvo_usb_probe function obtains an IRQ, then returns on a later error without releasing its allocated state because the failure path lacks cleanup. Reachability requires local low-privilege access and a configured Tahvo USB PHY that reaches the post-IRQ error path; the documented impact is availability loss only.
The record
- CVE
- CVE-2023-53379
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=0d45a1373e669880b8beaecc8765f44cb0241e47 <342161c11403ea00e9febc16baab1d883d589d04
- Affected versionversion=0d45a1373e669880b8beaecc8765f44cb0241e47 <38dbd6f72bfbeba009efe0e9ec1f3ff09f9e23fa
- Affected versionversion=0d45a1373e669880b8beaecc8765f44cb0241e47 <dd9b7c89a80428cc5f4ae0d2e1311fdedb2a1aac
- Affected versionversion=0d45a1373e669880b8beaecc8765f44cb0241e47 <ecf26d6e1b5450620c214feea537bb6ce05c6741
- Affected versionversion=3f06415418f37ac602e71a61ee83ea43553e6bbd <3e5a7bebf832b1482efe27bcc15a88c5b28a30d0
- Affected versionversion=494629ba62a961de1f2dd0b7125878acb27b8043 <56901de563359de20513e16a9ae008ae2c22e9a9
- Affected versionversion=4eab21911d5d6a3377b8965b9fb06463b248fe6b
- Affected versionversion=5.15
- Affected versionversion=5e2d2f05204f7ab9c645a1fb9f10a3f6393dd2fa <4da9edeccf77d7b4c6dbcb34d5908acdaa5bd7e3
- Affected versionversion=606668e24a0d7fd262e2326d76bb60b965fe713f <fe9cdc19861950582f077f254a12026e169eaee5
- Affected versionversion=62e663c172115b9e26a0856508db6277871a7c32
- Affected versionversion=b45f0d0105a0f50e681dc8fac4b32e1192de34f2
- Affected versionversion=dcf379ea4e93b8ea23d628db68ae953b26d63af1
What conditions does exploitation require?
What is affected?
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
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