CVE-2022-49518
Last modified
CVE-2022-49518 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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.. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.18, < 5.18.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-49518?
How severe is CVE-2022-49518?
How do I fix CVE-2022-49518?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49512In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49513In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49514In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49515In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49516In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49517In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49519In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-4952A vulnerability has been found in OmniSharp csharp-language-…7.5
- CVE-2022-49520In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49521In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49522In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49523In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49518?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
