CVE-2022-50049
Last modified
CVE-2022-50049 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ASoC: DPCM: Don't pick up BE without substream When DPCM tries to add valid BE connections at dpcm_add_paths(), it doesn't check whether the picked BE actually supports for the given stream direction. Due to that, when an asymmetric BE stream is present, it picks up wrongly and this may result in a NULL dereference at a later point where the code assumes the existence of a corresponding BE substream. This patch adds the check for the presence of the substream for the target BE for avoiding the problem above. Note that we have already some fix for non-existing BE substream at commit 6246f283d5e0 ("ASoC: dpcm: skip missing substream while applying symmetry"). EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ASoC: DPCM: Don't pick up BE without substream When DPCM tries to add valid BE connections at dpcm_add_paths(), it doesn't check whether the picked BE actually supports for the given stream direction. Due to that, when an asymmetric BE stream is present, it picks up wrongly and this may result in a NULL dereference at a later point where the code assumes the existence of a corresponding BE substream. This patch adds the check for the presence of the substream for the target BE for avoiding the problem above. Note that we have already some fix for non-existing BE substream at commit 6246f283d5e0 ("ASoC: dpcm: skip missing substream while applying symmetry"). But the code path we've hit recently is rather happening before the previous fix. So this patch tries to fix at picking up a BE instead of parsing BE lists.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.17, < 5.19.4 | — |
| Linux | Linux Kernel | 6.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-50049?
How severe is CVE-2022-50049?
How do I fix CVE-2022-50049?
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-50043In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50044In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2022-50045In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50046In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50047In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50048In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50050In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50051In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50052In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50053In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50054In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50055In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-50049?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
