LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38616: 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.

HighCVSS 8.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-38616 is a Linux kernel issue in the carl9170 Wi-Fi driver. The public record rates it high, mainly because impact could include availability disruption. The available sources describe a memory-clearing correction and compiler fortified-memset warning, not confirmed real-world exploitation.

Executive priority

Address during high-priority Linux patch cycles, focused on systems with relevant wireless driver exposure. There is no provided evidence of active exploitation, but the CVSS rating and kernel context justify timely remediation.

Technical view

The fix changes carl9170_tx_release() in drivers/net/wireless/ath/carl9170/tx.c to avoid a detected write beyond a field during memset handling. The CVE is mapped to CWE-400 with CVSS 3.1 score 8.2: network attack vector, no privileges, no user interaction, low integrity impact, high availability impact.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds that include or use the carl9170 wireless driver. Exact exposure depends on distribution backports and whether the affected driver is present or enabled.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It provides a high CVSS rating but limited public detail on a practical attack path. Treat as a kernel maintenance priority, especially on systems using the affected Wi-Fi driver.

Researcher notes

Public details are narrow and mostly describe the kernel code correction. The affected-version data in the bundle is not enough to derive precise distribution package exposure. Use upstream commits plus distribution advisories for authoritative validation.

Mitigation direction

  • Update to a vendor kernel containing the linked Linux stable fixes.
  • Check distribution advisories for exact fixed package versions.
  • Prioritize systems with carl9170 wireless driver exposure.
  • If patching is delayed, follow vendor guidance for temporary controls.

Validation and detection

  • Inventory Linux kernel versions across affected systems.
  • Determine whether carl9170 driver is present or enabled.
  • Verify installed kernels include the relevant stable commit or vendor backport.
  • Confirm vulnerability scanner results against distribution-specific fixed versions.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-38616 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H3.94.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2024-38616Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfb5f6a0e8063b7a84d6d44ef353846ccd7708d2e, fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e, fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e, fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e, fb5f6a0e8063b7a84d6d44ef353846ccd7708d2eunaffected
LinuxLinux5.17, 0, 6.1.93, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

CWE-400

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs