Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is an error-handling bug in the vimc media driver. If initialization fails, the kernel calls the wrong cleanup function and can hit a warning condition. The rated impact is availability, not data theft or data modification.
Executive priority
Treat as a moderate Linux availability risk. It is not presented as remotely exploitable or actively exploited, but kernel availability issues deserve routine patch-cycle handling, especially on shared systems.
Technical view
CVE-2022-50340 affects Linux kernel vimc_init() cleanup logic. On platform_driver_register(&vimc_pdrv) failure, it calls platform_driver_unregister(&vimc_pdrv) instead of platform_device_unregister(&vimc_pdev), producing an unexpected driver unregister warning. CVSS 3.1 is 5.5, local, low complexity, low privilege, no user interaction, availability high.
Likely exposure
Exposure is limited to Linux systems with affected kernel versions where the vimc media driver is present and reachable locally. The source bundle does not identify network exposure, affected distributions, or default enablement.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates local, low-privilege availability impact with no confidentiality or integrity impact.
Researcher notes
The evidence is narrow: CVE text, CVSS, CWE-617, affected Linux entries, and stable kernel commits. It identifies the faulty error path but does not document exploitability beyond local availability impact.
Mitigation direction
- Check Linux kernel stable guidance for the listed fix commits.
- Upgrade affected kernels to vendor-supported builds containing the vimc cleanup fix.
- Prioritize systems where untrusted local users can access kernel module functionality.
- Track distribution advisories before applying kernel changes in production.
Validation and detection
- Inventory Linux kernel versions against the affected version data.
- Confirm whether the vimc driver is built, installed, or loadable.
- Verify deployed kernels include one of the referenced stable fixes.
- Review kernel logs for related unexpected driver unregister warnings.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 14d85b600bb1f6f8ef61fa8fc1907e2e623d8350
- Linux stable commit 9c9ff35d68691aaea85b2e93763772e23930b3a3
- Linux stable commit 681ac2902039d9b497b3ae18fdc204314979e61e
- Linux stable commit f38df8984ef1b45ba23888d0e232cc21a95bd04b
- Linux stable commit f74d3f326d1d5b8951ce263c59a121ecfa65e7c0
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-617: 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-50340 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/14d85b600bb1f6f8ef61fa8fc1907e2e623d8350CVE reference
- https://git.kernel.org/stable/c/9c9ff35d68691aaea85b2e93763772e23930b3a3CVE reference
- https://git.kernel.org/stable/c/681ac2902039d9b497b3ae18fdc204314979e61eCVE reference
- https://git.kernel.org/stable/c/f38df8984ef1b45ba23888d0e232cc21a95bd04bCVE reference
- https://git.kernel.org/stable/c/f74d3f326d1d5b8951ce263c59a121ecfa65e7c0CVE 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.
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.