LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49391: remoteproc: mtk_scp: Fix a potential double free

In the Linux kernel, the following vulnerability has been resolved: remoteproc: mtk_scp: Fix a potential double free 'scp->rproc' is allocated using devm_rproc_alloc(), so there is no need to free it explicitly in the remove function.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a double-free bug in the MediaTek SCP remote processor driver. A local user with low privileges could potentially cause serious confidentiality, integrity, or availability impact on affected systems. Exposure is likely limited to kernels and devices using this driver path.

Executive priority

Treat as high priority for affected MediaTek Linux fleets, especially embedded or appliance environments. It is not a broad internet-facing emergency based on the provided evidence, but affected local multi-user or exposed device contexts should patch promptly.

Technical view

The flaw is CWE-415 in remoteproc/mtk_scp remove handling. The source says scp->rproc is allocated with devm_rproc_alloc(), so explicit freeing in remove could free managed memory twice. CVSS 3.1 is 7.8 with local, low-privilege, no-user-interaction conditions.

Likely exposure

Most likely exposure is Linux 5.18-era systems or embedded devices using the MediaTek SCP remoteproc driver. Generic systems without this hardware or driver are less likely affected. Distribution kernels need separate verification because vendors may backport fixes without changing major version numbers.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The CVSS vector indicates a local attacker with low privileges and no user interaction could trigger high confidentiality, integrity, and availability impact.

Researcher notes

The source evidence identifies the bug class and fix rationale but does not provide exploit details or broad affected distro mapping. Focus validation on kernel provenance, driver reachability, and whether devm_rproc_alloc() ownership is corrected by the stable commits.

Mitigation direction

  • Update affected Linux kernels using vendor or distribution guidance.
  • Confirm the referenced upstream stable fixes are included in deployed kernels.
  • Prioritize MediaTek-based devices using the SCP remoteproc driver.
  • Limit untrusted local access until patched, where operationally feasible.

Validation and detection

  • Inventory Linux kernel versions across MediaTek-based systems.
  • Check whether the mtk_scp remoteproc driver is present or loaded.
  • Compare vendor kernel changelogs against the referenced stable commits.
  • Use distribution advisories to confirm backported fix status.
Prepared
Confidence
medium
Sources
4

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-415: 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-49391 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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: total

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49391Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
LinuxLinuxc1407ac1099ab9726c31d38d806f3150f494c494, c1407ac1099ab9726c31d38d806f3150f494c494unaffected
LinuxLinux5.18, 0, 5.18.4, 5.19affected
Weakness

CWE details

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

CWE-415 · source CWE mapping

Double Free

Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.