LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49518: ASoC: SOF: ipc3-topology: Correct get_control_data for non bytes payload

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-topology: Correct get_control_data for non bytes payload It is possible to craft a topology where sof_get_control_data() would do out of bounds access because it expects that it is only called when the payload is bytes type. Confusingly it also handles other types of controls, but the payload parsing implementation is only valid for bytes. Fix the code to count the non bytes controls and instead of storing a pointer to sof_abi_hdr in sof_widget_data (which is only valid for bytes), store the pointer to the data itself and add a new member to save the size of the data. In case of non bytes controls we store the pointer to the chanv itself, which is just an array of values at the end. In case of bytes control, drop the wrong cdata->data (wdata[i].pdata) check against NULL since it is incorrect and invalid in this context. The data is pointing to the end of cdata struct, so it should never be null.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-49518 is a Linux kernel issue in the ASoC Sound Open Firmware topology parser. A crafted topology can cause out-of-bounds memory access. Public sources do not provide CVSS, exploitation evidence, or detailed business impact, so urgency depends on whether affected kernel versions and SOF audio components are present.

Executive priority

Handle through normal kernel patch management unless local exposure analysis shows broad SOF use on sensitive systems. There is no cited active exploitation or CVSS score, but kernel memory-safety defects should not remain untracked.

Technical view

In SOF ipc3-topology, sof_get_control_data() assumed byte-type payload parsing but could process non-byte controls. A crafted topology could trigger out-of-bounds access. The kernel fix changes how non-byte control data is counted and stored, and corrects bytes-control handling.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions listed by the CVE data, including 5.18, 5.18.3, and 5.19, where ASoC/SOF topology handling is relevant. Distribution backports may change exposure, so package-level verification is required.

Exploitation context

The source states a crafted topology can trigger the bug. It does not state remote exploitation, privilege requirements, impact beyond out-of-bounds access, or active exploitation. CISA KEV status is false in the provided data.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. No CWE, CVSS vector, exploit status, or detailed affected distribution matrix is provided. Validate exposure against distro backports rather than upstream version numbers alone.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize affected systems using ASoC/SOF audio topology support.
  • If no vendor update is available, follow vendor guidance.

Validation and detection

  • Inventory Linux kernel versions across relevant systems.
  • Check whether vendor kernels include the referenced stable commits.
  • Confirm whether ASoC/SOF components are enabled or deployed.
  • Document systems remaining on affected kernel builds.
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.

cve · low confidence lookup

CVE-2022-49518 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7006d20e5e9d25c079a82e2bc0ea7e292fdea6e6, 7006d20e5e9d25c079a82e2bc0ea7e292fdea6e6unaffected
LinuxLinux5.18, 0, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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