Local memory exhaustion via failed kernel-thread cleanup
Published Dec 8, 2025 · Updated May 11, 2026
Memory leak in the Linux RSI wireless coexistence driver allows local users to exhaust kernel memory during failed coexistence startup. The rsi_coex_attach() error path leaves the allocated coex_cb object unreleased when rsi_create_kthread() fails, rather than freeing it before returning. Reachability requires the RSI coexistence initialization path and a kernel-thread creation failure; repeated leaks can consume kernel memory and interrupt service.
Summary
What happened
Memory leak in the Linux RSI wireless coexistence driver allows local users to exhaust kernel memory during failed coexistence startup. The rsi_coex_attach() error path leaves the allocated coex_cb object unreleased when rsi_create_kthread() fails, rather than freeing it before returning. Reachability requires the RSI coexistence initialization path and a kernel-thread creation failure; repeated leaks can consume kernel memory and interrupt service.
The record
- CVE
- CVE-2022-50629
- Published
- Dec 8, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 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=2108df3c4b1856588ca2e7f641900c2bbf38467e <956fb851a6e19da5ab491e19c1bc323bb2c2cf6f
- Affected versionversion=2108df3c4b1856588ca2e7f641900c2bbf38467e <98259e0b6cf7f021da9fe4e11fbcce6ad6705ffe
- Affected versionversion=2108df3c4b1856588ca2e7f641900c2bbf38467e <ace789b1d465fae104cd37e49f6e1bcd1c8ff417
- Affected versionversion=2108df3c4b1856588ca2e7f641900c2bbf38467e <b56e60b3b158a93bc713437e8e466f401ff8cc9f
- Affected versionversion=2108df3c4b1856588ca2e7f641900c2bbf38467e <c4f1ded67a90fb3b2e679e2c90b78921d9246044
- Affected versionversion=2108df3c4b1856588ca2e7f641900c2bbf38467e <efc8df970561ff708379b89b348e16d3b410cc7b
- Affected versionversion=2108df3c4b1856588ca2e7f641900c2bbf38467e <fe4d7280cf4ddbea6536b596297c07662c7856fc
- Affected versionversion=4.17
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