CVE-2024-38616
"Linux WiFi Driver Carl9170 Fortified Memset Warning"
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: re-fix fortified-memset warning The carl9170_tx_release() function sometimes triggers a fortified-memset warning in my randconfig builds: In file included from include/linux/string.h:254, from drivers/net/wireless/ath/carl9170/tx.c:40: In function 'fortify_memset_chk', inlined from 'carl9170_tx_release' at drivers/net/wireless/ath/carl9170/tx.c:283:2, inlined from 'kref_put' at include/linux/kref.h:65:3, inlined from 'carl9170_tx_put_skb' at drivers/net/wireless/ath/carl9170/tx.c:342:9: include/linux/fortify-string.h:493:25: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning] 493 | __write_overflow_field(p_size_field, size); Kees previously tried to avoid this by using memset_after(), but it seems this does not fully address the problem. I noticed that the memset_after() here is done on a different part of the union (status) than the original cast was from (rate_driver_data), which may confuse the compiler. Unfortunately, the memset_after() trick does not work on driver_rates[] because that is part of an anonymous struct, and I could not get struct_group() to do this either. Using two separate memset() calls on the two members does address the warning though.
INFO
Published Date :
June 19, 2024, 2:15 p.m.
Last Modified :
April 1, 2025, 6:27 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
Yes !
Impact Score :
4.2
Exploitability Score :
3.9
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-38616.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-38616 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-38616 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 01, 2025
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.9 up to (excluding) 6.9.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.8.12 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.17 up to (excluding) 6.1.93 Added Reference Type kernel.org: https://git.kernel.org/stable/c/042a39bb8e0812466327a5102606e88a5a4f8c02 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/042a39bb8e0812466327a5102606e88a5a4f8c02 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/066afafc10c9476ee36c47c9062527a17e763901 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/066afafc10c9476ee36c47c9062527a17e763901 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/13857683126e8a6492af73c74d702835f7a2175b Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/13857683126e8a6492af73c74d702835f7a2175b Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/87586467098281f04fa93e59fe3a516b954bddc4 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/87586467098281f04fa93e59fe3a516b954bddc4 Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/042a39bb8e0812466327a5102606e88a5a4f8c02 Added Reference https://git.kernel.org/stable/c/066afafc10c9476ee36c47c9062527a17e763901 Added Reference https://git.kernel.org/stable/c/0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83 Added Reference https://git.kernel.org/stable/c/13857683126e8a6492af73c74d702835f7a2175b Added Reference https://git.kernel.org/stable/c/87586467098281f04fa93e59fe3a516b954bddc4 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jul. 03, 2024
Action Type Old Value New Value Added CWE CISA-ADP CWE-400 Added CVSS V3.1 CISA-ADP AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 19, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: re-fix fortified-memset warning The carl9170_tx_release() function sometimes triggers a fortified-memset warning in my randconfig builds: In file included from include/linux/string.h:254, from drivers/net/wireless/ath/carl9170/tx.c:40: In function 'fortify_memset_chk', inlined from 'carl9170_tx_release' at drivers/net/wireless/ath/carl9170/tx.c:283:2, inlined from 'kref_put' at include/linux/kref.h:65:3, inlined from 'carl9170_tx_put_skb' at drivers/net/wireless/ath/carl9170/tx.c:342:9: include/linux/fortify-string.h:493:25: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning] 493 | __write_overflow_field(p_size_field, size); Kees previously tried to avoid this by using memset_after(), but it seems this does not fully address the problem. I noticed that the memset_after() here is done on a different part of the union (status) than the original cast was from (rate_driver_data), which may confuse the compiler. Unfortunately, the memset_after() trick does not work on driver_rates[] because that is part of an anonymous struct, and I could not get struct_group() to do this either. Using two separate memset() calls on the two members does address the warning though. Added Reference kernel.org https://git.kernel.org/stable/c/13857683126e8a6492af73c74d702835f7a2175b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/87586467098281f04fa93e59fe3a516b954bddc4 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/042a39bb8e0812466327a5102606e88a5a4f8c02 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/066afafc10c9476ee36c47c9062527a17e763901 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-38616 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-38616
weaknesses.