Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26897: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete

Noroxi assessment

Priority: Monitor (action score 18/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.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 1bc5461a21c56a36e2a7d81e152b90ce019a3905, 24355fcb0d4cbcb6ddda262596558e8cfba70f11, 4afa0246656d5680c8a4c3fb37ba6570c4ab819b.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1bc5461a21c56a36e2a7d81e152b90ce019a3905, 24355fcb0d4cbcb6ddda262596558e8cfba70f11, 4afa0246656d5680c8a4c3fb37ba6570c4ab819b 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: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() instead of inside ath9k_tx_init()).

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Apr 17, 2024
Updated
Oct 15, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
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.

Follow CVE-2024-26897

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

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

  • debian debian linux10.0
  • linux linux kernel5.15.17 and later · before 5.15.153
  • linux linux kernel5.16.3 and later · before 6.1.83
  • linux linux kernel5.10.136 and later · before 5.10.214
  • linux linux kernel6.7 and later · before 6.7.11
  • linux linux kernel6.8 and later · before 6.8.2
  • linux linux kernel6.2 and later · before 6.6.23

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

    • 7bbc1a50a7963f14048f0e54b0b73159f86d4ea3, 5.17affected
    • 78c8397132dd4735ac6a7b5a651302f0b9f264ad and later · before 1bc5461a21c56a36e2a7d81e152b90ce019a3905affected · git
    • 735aefae7b68025cd04c482a940c0f6fc6797a63 and later · before f8ff4b4df71e87f609be0cc37d92e918107f9b90affected · git
    • 8b3046abc99eefe11438090bcc4ec3a3994b55d0 and later · before 74d0639261dd795dce958d1b14815bdcbb48a715affected · git
    • 8b3046abc99eefe11438090bcc4ec3a3994b55d0 and later · before a015fbf698c8957aa5fbeefc5c59dd2cf3107298affected · git
    • 8b3046abc99eefe11438090bcc4ec3a3994b55d0 and later · before ac90e22e735bac44f74b5161fb096fbeb0ff8bc2affected · git
    • 8b3046abc99eefe11438090bcc4ec3a3994b55d0 and later · before 4afa0246656d5680c8a4c3fb37ba6570c4ab819baffected · git
    • 8b3046abc99eefe11438090bcc4ec3a3994b55d0 and later · before 24355fcb0d4cbcb6ddda262596558e8cfba70f11affected · git
    • 5.10.136 and later · before 5.10.214affected · semver
    • 5.15.17 and later · before 5.15.153affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.31.1.el9_47.3.0-427.31.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4

+96

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-26894Apr 17, 2024 · ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()
    24Monitor
  • ← EarlierCVE-2024-26895Apr 17, 2024 · wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces
    31Monitor
  • Later →CVE-2024-26898Apr 17, 2024 · aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
    31Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Linux Linux1bc5461a21c56a36e2a7d81e152b90ce019a3905Vendor (CNA)
Linux Linux24355fcb0d4cbcb6ddda262596558e8cfba70f11Vendor (CNA)
Linux Linux4afa0246656d5680c8a4c3fb37ba6570c4ab819bVendor (CNA)
Linux Linux5.10.214Vendor (CNA)
Linux Linux5.15.153Vendor (CNA)
Linux Linux5.17Vendor (CNA)
Linux Linux74d0639261dd795dce958d1b14815bdcbb48a715Vendor (CNA)
Linux Linuxa015fbf698c8957aa5fbeefc5c59dd2cf3107298Vendor (CNA)
Linux Linuxac90e22e735bac44f74b5161fb096fbeb0ff8bc2Vendor (CNA)
Linux Linuxf8ff4b4df71e87f609be0cc37d92e918107f9b90Vendor (CNA)
almalinux:bpftool7.3.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+6

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.

No nightly-computed relations.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

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

nvd-primary

Attack context

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

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (8 more)

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

All records