8.2
CWE
400
Advisory Published
CVE Published
Updated

CVE-2024-38616: wifi: carl9170: re-fix fortified-memset warning

First published: Wed Jun 19 2024(Updated: )

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.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.17<6.1.93
Linux Kernel>=6.2<6.6.33
Linux Kernel>=6.7<6.8.12
Linux Kernel>=6.9<6.9.3
debian/linux
5.10.223-1
5.10.234-1
6.1.129-1
6.1.135-1
6.12.22-1
6.12.25-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-38616?

    CVE-2024-38616 is considered to have a moderate severity level due to potential issues with memory handling in the Linux kernel.

  • How do I fix CVE-2024-38616?

    To fix CVE-2024-38616, upgrade to the updated kernel versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.

  • Can CVE-2024-38616 be exploited remotely?

    CVE-2024-38616 is not directly exploitable remotely as it primarily impacts the kernel and requires local access to exploit.

  • What versions of the Linux kernel are affected by CVE-2024-38616?

    The affected Linux kernel versions include those prior to updates identified in CVE-2024-38616, specifically prior to 5.10.223-1, 5.10.226-1, 6.1.123-1, and others listed in the advisory.

  • Is there a workaround for CVE-2024-38616 if I cannot update my kernel?

    Currently, there are no documented workarounds for CVE-2024-38616, so applying the kernel update is the recommended approach.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203