LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49746: dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init

In the Linux kernel, the following vulnerability has been resolved: dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init If the function sdma_load_context() fails, the sdma_desc will be freed, but the allocated desc->bd is forgot to be freed. We already met the sdma_load_context() failure case and the log as below: [ 450.699064] imx-sdma 30bd0000.dma-controller: Timeout waiting for CH0 ready ... In this case, the desc->bd will not be freed without this change.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can leak memory in the i.MX SDMA driver when a transfer setup failure occurs. The main business risk is local availability impact on systems using the affected driver, not data theft or remote compromise.

Executive priority

Handle through normal kernel patch management, with higher priority for embedded or operational systems using i.MX SDMA. This is not evidenced as remotely exploitable or actively exploited, but availability impact can matter on constrained or critical devices.

Technical view

In sdma_transfer_init, if sdma_load_context() fails, sdma_desc is freed but desc->bd is not. This is CWE-401 and has CVSS 5.5: local attack vector, low privileges, no confidentiality or integrity impact, and high availability impact.

Likely exposure

Exposure is most likely on Linux systems running affected kernel branches with the imx-sdma DMA controller driver enabled or used. The source lists Linux kernel versions and stable commit references, but does not identify specific distributions or appliances.

Exploitation context

The CVE is not marked KEV, and the provided sources do not report active exploitation. The CVSS vector indicates exploitation requires local access and low privileges, with the expected consequence being availability degradation through memory leakage.

Researcher notes

The important code path is sdma_transfer_init error handling after sdma_load_context() failure. The fix frees desc->bd before freeing the descriptor. Evidence is sufficient for root cause and impact class, but the provided sources do not establish real-world exploit activity.

Mitigation direction

  • Update affected Linux kernels through supported vendor or distribution packages.
  • Verify the update includes one of the referenced stable kernel fixes.
  • Prioritize systems using imx-sdma or i.MX DMA controller functionality.
  • If no package is available, monitor kernel and vendor guidance for backports.

Validation and detection

  • Inventory kernel versions against the affected versions listed in the CVE record.
  • Check whether the imx-sdma driver or matching DMA controller is present.
  • Review system logs for sdma_load_context failure indicators such as CH0 timeout messages.
  • Confirm the running kernel includes the applicable stable fix commit.
Prepared
Confidence
high
Sources
8

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.

cwe · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-49746 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
7Source 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-49746Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux21420841a554dae8a193cd3454ba91d913cfc320, 21420841a554dae8a193cd3454ba91d913cfc320, 21420841a554dae8a193cd3454ba91d913cfc320, 21420841a554dae8a193cd3454ba91d913cfc320, 21420841a554dae8a193cd3454ba91d913cfc320, 21420841a554dae8a193cd3454ba91d913cfc320unaffected
LinuxLinux4.19, 0, 4.19.272, 5.4.231, 5.10.167, 5.15.92, 6.1.10, 6.2affected
Weakness

CWE details

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

CWE-401 · source CWE mapping

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.