{"id":"CVE-2021-47288","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ngene: Fix out-of-bounds bug in ngene_command_config_free_buf()\n\nFix an 11-year old bug in ngene_command_config_free_buf() while\naddressing the following warnings caught with -Warray-bounds:\n\narch/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]\narch/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]\n\nThe problem is that the original code is trying to copy 6 bytes of\ndata into a one-byte size member _config_ of the wrong structue\nFW_CONFIGURE_BUFFERS, in a single call to memcpy(). This causes a\nlegitimate compiler warning because memcpy() overruns the length\nof &com.cmd.ConfigureBuffers.config. It seems that the right\nstructure is FW_CONFIGURE_FREE_BUFFERS, instead, because it contains\n6 more members apart from the header _hdr_. Also, the name of\nthe function ngene_command_config_free_buf() suggests that the actual\nintention is to ConfigureFreeBuffers, instead of ConfigureBuffers\n(which takes place in the function ngene_command_config_buf(), above).\n\nFix this by enclosing those 6 members of struct FW_CONFIGURE_FREE_BUFFERS\ninto new struct config, and use &com.cmd.ConfigureFreeBuffers.config as\nthe destination address, instead of &com.cmd.ConfigureBuffers.config,\nwhen calling memcpy().\n\nThis also helps with the ongoing efforts to globally enable\n-Warray-bounds and get us closer to being able to tighten the\nFORTIFY_SOURCE routines on memcpy().","modified":"2026-03-23T05:06:21.911769Z","published":"2024-05-21T15:15:16.867Z","related":["SUSE-SU-2024:1979-1","SUSE-SU-2024:1983-1","SUSE-SU-2024:2010-1","SUSE-SU-2024:2183-1","SUSE-SU-2024:2184-1","SUSE-SU-2024:2185-1","SUSE-SU-2025:01995-1"],"references":[{"type":"FIX","url":"https://git.kernel.org/stable/c/e991457afdcb5f4dbc5bc9d79eaf775be33e7092"},{"type":"FIX","url":"https://git.kernel.org/stable/c/ec731c6ef564ee6fc101fc5d73e3a3a953d09a00"},{"type":"FIX","url":"https://git.kernel.org/stable/c/4487b968e5eacd02c493303dc2b61150bb7fe4b2"},{"type":"FIX","url":"https://git.kernel.org/stable/c/8d4abca95ecc82fc8c41912fa0085281f19cc29f"},{"type":"FIX","url":"https://git.kernel.org/stable/c/b9a178f189bb6d75293573e181928735f5e3e070"},{"type":"FIX","url":"https://git.kernel.org/stable/c/c6ddeb63dd543b5474b0217c4e47538b7ffd7686"},{"type":"FIX","url":"https://git.kernel.org/stable/c/e617fa62f6cf859a7b042cdd6c73af905ff8fca3"},{"type":"FIX","url":"https://git.kernel.org/stable/c/e818f2ff648581a6c553ae2bebc5dcef9a8bb90c"}],"affected":[{"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-47288.json","unresolved_ranges":[{"events":[{"introduced":"2.6.34"},{"fixed":"4.4.277"}]},{"events":[{"introduced":"4.5"},{"fixed":"4.9.277"}]},{"events":[{"introduced":"4.10"},{"fixed":"4.14.241"}]},{"events":[{"introduced":"4.15"},{"fixed":"4.19.199"}]},{"events":[{"introduced":"4.20"},{"fixed":"5.4.136"}]},{"events":[{"introduced":"5.5"},{"fixed":"5.10.54"}]},{"events":[{"introduced":"5.11"},{"fixed":"5.13.6"}]},{"events":[{"introduced":"0"},{"last_affected":"5.14-rc1"}]},{"events":[{"introduced":"0"},{"last_affected":"5.14-rc2"}]}]}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"}]}