Kernel memory exhaustion via failed HNS registration
Published Sep 16, 2025 · Updated Sep 16, 2025
Memory leak in the Linux kernel HNS network driver allows local users to consume kernel memory when device registration fails during probing. In hnae_ae_register(), dev_set_name() allocates the class-device name, but a device_register() failure returns without releasing the reference that invokes kobject_cleanup(). The path requires local low-privileged access and a failed HiSilicon HNS device probe; repeated failures can interrupt service by depleting memory.
Summary
What happened
Memory leak in the Linux kernel HNS network driver allows local users to consume kernel memory when device registration fails during probing. In hnae_ae_register(), dev_set_name() allocates the class-device name, but a device_register() failure returns without releasing the reference that invokes kobject_cleanup(). The path requires local low-privileged access and a failed HiSilicon HNS device probe; repeated failures can interrupt service by depleting memory.
The record
- CVE
- CVE-2022-50352
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=4.4
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <02dc0db19d944b4a90941db505ecf1aaec714be4
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <2974f3b330ef25f5d34a4948d04290c2cd7802cf
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <3b78453cca046d3b03853f0d077ad3ad130db886
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <7ae1345f6ad715acbcdc9e1ac28153684fd498bb
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <91f8f5342bee726ed5692583d58f69e7cc9ae60e
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <a3c148955c22fe1d94d7a2096005679c1f22eddf
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <dfc0337c6dceb6449403b33ecb141f4a1458a1e9
- Affected versionversion=6fe6611ff275522a4e4c0359e2f46cdd07780d2f <ff2f5ec5d009844ec28f171123f9e58750cef4bf
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