CVE-2024-38567 — wifi: carl9170: add a proper sanity check for endpoints
In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: add a proper sanity check for endpoints Syzkaller reports [1] hitting a warning which is caused by presence of a wrong endpoint type at the URB sumbitting stage. While there was a check for a specific 4th endpoint, since it can switch types between bulk and interrupt, other endpoints are trusted implicitly. Similar warning is triggered in a couple of other syzbot issues [2]. Fix the issue by doing a comprehensive check of all endpoints taking into account difference between high- and full-speed configuration. [1] Syzkaller report: ... WARNING: CPU: 0 PID: 4721 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 ... Call Trace: <TASK> carl9170_usb_send_rx_irq_urb+0x273/0x340 drivers/net/wireless/ath/carl9170/usb.c:504 carl9170_usb_init_device drivers/net/wireless/ath/carl9170/usb.c:939 [inline] carl9170_usb_firmware_finish drivers/net/wireless/ath/carl9170/usb.c:999 [inline] carl9170_usb_firmware_step2+0x175/0x240 drivers/net/wireless/ath/carl9170/usb.c:1028 request_firmware_work_func+0x130/0x240 drivers/base/firmware_loader/main.c:1107 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x669/0x1090 kernel/workqueue.c:2436 kthread+0x2e8/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 </TASK> [2] Related syzkaller crashes:
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < ac3ed46a8741d464bc70ebdf7433c1d786cf329dversion 2.6.37≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < b6dd09b3dac89b45d1ea3e3bd035a3859c0369a0≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < 0fa08a55201ab9be72bacb8ea93cf752d338184f≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < 03ddc74bdfd71b84a55c9f2185d8787f258422cd≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < 62eb07923f3693d55b0c2d9a5a4f1ad72cb6b8fd≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < 265c3cda471c26e0f25d0c755da94e1eb15d7a0c≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < 6a9892bf24c906b4d6b587f8759ca38bff672582 and 2 more≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < 8650725bb0a48b206d5a8ddad3a7488f9a5985b7≥ a84fab3cbfdc427e7d366f1cc844f27b2084c26c and < eb0f2fc3ff5806cc572cd9055ce7c52a01e97645 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 2.6.37 and < 4.19.316≥ 6.9 and < 6.9.3≥ 6.7 and < 6.8.12≥ 6.2 and < 6.6.33≥ 5.16 and < 6.1.93≥ 5.11 and < 5.15.161≥ 5.5 and < 5.10.219≥ 4.20 and < 5.4.278 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · linux/linux kernel
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2024
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
13 on the record
- git.kernel.org/stable/c/6a9892bf24c906b4d6b587f8759ca38bff672582
- git.kernel.org/stable/c/0fa08a55201ab9be72bacb8ea93cf752d338184f
- git.kernel.org/stable/c/62eb07923f3693d55b0c2d9a5a4f1ad72cb6b8fd
- git.kernel.org/stable/c/eb0f2fc3ff5806cc572cd9055ce7c52a01e97645
- git.kernel.org/stable/c/b6dd09b3dac89b45d1ea3e3bd035a3859c0369a0
- git.kernel.org/stable/c/8650725bb0a48b206d5a8ddad3a7488f9a5985b7
- git.kernel.org/stable/c/265c3cda471c26e0f25d0c755da94e1eb15d7a0c
- git.kernel.org/stable/c/03ddc74bdfd71b84a55c9f2185d8787f258422cd
- git.kernel.org/stable/c/ac3ed46a8741d464bc70ebdf7433c1d786cf329d
- github.com/advisories/GHSA-wgqj-6qph-jqhq
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- nvd.nist.gov/vuln/detail/CVE-2024-38567
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-38567 is "wifi: carl9170: add a proper sanity check for endpoints", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.