Memory consumption via unreleased SDIO transmit buffers
Published Sep 17, 2026 · Updated Sep 17, 2026
Memory leakage in the mt792x SDIO driver in Linux 5.12 allows attackers to consume memory via rejected transmit frames. In drivers/net/wireless/mediatek/mt76/sdio.c, mt76s_tx_queue_skb returns when tx_prepare_skb fails without releasing the socket buffer, including when zero-length frames are rejected. Exposure requires the affected SDIO transmit path; repeated failures retain kernel memory, but the upstream disclosure does not establish an attacker-controlled trigger or a resulting crash or hang.
Summary
What happened
Memory leakage in the mt792x SDIO driver in Linux 5.12 allows attackers to consume memory via rejected transmit frames. In drivers/net/wireless/mediatek/mt76/sdio.c, mt76s_tx_queue_skb returns when tx_prepare_skb fails without releasing the socket buffer, including when zero-length frames are rejected. Exposure requires the affected SDIO transmit path; repeated failures retain kernel memory, but the upstream disclosure does not establish an attacker-controlled trigger or a resulting crash or hang.
The record
- CVE
- CVE-2026-90378
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=5.12
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <6a342db7a6502bc6781579145e05d4d4731786ab
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <6a8000c76dc34490a2bb321ad1a5f882a2ccab7c
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <808f2767d4217a5b96f674288573b9b89d432eed
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <9ef1351209d42b7d96604f2a13d7ea8215a24e07
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <b64d196280aff8494ba6fb387e37b18479c99b83
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <c2c7f16f2c62f79f7c381e500afa7123580742a5
- Affected versionversion=b747fa343817fd322b4463dda99d28fc51e19c52 <ddf6a17d8e3d0dbb841c13c10d7c1340a138a80d
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started