CVE-2022-50734: 
Linux Debian vulnerability analysis and mitigation

Overview

CVE-2022-50734 is a memory leak (memleak) vulnerability in the Linux kernel's NVMEM (Non-Volatile Memory) subsystem, specifically within the nvmem_register() function. The flaw was disclosed on December 24, 2025, and affects Linux kernel versions starting from the introduction of the vulnerable code (commit de0534df93474f268486c486ea7e01b44a478026) up to the respective fix commits across stable branches. Fixed versions include kernel 5.15.75, 5.19.17, 6.0.3, and 6.1. The CVSS base score is listed as 0.0 (no official severity rating assigned), with Feedly estimating it as Medium severity (Feedly, ENISA EUVD).

Technical details

The root cause is a memory management error (CWE-401: Missing Release of Memory after Effective Lifetime) in the nvmem_register() function of the Linux kernel's NVMEM core subsystem. When dev_set_name() allocates memory for nvmem->dev.kobj.name, and a subsequent call to nvmem_validate_keepouts() fails, the function frees the nvmem structure and returns an error — but the memory allocated for the kobject name is never released, resulting in a kernel memory leak. The fix reorders the logic by moving nvmem_validate_keepouts() to execute after device_register(), allowing the device core's cleanup path to properly handle deallocation of the kobject name on error (Feedly, ENISA EUVD).

Impact

The vulnerability causes a kernel memory leak each time nvmem_register() is called and nvmem_validate_keepouts() fails, gradually consuming kernel memory over time. This primarily affects availability — repeated triggering of the error path could contribute to kernel memory exhaustion, potentially degrading system stability or performance. There is no direct confidentiality or integrity impact, and the vulnerability does not enable privilege escalation or remote code execution on its own (Feedly).

Exploitability

CVE-2022-50734 has an EPSS score of approximately 0.018% (0.000180), indicating a very low probability of exploitation in the wild. There is no known public proof-of-concept exploit, no evidence of in-the-wild exploitation, no threat actor attribution, and it is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The vulnerability requires local access and specific error conditions in the NVMEM subsystem to trigger (Feedly).

Mitigation and workarounds

The Linux kernel maintainers have addressed this vulnerability in the following stable releases: 5.15.75, 5.19.17, 6.0.3, and 6.1. The fix involves moving nvmem_validate_keepouts() after device_register() so that the device core properly handles kobject name memory cleanup on error. Users should update their Linux kernel to one of the patched versions. No configuration-based workaround is available; upgrading is the recommended remediation (ENISA EUVD, Kernel Git).

Additional resources


Source: This report was generated using AI

Related Linux Debian vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-116612HIGH7.8
  • Linux Debian logoLinux Debian
  • gstreamer-editing-services1.0
NoYesOct 26, 2026
CVE-2026-115909HIGH7.5
  • Linux Debian logoLinux Debian
  • rust-zip
NoNoOct 26, 2026
CVE-2026-115907HIGH7.5
  • Linux Debian logoLinux Debian
  • rust-zip
NoNoOct 26, 2026
CVE-2026-115910MEDIUM6.8
  • Python logoPython
  • social-auth-core
NoYesOct 26, 2026
CVE-2026-2270MEDIUM5.9
  • NixOS logoNixOS
  • kubernetes
NoYesOct 26, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management