Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the WPCM450 interrupt controller initialization path. If a hardware mapping operation fails, allocated memory is not freed. The main business risk is local availability impact, not data theft or remote compromise.
Executive priority
Treat as a normal vulnerability management item unless WPCM450-based systems are business-critical. It is not documented as remotely exploitable or actively exploited, but availability impact justifies timely kernel maintenance.
Technical view
The flaw is a CWE-401 memory leak in wpcm450_aic_of_init(). When of_iomap() fails, the aic allocation is not released before returning. CVSS 3.1 is 5.5 with local access and low privileges required, no confidentiality or integrity impact, and high availability impact.
Likely exposure
Exposure appears limited to Linux kernels and deployments that include or use the wpcm450 irqchip driver. Exact distribution package exposure is not proven by the bundle, so teams should map their kernel version and vendor backports.
Exploitation context
The bundle does not show active exploitation, and KEV is false. The CVSS vector indicates local access with low privileges is required. The condition depends on an initialization failure path, so practical exploitability is not established here.
Researcher notes
Evidence is narrow: a kernel commit fixes a leak on an of_iomap() failure path. The source bundle does not provide exploit reports, operational triggers, or distribution-specific fixed package versions. Avoid broad product claims without vendor confirmation.
Mitigation direction
- Check vendor kernel advisories and package updates for CVE-2022-50416.
- Update to a kernel containing one of the referenced stable fixes.
- Prioritize systems using the wpcm450 irqchip driver.
- For appliances, confirm whether the vendor backported the fix.
- Monitor for vendor-specific guidance before applying unsupported kernel changes.
Validation and detection
- Inventory Linux kernel versions across affected device classes.
- Check whether deployed kernels include the referenced stable commits or vendor backports.
- Confirm whether wpcm450 irqchip support is present in relevant builds.
- Review vendor advisories for package names, fixed versions, and reboot requirements.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2022-50416 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/740efb64ca5e8f2b30ac843bc4ab07950479fed4CVE reference
- https://git.kernel.org/stable/c/bcbcb396e1a8bd4dcaabfb0d5b98abae70880470CVE reference
- https://git.kernel.org/stable/c/773c9d7f127f7a599d42ceed831de69f5aa22f03CVE reference
- https://git.kernel.org/stable/c/4208d4faf36573a507b5e5de17abe342e9276759CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.