cbcvebase.
CVE-2024-38616
published 2024-06-19

CVE-2024-38616: In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: re-fix fortified-memset warning The carl9170_tx_release() function…

PriorityP340high8.2CVSS 3.1
AVNACLPRNUINSUCNILAH
EPSS
0.65%
47.1th percentile
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.

Affected

15 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.94-1 (bookworm)linux 6.1.94-1 (bookworm)
linuxlinux
linuxlinux>= fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e < 13857683126e8a6492af73c74d702835f7a2175b13857683126e8a6492af73c74d702835f7a2175b
linuxlinux>= fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e < 87586467098281f04fa93e59fe3a516b954bddc487586467098281f04fa93e59fe3a516b954bddc4
linuxlinux>= fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e < 0c38c9c460bb8ce8d6f6cf316e0d71a70983ec830c38c9c460bb8ce8d6f6cf316e0d71a70983ec83
linuxlinux>= fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e < 042a39bb8e0812466327a5102606e88a5a4f8c02042a39bb8e0812466327a5102606e88a5a4f8c02
linuxlinux>= fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e < 066afafc10c9476ee36c47c9062527a17e763901066afafc10c9476ee36c47c9062527a17e763901
linuxlinux_kernel>= 0 < 6.1.94-16.1.94-1
linuxlinux_kernel>= 0 < 6.8.12-16.8.12-1
linuxlinux_kernel>= 0 < 6.8.12-16.8.12-1
linuxlinux_kernel>= 0 < 6.8.0-40.406.8.0-40.40
linuxlinux_kernel>= 5.17 < 6.1.936.1.93
linuxlinux_kernel>= 6.2 < 6.6.336.6.33
linuxlinux_kernel>= 6.7 < 6.8.126.8.12
linuxlinux_kernel>= 6.9 < 6.9.36.9.3

CVSS provenance

nvdv3.18.2HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
osv8.2HIGH
vendor_debian8.2HIGH
vendor_redhat8.2HIGH
vendor_ubuntu6.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.