wifi: carl9170: re-fix fortified-memset warning
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.93, 6.6.33, 6.8.12, 6.9.3
- CVEs
- CVE-2024-38616
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 00:33 UTC · Revision 1
Source evidence
wifi: carl9170: re-fix fortified-memset warning
core-osv · Original sourcePublished 19 Jun 2024, 13:56 UTC
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.
osv:CVE-2024-38616
Kernel
Fixed versions: 6.1.93, 6.6.33, 6.8.12, 6.9.3
Complete source record
{
"id": "486c6d78840bb7ad904c234df520eb7e505bb55fe0ca46430e97c7ab7c33b408",
"url": "https://osv.dev/vulnerability/CVE-2024-38616",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "wifi: carl9170: re-fix fortified-memset warning",
"summary": "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.",
"evidence": "osv:CVE-2024-38616",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.93",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.33",
"evidence": "/affected/1/ranges"
},
{
"value": "6.8.12",
"evidence": "/affected/1/ranges"
},
{
"value": "6.9.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-38616",
"aliases": [
"CVE-2024-38616"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e"
},
{
"fixed": "13857683126e8a6492af73c74d702835f7a2175b"
},
{
"fixed": "87586467098281f04fa93e59fe3a516b954bddc4"
},
{
"fixed": "0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83"
},
{
"fixed": "042a39bb8e0812466327a5102606e88a5a4f8c02"
},
{
"fixed": "066afafc10c9476ee36c47c9062527a17e763901"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38616.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.17.0"
},
{
"fixed": "6.1.93"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.33"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.8.12"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.9.0"
},
{
"fixed": "6.9.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38616.json"
}
}
],
"modified": "2026-10-28T02:30:45.617856157Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/042a39bb8e0812466327a5102606e88a5a4f8c02",
"https://git.kernel.org/stable/c/066afafc10c9476ee36c47c9062527a17e763901",
"https://git.kernel.org/stable/c/0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83",
"https://git.kernel.org/stable/c/13857683126e8a6492af73c74d702835f7a2175b",
"https://git.kernel.org/stable/c/87586467098281f04fa93e59fe3a516b954bddc4",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38616.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-38616",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38616.json"
}
},
"related_cves": [
{
"value": "CVE-2024-38616",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 513519,
"published_at": "2024-06-19T13:56:16.086+00:00"
}