LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49237: ath11k: add missing of_node_put() to avoid leak

In the Linux kernel, the following vulnerability has been resolved: ath11k: add missing of_node_put() to avoid leak The node pointer is returned by of_find_node_by_type() or of_parse_phandle() with refcount incremented. Calling of_node_put() to aovid the refcount leak.

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49237 is a Linux kernel issue in the ath11k wireless driver where a device-tree reference is not released, causing a reference-count leak. The published impact is availability only. It requires local access with low privileges, so urgency is lower than remote code execution but relevant for Linux endpoints, appliances, or embedded systems using affected kernels.

Executive priority

Treat as a routine but real availability-risk kernel update. Prioritize affected Linux fleets where wireless drivers are active, especially managed endpoints and embedded devices. No public active exploitation is indicated in the provided sources.

Technical view

The kernel fix adds missing of_node_put() calls after of_find_node_by_type() or of_parse_phandle(), preventing a device-node refcount leak in ath11k. The CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H with score 5.5. Public sources identify Linux kernel versions around 5.17 and stable fixes via referenced kernel commits.

Likely exposure

Exposure is most likely on Linux systems running affected 5.17-era kernels with ath11k driver code present or used. Distribution backports may change actual status, so kernel package provenance matters more than upstream version alone.

Exploitation context

The CVSS vector indicates local, low-privilege exploitation with no user interaction and availability impact. The source bundle does not show CISA KEV listing or other evidence of active exploitation.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. The issue is a reference-count leak, not a confidentiality or integrity flaw per CVSS. Validate using vendor kernel mappings because stable distributions may backport the fix without changing major kernel version.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported fixes and exact package versions.
  • Prioritize systems where ath11k is built, loaded, or used with Qualcomm Wi-Fi hardware.

Validation and detection

  • Inventory Linux kernel versions and distribution kernel package revisions.
  • Check whether ath11k is present, built, or loaded on relevant systems.
  • Confirm vendor advisories map installed packages to the referenced fixed commits.
  • Review availability monitoring for unexplained kernel or driver instability.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2022-49237 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-49237Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6ac04bdc5edb418787ab2040b1f922c23464c750, 6ac04bdc5edb418787ab2040b1f922c23464c750unaffected
LinuxLinux5.17, 0, 5.17.2, 5.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.