wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1de0ca1d7320a645ba2ee5954f64be08935b002a, Kernel 581261b2d6fdb4237b24fa13f5a5f87bf2861f2c, Kernel 5fa329c44e1e635da2541eab28b6cdb8464fc8d1 and 6 more.
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan() Replace one-element array with a flexible-array member in `struct mwifiex_ie_types_wildcard_ssid_params` to fix the following warning on a MT8173 Chromebook (mt8173-elm-hana): [ 356.775250] ------------[ cut here ]------------ [ 356.784543] memcpy: detected field-spanning write (size 6) of single field "wildcard_ssid_tlv->ssid" at drivers/net/wireless/marvell/mwifiex/scan.c:904 (size 1) [ 356.813403] WARNING: CPU: 3 PID: 742 at drivers/net/wireless/marvell/mwifiex/scan.c:904 mwifiex_scan_networks+0x4fc/0xf28 [mwifiex] The "(size 6)" above is exactly the length of the SSID of the network this device was connected to. The source of the warning looks like: ssid_len = user_scan_in->ssid_list[i].ssid_len; [...] memcpy(wildcard_ssid_tlv->ssid, user_scan_in->ssid_list[i].ssid, ssid_len); There is a #define WILDCARD_SSID_TLV_MAX_SIZE that uses sizeof() on this struct, but it already didn't account for the size of the one-element array, so it doesn't need to be changed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.0, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <1de0ca1d7320a645ba2ee5954f64be08935b002a, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <581261b2d6fdb4237b24fa13f5a5f87bf2861f2c, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <5fa329c44e1e635da2541eab28b6cdb8464fc8d1, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <a09760c513ae0f98c7082a1deace7fb6284ee866, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <b466746cfb6be43f9a1457bbee52ade397fb23ea, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <c4698ef8c42e02782604bf4f8a489dbf6b0c1365, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <d241a139c2e9f8a479f25c75ebd5391e6a448500, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <d7774910c5583e61c5fe2571280366624ef48036, >=5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e <e2de22e4b6213371d9e76f74a10ce817572a8d74 | 1de0ca1d7320a645ba2ee5954f64be08935b002a, 581261b2d6fdb4237b24fa13f5a5f87bf2861f2c, 5fa329c44e1e635da2541eab28b6cdb8464fc8d1, a09760c513ae0f98c7082a1deace7fb6284ee866, b466746cfb6be43f9a1457bbee52ade397fb23ea, c4698ef8c42e02782604bf4f8a489dbf6b0c1365, d241a139c2e9f8a479f25c75ebd5391e6a448500, d7774910c5583e61c5fe2571280366624ef48036, e2de22e4b6213371d9e76f74a10ce817572a8d74 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket