CVE-2022-49403: lib/string_helpers: fix not adding strarray to device's resource list
In the Linux kernel, the following vulnerability has been resolved:
lib/string_helpers: fix not adding strarray to device's resource list
Add allocated strarray to device's resource list. This is a must to
automatically release strarray when the device disappears.
Without this fix we have a memory leak in the few drivers which use
devm_kasprintf_strarray().
Security readout for executives and security teams
Plain-English summary
CVE-2022-49403 is a Linux kernel memory leak. In limited driver paths, allocated string arrays were not attached to the device resource list, so memory was not automatically released when a device disappeared. The main business risk is local availability degradation, not data theft or integrity loss.
Executive priority
Treat this as routine-to-priority kernel maintenance, not an emergency internet-facing incident. Patch affected Linux fleets through normal kernel update channels, with higher urgency for shared systems or environments where local users are not fully trusted.
Technical view
The issue is CWE-401 in lib/string_helpers: devm_kasprintf_strarray() failed to add allocated strarray objects to the device managed resource list. Drivers using that helper could leak memory across device removal events. CVSS 3.1 is 5.5: local, low-complexity, low-privilege, no user interaction, high availability impact only.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions listed in the CVE data and using drivers that call devm_kasprintf_strarray(). The source states only a few drivers use this helper, so exposure is narrower than a broad kernel-wide remote issue.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The CVSS vector requires local low-privilege access. The plausible impact is resource exhaustion or degraded availability through repeated leak conditions, but the provided sources do not describe exploit procedures.
Researcher notes
The root cause is missing device-managed resource registration for an allocated string array. The fix adds that allocation to the device resource list so cleanup occurs when the device disappears. The provided evidence does not identify specific drivers, distributions, or real-world exploitation.
Mitigation direction
Review vendor or distribution kernel advisories for CVE-2022-49403 fixes.
Update affected Linux kernels to versions containing the referenced stable commits.
Prioritize multi-user systems where local untrusted users can access relevant device paths.
Monitor systems for abnormal memory growth until patched.
Validation and detection
Inventory Linux kernel versions against the CVE affected-version data.
Confirm whether installed kernels include the referenced stable fixes.
Review enabled or loaded drivers for use of devm_kasprintf_strarray().
Check operational telemetry for unexplained memory growth after device removal events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.