Menu

Star on GitHub · 3.2k

CVE-2022-49518

7.1 · HIGH

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_contr…

Published Feb 26, 2025CWE-125EPSS 0.25%

Overview

CVE-2022-49518 is a high-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-49518?

CVE-2022-49518 is a high-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2022-49518?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-49518?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-49518?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49518 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all