ASoC Codecs va-macro: Array Out of Bounds Access Vulnerability
Summary
GSD-2022-1001878: ASoC: codecs: va-macro: fix accessing array out of bounds for enum type. Affects Kernel versions >= 908e6b1df26efc9d2df70c9a7bf4f5eae5c5702f, < 966408e37d84b762d11978b7bfb03fff0c6222ad. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The ASoC (Audio System on Chip) framework in the Linux Kernel provides support for audio drivers and codecs. Codecs are responsible for encoding and decoding audio data. One of the codecs, va-macro, is affected by an array out of bounds access vulnerability.
Vulnerability Detail
The vulnerability occurs when accessing an array out of bounds for an enum type in the va-macro codec. This can lead to memory corruption or crashes, potentially allowing an attacker to execute arbitrary code or cause a denial of service. The vulnerability was introduced in Linux Kernel version v5.11 and is fixed in version v5.15.33.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no known workaround for this vulnerability.
Conclusion
The ASoC va-macro codec in the Linux Kernel is affected by an array out of bounds access vulnerability. It is recommended to update the kernel to version v5.15.33 or later to fix the vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
ASoC stands for Audio System on Chip. It is a framework in the Linux Kernel that provides support for audio drivers and codecs.
va-macro is a codec in the ASoC framework responsible for encoding and decoding audio data.
An array out of bounds access vulnerability occurs when code tries to access an array element outside the bounds of the array. This can lead to memory corruption or crashes.
The vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial of service by exploiting the memory corruption or crashes.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
