Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-38616, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Analyzed3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS (exploitation in 30 days)
0.65% · top 48% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

  • Linux · Linux

    • affected fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e – < 13857683126e8a6492af73c74d702835f7a2175b
    • affected fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e – < 87586467098281f04fa93e59fe3a516b954bddc4
    • affected fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e – < 0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83
    • affected fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e – < 042a39bb8e0812466327a5102606e88a5a4f8c02
    • affected fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e – < 066afafc10c9476ee36c47c9062527a17e763901
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.93 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.8.12 – ≤ 6.8.*
    • unaffected 6.9.3 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-38616 badge
[![CVE-2024-38616](https://cveledger.app/badge/CVE-2024-38616.svg)](https://cveledger.app/cve/CVE-2024-38616)

Record last updated .