Kernel memory leak via omitted device release
Published Sep 15, 2025 · Updated Sep 15, 2025
Memory leak in the Linux kernel watchdog core allows attackers to leave kernel allocations unreleased after failed device registration. The watchdog_cdev_register error path returns after cdev_device_add fails with a nonzero device ID without calling put_device, leaking wd_data and the device name. Reachability requires kernel-level watchdog device registration, and no unprivileged trigger is documented.
Summary
What happened
Memory leak in the Linux kernel watchdog core allows attackers to leave kernel allocations unreleased after failed device registration. The watchdog_cdev_register error path returns after cdev_device_add fails with a nonzero device ID without calling put_device, leaking wd_data and the device name. Reachability requires kernel-level watchdog device registration, and no unprivileged trigger is documented.
The record
- CVE
- CVE-2023-53234
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=450caf1faa0d7bbbd1da93d3ee8c5edea7bc51a8 <bf26b0e430ce34261f45959989edaf680b64d538
- Affected versionversion=5.5
- Affected versionversion=72139dfa2464e43957d330266994740bb7be2535 <13721a2ac66b246f5802ba1b75ad8637e53eeecc
- Affected versionversion=72139dfa2464e43957d330266994740bb7be2535 <23cc41c3f19c4d858c3708f1c0a06e94958e6c3b
- Affected versionversion=72139dfa2464e43957d330266994740bb7be2535 <50808d034e199fe3ff7a9d2068a4eebeb6b4098a
- Affected versionversion=72139dfa2464e43957d330266994740bb7be2535 <ac099d94e0480c937aa9172ab64074981ca1a4d3
- Affected versionversion=72139dfa2464e43957d330266994740bb7be2535 <c5a21a5501508ae3afa2fe6d5a3e74a37fa48df3
- Affected versionversion=ca7851d46de8a8d69022c4e5feed0820483b5f46 <59e391b3fc507a15b7e8e9d9f4de87cae177c366
- Affected versionversion=f4c36f1999745c2160422fe2f362deadbe3a136b <8c1655600f4f2839fb844fe8c70b2b65fadc7a56
- Affected versionversion=f76905ce52653e8a821963c35d9013cff19b1399
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
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