LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50115: ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes We have sanity checks for byte controls and if any of the fail the locally allocated scontrol->ipc_control_data is freed up, but not set to NULL. On a rollback path of the error the higher level code will also try to free the scontrol->ipc_control_data which will eventually going to lead to memory corruption as double freeing memory is not a good thing.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can corrupt memory when an audio-related error path frees the same control data twice. The source bundle does not provide a CVSS score, exploitation evidence, or detailed prerequisites, so urgency depends on whether affected kernel lines and SOF audio components are present.

Executive priority

Treat as a targeted kernel maintenance item until stronger risk evidence appears. Patch through normal kernel update channels, prioritizing affected Linux hosts where audio/SOF functionality is in scope or vendor advisories mark exposure.

Technical view

CVE-2022-50115 affects Linux kernel ASoC SOF ipc3-topology handling. Failed byte-control sanity checks free scontrol->ipc_control_data without nulling it; rollback can free it again, causing memory corruption. The listed fix prevents the double free in the load_bytes path.

Likely exposure

Potential exposure is Linux systems on affected 5.18, 5.18.18, 5.19.2, or 6.0-related kernel lines using the affected ASoC SOF IPC3 topology code. The bundle does not define distribution-specific package versions, hardware prerequisites, or reachable attack surface.

Exploitation context

The bundle states CISA KEV is false and provides no cited evidence of active exploitation. It describes a memory-corruption flaw in an error rollback path, but does not establish whether exploitation is practical or whether access must be local.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. No CVSS, CWE, exploit status, or distribution mapping is supplied. Validation should focus on commit presence, branch exposure, and whether the affected SOF IPC3 topology path is compiled and reachable.

Mitigation direction

  • Check Linux distribution or device vendor advisories for fixed kernel packages.
  • Upgrade to a vendor kernel containing the referenced stable fixes.
  • Prioritize systems matching the listed affected kernel lines.
  • Track vendor backports by commit ID, not version number alone.
  • Avoid unsupported workarounds; follow vendor guidance if patching is delayed.

Validation and detection

  • Inventory running Linux kernel versions against the affected list.
  • Review vendor changelogs for the referenced stable commit IDs.
  • Confirm whether SOF ASoC IPC3 topology support is present on relevant systems.
  • After updating, verify audio initialization and kernel stability through normal regression testing.
Prepared
Confidence
medium
Sources
5

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-50115 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
4Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb5cee8feb1d482a9d07b677f4f2f9565bacda53e, b5cee8feb1d482a9d07b677f4f2f9565bacda53e, b5cee8feb1d482a9d07b677f4f2f9565bacda53eunaffected
LinuxLinux5.18, 0, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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