net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write
In the Linux kernel, the following vulnerability has been resolved: net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write A deadlock can occur between nfc_unregister_device() and rfkill_fop_write() due to lock ordering inversion between device_lock and rfkill_global_mutex. The problematic lock order is: Thread A (rfkill_fop_write): rfkill_fop_write() mutex_lock(&rfkill_global_mutex) rfkill_set_block() nfc_rfkill_set_block() nfc_dev_down() device_lock(&dev->dev) <- waits for device_lock Thread B (nfc_unregister_device): nfc_unregister_device() device_lock(&dev->dev) rfkill_unregister() mutex_lock(&rfkill_global_mutex) <- waits for rfkill_global_mutex This creates a classic ABBA deadlock scenario. Fix this by moving rfkill_unregister() and rfkill_destroy() outside the device_lock critical section. Store the rfkill pointer in a local variable before releasing the lock, then call rfkill_unregister() after releasing device_lock. This change is safe because rfkill_fop_write() holds rfkill_global_mutex while calling the rfkill callbacks, and rfkill_unregister() also acquires rfkill_global_mutex before cleanup. Therefore, rfkill_unregister() will wait for any ongoing callback to complete before proceeding, and device_del() is only called after rfkill_unregister() returns, preventing any use-after-free. The similar lock ordering in nfc_register_device() (device_lock -> rfkill_global_mutex via rfkill_register) is safe because during registration the device is not yet in rfkill_list, so no concurrent rfkill operations can occur on this device.
- Published
- Jan 13, 2026
- Updated
- Sep 8, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-667
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.4.293 and later · before 4.5
- linux linux kernel4.9.291 and later · before 4.10
- linux linux kernel4.14.256 and later · before 4.15
- linux linux kernel4.19.218 and later · before 4.20
- linux linux kernel5.4.162 and later · before 5.5
- linux linux kernel5.10.82 and later · before 5.10.248
- linux linux kernel5.15.5 and later · before 5.15.198
- linux linux kernel5.16.1 and later · before 6.1.160
- linux linux kernel6.2 and later · before 6.6.120
- linux linux kernel6.7 and later · before 6.12.64
- linux linux kernel6.13 and later · before 6.18.4
- linux linux kernel5.16
- linux linux kernel6.19
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5ef16d2d172ee56714cff37cd005b98aba08ef5a, ff169909eac9e00bf1aa0af739ba6ddfb1b1d135, 47244ac0b65bd74cc70007d8e1bac68bd2baad19, c45cea83e13699bdfd47842e04d09dd43af4c371, 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6, 5.16affected
- 73a0d12114b4bc1a9def79a623264754b9df698e and later · before 2e0831e9fc46a06daa6d4d8d57a2738e343130c3affected · git
- 8a9c61c3ef187d8891225f9b932390670a43a0d3 and later · before e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012affected · git
- 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and later · before ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5affected · git
- 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and later · before 6b93c8ab6f6cda8818983a4ae3fcf84b023037b4affected · git
- 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and later · before 8fc4632fb508432895430cd02b38086bdd649083affected · git
- 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and later · before f3a8a7c1aa278f2378b2f3a10500c6674dffdfdaaffected · git
- 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and later · before 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5affected · git
- 5.10.82 and later · before 5.10.248affected · semver
- 5.15.5 and later · before 5.15.198affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.5-1 | 6.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5 | Vendor (CNA) |
| Linux Linux | 2e0831e9fc46a06daa6d4d8d57a2738e343130c3 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 5.10.248 | Vendor (CNA) |
| Linux Linux | 5.15.198 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6b93c8ab6f6cda8818983a4ae3fcf84b023037b4 | Vendor (CNA) |
| Linux Linux | 8fc4632fb508432895430cd02b38086bdd649083 | Vendor (CNA) |
| Linux Linux | e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012 | Vendor (CNA) |
| Linux Linux | ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5 | Vendor (CNA) |
| Linux Linux | f3a8a7c1aa278f2378b2f3a10500c6674dffdfda | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5
- git.kernel.org/stable/c/2e0831e9fc46a06daa6d4d8d57a2738e343130c3
- git.kernel.org/stable/c/6b93c8ab6f6cda8818983a4ae3fcf84b023037b4
- git.kernel.org/stable/c/8fc4632fb508432895430cd02b38086bdd649083
- git.kernel.org/stable/c/e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012
- git.kernel.org/stable/c/ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5
- git.kernel.org/stable/c/f3a8a7c1aa278f2378b2f3a10500c6674dffdfda
- cert-portal.siemens.com/productcert/html/ssa-019113.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.