Kernel memory leak via failed macio device registration
Published Oct 4, 2025 · Updated Oct 4, 2025
Memory leak in Linux kernel 2.6.30 and later affected branches allows local users to reduce availability when macio device registration fails. macio_add_one_device allocates a dynamic device name but does not release the device_initialize reference when of_device_register fails, preventing kobject_cleanup from freeing the name. Reachability requires the Macintosh macio device path and a registration failure; the resulting leak has no disclosed confidentiality or integrity impact.
Summary
What happened
Memory leak in Linux kernel 2.6.30 and later affected branches allows local users to reduce availability when macio device registration fails. macio_add_one_device allocates a dynamic device name but does not release the device_initialize reference when of_device_register fails, preventing kobject_cleanup from freeing the name. Reachability requires the Macintosh macio device path and a registration failure; the resulting leak has no disclosed confidentiality or integrity impact.
The record
- CVE
- CVE-2022-50474
- 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=1fa5ae857bb14f6046205171d98506d8112dd74e <19ded60b40e86b0903c8d5bd0161437ed5107a8b
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <2ac0a7059b7bcbed35bfffa34a82c9a9e99638ef
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <35858b87a943917fa30172aa4bf01ce7adbcb42c
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <3a866ff6fc2232c8e393cdb55ffb8ce947349e03
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <5ca86eae55a2f006e6c1edd2029b2cacb6979515
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <76837e7f6b30da72ad59f56291e22804a219e015
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <aa9054267366ff0a382d403d17728e21951ddbb9
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <b29a2f1dd33ae9b94821ab2f4d398b9081786748
- Affected versionversion=1fa5ae857bb14f6046205171d98506d8112dd74e <ca765257feb89dacf604ced9cd233db5f865dee0
- Affected versionversion=2.6.30
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