Memory leak via missing receive callback
Published Dec 9, 2025 · Updated May 11, 2026
Memory leak in the ath9k HTC wireless driver in Linux allows local users to consume kernel memory through messages routed to an endpoint without a receive callback. The ath9k_htc_rx_msg() function passes service-message socket buffers to an endpoint receive callback but leaves the buffer allocated when that callback is absent. Reachability requires the affected receive path; repeated triggers can exhaust memory and interrupt service.
Summary
What happened
Memory leak in the ath9k HTC wireless driver in Linux allows local users to consume kernel memory through messages routed to an endpoint without a receive callback. The ath9k_htc_rx_msg() function passes service-message socket buffers to an endpoint receive callback but leaves the buffer allocated when that callback is absent. Reachability requires the affected receive path; repeated triggers can exhaust memory and interrupt service.
The record
- CVE
- CVE-2023-53802
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.35
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <564bc2222bf50eb6cdee715a5431bf4dc9f923c1
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <5a84e51f72580fc70066b03f3dac38421e702a0b
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <68171c006c8645a3e0293a6c3e6037c6538ac1c5
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <9b25e3985477ac3f02eca5fc1e0cc6850a3f7e69
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <b11f95f65cc52ee3a756e6f6a88df37a203e25bd
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <bbfababb4f899fe1556eac195f9774b6fe675fb6
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <c0c0614f143b568cd0e9525d53cf12e5dcd11987
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <ec246dfe006b2a8f36353f7489e4f525114db9a5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo