Local service interruption via uninitialized wiphy work lock
Published Apr 16, 2025 · Updated May 23, 2026
Use of an uninitialized resource in affected Linux kernel releases allows local users to interrupt service after an rfkill allocation failure. The cfg80211_dev_free function takes wiphy_work_lock and accesses related work data even when rfkill allocation failed before that state was initialized. Exploitation requires low-privileged local access and the allocation-error path; the published impact is limited to availability.
Summary
What happened
Use of an uninitialized resource in affected Linux kernel releases allows local users to interrupt service after an rfkill allocation failure. The cfg80211_dev_free function takes wiphy_work_lock and accesses related work data even when rfkill allocation failed before that state was initialized. Exploitation requires low-privileged local access and the allocation-error path; the published impact is limited to availability.
The record
- CVE
- CVE-2025-22119
- Published
- Apr 16, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=0272d4af7f92997541d8bbf4c51918b93ded6ee2 <b679fe84cd5cc6f3481b7131fd28676191ad2615
- Affected versionversion=6.1.132 <6.1.142
- Affected versionversion=6.12.20 <6.12.35
- Affected versionversion=6.13.8 <6.14
- Affected versionversion=6.14
- Affected versionversion=6.6.84 <6.6.95
- Affected versionversion=72d520476a2fab6f3489e8388ab524985d6c4b90 <2617f60c3613ef105b8db2d514d2cac2a1836f7d
- Affected versionversion=72d520476a2fab6f3489e8388ab524985d6c4b90 <fc88dee89d7b63eeb17699393eb659aadf9d9b7c
- Affected versionversion=75d262ad3c36d52852d764588fcd887f0fcd9138 <eeacfbab984200dcdcd68fcf4c6e91e2c6b38792
- Affected versionversion=8930a3e1568cf534f86c8ed2def817c6d0528fc1 <7e6040853f5b5f067a18c52286e676bc298fe6a2
- Affected versionversion=a5158d67bff06cb6fea31be39aeb319fd908ed8e <60606efbf52582c0ab93e99789fddced6b47297a
- Affected versionversion=dea22de162058216a90f2706f0d0b36f0ff309fd
What conditions does exploitation require?
What is affected?
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
- syzbot cfg80211_dev_free C reproducerproof of concept · demonstrated
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