Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource-management flaw in a Qualcomm AOSS driver path. A local low-privileged user could potentially trigger a denial of service, affecting availability rather than data theft or tampering. The public record rates it medium severity.
Executive priority
Treat as a moderate availability risk. It is not a broad remote compromise signal, but embedded, mobile, or appliance fleets using Qualcomm-related kernels should verify patch status through vendor channels.
Technical view
In Linux kernel versions before 5.17.2, drivers/soc/qcom/qcom_aoss.c failed to release an of_find_device_by_node reference after use, such as with put_device. The issue maps to CWE-772 and has CVSS 3.1 score 5.5 with local, low-privilege availability impact.
Likely exposure
Exposure is most relevant to systems running affected Linux kernels before 5.17.2 where the Qualcomm AOSS driver code is present or backported. The source bundle’s affected product metadata is incomplete and lists vendor/product as n/a.
Exploitation context
No provided source indicates active exploitation, and this CVE is not listed as KEV in the bundle. The CVSS vector requires local access and low privileges, with no user interaction and high availability impact.
Researcher notes
The public description is narrow: missing reference release after of_find_device_by_node in qcom_aoss.c. Avoid expanding impact beyond local denial of service unless additional vendor analysis confirms reachable failure modes or affected downstream kernels.
Mitigation direction
- Upgrade to Linux kernel 5.17.2 or a vendor kernel containing the referenced fix.
- Check distribution or device vendor advisories for maintained backports.
- Prioritize Qualcomm SoC platforms where the qcom_aoss driver is used.
- Track kernel inventory for versions older than 5.17.2.
Validation and detection
- Identify hosts or firmware images running Linux kernels before 5.17.2.
- Confirm whether qcom_aoss.c or equivalent vendor backport is present.
- Verify vendor kernel changelogs include the referenced upstream commit or fix.
- Document systems where affected product metadata cannot be confirmed.
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-772: 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-2023-22996 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.
Missing Release of Resource after Effective Lifetime
Missing Release of Resource after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.