Local memory exhaustion via unbounded rfkill events
Published Apr 24, 2026 · Updated Apr 24, 2026
Resource exhaustion in Linux Kernel 2.6.31 and later allows local users to exhaust memory through unconsumed rfkill events. The rfkill event path in net/rfkill/core.c queues a new event for each eligible userspace-triggered state change without limiting the number retained for an unread rfkill file descriptor. Exploitation requires low-privileged local access, an rfkill-enabled system, and an open descriptor whose pending events are not consumed; sustained allocation can interrupt the system through out-of-memory handling.
Summary
What happened
Resource exhaustion in Linux Kernel 2.6.31 and later allows local users to exhaust memory through unconsumed rfkill events. The rfkill event path in net/rfkill/core.c queues a new event for each eligible userspace-triggered state change without limiting the number retained for an unread rfkill file descriptor. Exploitation requires low-privileged local access, an rfkill-enabled system, and an open descriptor whose pending events are not consumed; sustained allocation can interrupt the system through out-of-memory handling.
The record
- CVE
- CVE-2026-31670
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4bcd1615a4e2a185ae9edd27b4143d7dfa7134f4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <673d2a3eef6e0ee9736501a150c9e4024a4e60a6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <80ce4cb026f0a4c4532b6cad827b44debda6256a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <82843afc19012a29ba863961ef494165aa1a88f4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a8c26800e0220e1550af012f5a20e50f5c78864d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b1e0c8d3ab58a0161db487bf5fc47adfcaf5d5ca
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e3842779547c83150569071d9980517cc9029fc0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ea245d78dec594372e27d8c79616baf49e98a4a1
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