CVE-2024-38616

wifi: carl9170: re-fix fortified-memset warning

Published Jun 19, 2024 CVSS 3.1 · 8.2 High EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-6949-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-6949-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-6952-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-6955-1 Linux kernel (OEM) vulnerabilities
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 8:20 PM
Reserved
Jun 18, 2024, 7:36 PM
Status
Analyzed
Published
Jun 19, 2024, 2:15 PM
Modified
Jun 17, 2026, 7:40 AM
Severity
Low
Public date
Jun 19, 2024, 12:00 AM