Kernel memory leak via unbalanced device cleanup
Published Dec 30, 2025 · Updated Dec 30, 2025
Memory leak in the DIO bus initialization path in affected Linux kernel versions leaves failed device registrations allocated. dio_init() omitted put_device() after device_register() failed and lacked a release callback to free the dio_dev object and its name. Only a device-registration failure during DIO initialization reaches the leak, and the published record reports no data disclosure or modification.
Summary
What happened
Memory leak in the DIO bus initialization path in affected Linux kernel versions leaves failed device registrations allocated. dio_init() omitted put_device() after device_register() failed and lacked a release callback to free the dio_dev object and its name. Only a device-registration failure during DIO initialization reaches the leak, and the published record reports no data disclosure or modification.
The record
- CVE
- CVE-2022-50848
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 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=2.6.29
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <4b68caa95064ac464f1b261d08ac677e753d1088
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <78fddc0ff971f9874d53c854818cc4aafa144114
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <8e002b9fe831b27d4506df6fa60cb33ba0730ac3
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <a0ead7e8da84f4c3759417b8e928b65e0207c646
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <a524e7fed696a4dfef671e0fda3511bfd2dca0cf
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <affe3cea6b3148fa66796a48640664822ceccd48
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <da64e01da40c6b71a54144126da53cc3b27201ac
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <e63e99397b2613d50a5f4f02ed07307e67a190f1
- Affected versionversion=2e4c77bea3d8b17d94f8ee382411f359b708560f <fce9890e1be4c0460dad850cc8c00414a9d25f0f
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