Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability bug in the Qualcomm LPG LED driver. A local, low-privileged user context is required by the CVSS vector. The issue can put sleeping code in an atomic context, which may destabilize the system. No source in the bundle shows active exploitation.
Executive priority
Handle through normal kernel patch management, with higher priority for Qualcomm-based Linux systems where local users or untrusted workloads are present. This is not evidenced as internet-exploited, but availability impact can matter for embedded, kiosk, mobile, or appliance-style deployments.
Technical view
The qcom-lpg LED driver used a brightness_set callback that could sleep, although that callback must be non-blocking. The upstream fix changes the driver to use brightness_set_blocking. The reported trace shows mutex locking during a timer/softirq path, consistent with CWE-667 locking misuse and availability impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernels with the qcom-lpg LED driver present or loaded, particularly Qualcomm-based platforms. The bundle lists Linux kernel versions or branches including 5.19, 6.0.16, 6.1.2, and 6.2 as affected, but does not fully define downstream vendor package status.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, and high availability impact. KEV is false, and the provided sources do not cite active exploitation. Treat this as a local denial-of-service risk unless vendor advisories provide more specific exploit evidence.
Researcher notes
The key behavioral flaw is blocking work in a non-blocking LED brightness callback. The fix direction is explicit in the source: use brightness_set_blocking. Evidence is strongest for the upstream kernel code path; downstream affected package ranges and exploitability details require vendor-specific confirmation.
Mitigation direction
- Update affected Linux kernels to a release containing the referenced stable qcom-lpg fix.
- Check distribution or device vendor advisories for backported kernel packages.
- Prioritize Qualcomm-platform systems that expose or load the qcom-lpg LED driver.
- If patching is delayed, review vendor guidance for driver-specific risk reduction.
Validation and detection
- Inventory kernel versions and compare them with vendor fixed releases or backport notes.
- Confirm whether the qcom-lpg LED driver is built, present, or loaded on target systems.
- Review kernel logs for sleeping-in-atomic warnings involving lpg brightness paths.
- Track the three referenced stable kernel commits in downstream package changelogs.
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-667: 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-50371 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
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.
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.