NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 51.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Linux Linux 042a39bb8e0812466327a5102606e88a5a4f8c02, 066afafc10c9476ee36c47c9062527a17e763901, 0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83.

Low priority for now. Upgrade to Linux Linux 042a39bb8e0812466327a5102606e88a5a4f8c02, 066afafc10c9476ee36c47c9062527a17e763901, 0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.2 · v3.1—No exploit Fix available

BDU:2024-11578

Published: Jun 19, 2024
Updated: Jun 17, 2026
EPSS: 0.6% · 51th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.17 and later · before 6.1.93
linux linux kernel6.2 and later · before 6.6.33
linux linux kernel6.7 and later · before 6.8.12
linux linux kernel6.9 and later · before 6.9.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.17affected
- fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e and later · before 13857683126e8a6492af73c74d702835f7a2175baffected · git
- fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e and later · before 87586467098281f04fa93e59fe3a516b954bddc4affected · git
- fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e and later · before 0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83affected · git
- fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e and later · before 042a39bb8e0812466327a5102606e88a5a4f8c02affected · git
- fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e and later · before 066afafc10c9476ee36c47c9062527a17e763901affected · git
- before 5.17not affected · semver
- 6.1.93 and later · up to and including 6.1.*not affected · semver
- 6.6.33 and later · up to and including 6.6.*not affected · semver
- 6.8.12 and later · up to and including 6.8.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.94-1	6.1.94-1
Debian:13	linux	before 6.8.12-1	6.8.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-38613Jun 19, 2024 · m68k: Fix spinlock race in kernel thread creation
18Monitor
← EarlierCVE-2024-38614Jun 19, 2024 · openrisc: traps: Don't send signals to kernel mode threads
22Monitor
Later →CVE-2024-38617Jun 19, 2024 · kunit/fortify: Fix mismatched kvalloc()/vfree() usage
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	042a39bb8e0812466327a5102606e88a5a4f8c02	Vendor (CNA)
Linux Linux	066afafc10c9476ee36c47c9062527a17e763901	Vendor (CNA)
Linux Linux	0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83	Vendor (CNA)
Linux Linux	13857683126e8a6492af73c74d702835f7a2175b	Vendor (CNA)
Linux Linux	87586467098281f04fa93e59fe3a516b954bddc4	Vendor (CNA)
debian:linux	6.1.94-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-394626 days apartclk: bcm: dvp: Assign ->num before accessing ->hws
39Monitor
CVE-2021-44406 days apartx86/xen: Drop USERGS_SYSRET64 paravirt call
35Monitor
CVE-2021-4731329 days apartcpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init
33Monitor
CVE-2021-47023112 days apartnet: marvell: prestera: fix port event handling on init
32Monitor
CVE-2022-487161 days apartASoC: codecs: wcd938x: fix incorrect used of portid
31Monitor
CVE-2024-383845 days apartblk-cgroup: fix list corruption from reorder of WRITE ->lqueued
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: low · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: Low
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

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

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/042a39bb8e0812466327a5102606e88a5a4f8c02

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records