CVE-2021-47288

published 21 May 2024 · updated 11 May 2026

media: ngene: Fix out-of-bounds bug in ngene_command_config_free_buf()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4487b968e5eacd02c493303dc2b61150bb7fe4b2, Kernel 8d4abca95ecc82fc8c41912fa0085281f19cc29f, Kernel b9a178f189bb6d75293573e181928735f5e3e070 and 5 more.

In the Linux kernel, the following vulnerability has been resolved: media: ngene: Fix out-of-bounds bug in ngene_command_config_free_buf() Fix an 11-year old bug in ngene_command_config_free_buf() while addressing the following warnings caught with -Warray-bounds: arch/alpha/include/asm/string.h:22:16: warning: '__builtin_memcpy' offset [12, 16] from the object at 'com' is out of the bounds of referenced subobject 'config' with type 'unsigned char' at offset 10 [-Warray-bounds] arch/x86/include/asm/string_32.h:182:25: warning: '__builtin_memcpy' offset [12, 16] from the object at 'com' is out of the bounds of referenced subobject 'config' with type 'unsigned char' at offset 10 [-Warray-bounds] The problem is that the original code is trying to copy 6 bytes of data into a one-byte size member _config_ of the wrong structue FW_CONFIGURE_BUFFERS, in a single call to memcpy(). This causes a legitimate compiler warning because memcpy() overruns the length of &com.cmd.ConfigureBuffers.config. It seems that the right structure is FW_CONFIGURE_FREE_BUFFERS, instead, because it contains 6 more members apart from the header _hdr_. Also, the name of the function ngene_command_config_free_buf() suggests that the actual intention is to ConfigureFreeBuffers, instead of ConfigureBuffers (which takes place in the function ngene_command_config_buf(), above). Fix this by enclosing those 6 members of struct FW_CONFIGURE_FREE_BUFFERS into new struct config, and use &com.cmd.ConfigureFreeBuffers.config as the destination address, instead of &com.cmd.ConfigureBuffers.config, when calling memcpy(). This also helps with the ongoing efforts to globally enable -Warray-bounds and get us closer to being able to tighten the FORTIFY_SOURCE routines on memcpy().

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.34, >=dae52d009fc950b5c209260d50fcc000f5becd3c <4487b968e5eacd02c493303dc2b61150bb7fe4b2, >=dae52d009fc950b5c209260d50fcc000f5becd3c <8d4abca95ecc82fc8c41912fa0085281f19cc29f, >=dae52d009fc950b5c209260d50fcc000f5becd3c <b9a178f189bb6d75293573e181928735f5e3e070, >=dae52d009fc950b5c209260d50fcc000f5becd3c <c6ddeb63dd543b5474b0217c4e47538b7ffd7686, >=dae52d009fc950b5c209260d50fcc000f5becd3c <e617fa62f6cf859a7b042cdd6c73af905ff8fca3, >=dae52d009fc950b5c209260d50fcc000f5becd3c <e818f2ff648581a6c553ae2bebc5dcef9a8bb90c, >=dae52d009fc950b5c209260d50fcc000f5becd3c <e991457afdcb5f4dbc5bc9d79eaf775be33e7092, >=dae52d009fc950b5c209260d50fcc000f5becd3c <ec731c6ef564ee6fc101fc5d73e3a3a953d09a004487b968e5eacd02c493303dc2b61150bb7fe4b2, 8d4abca95ecc82fc8c41912fa0085281f19cc29f, b9a178f189bb6d75293573e181928735f5e3e070, c6ddeb63dd543b5474b0217c4e47538b7ffd7686, e617fa62f6cf859a7b042cdd6c73af905ff8fca3, e818f2ff648581a6c553ae2bebc5dcef9a8bb90c, e991457afdcb5f4dbc5bc9d79eaf775be33e7092, ec731c6ef564ee6fc101fc5d73e3a3a953d09a00

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2021-47288 severity on Zeptric[![CVE-2021-47288](https://zeptric.io/badge/cve/CVE-2021-47288.svg)](https://zeptric.io/cve/CVE-2021-47288)