Medium

CVE-2025-71079 — 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 Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.1% (30-day exploitation probability)+0
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.1%

ahead of 1% of scored CVEs · Oct 14, 2026

Affects

Linux

Linux and 1 more

CVSS base

5.5

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)
Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	version c45cea83e13699bdfd47842e04d09dd43af4c371≥ 8a9c61c3ef187d8891225f9b932390670a43a0d3 and < e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012≥ 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and < ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5≥ 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and < 6b93c8ab6f6cda8818983a4ae3fcf84b023037b4≥ 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and < 8fc4632fb508432895430cd02b38086bdd649083≥ 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and < f3a8a7c1aa278f2378b2f3a10500c6674dffdfda≥ 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 and < 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5version 5ef16d2d172ee56714cff37cd005b98aba08ef5a and 12 more version ff169909eac9e00bf1aa0af739ba6ddfb1b1d135version 47244ac0b65bd74cc70007d8e1bac68bd2baad19≥ 73a0d12114b4bc1a9def79a623264754b9df698e and < 2e0831e9fc46a06daa6d4d8d57a2738e343130c3version 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6≥ 5.10.82 and < 5.10.248≥ 5.15.5 and < 5.15.198≥ 4.4.293 and < 4.5≥ 4.9.291 and < 4.10≥ 4.14.256 and < 4.15≥ 4.19.218 and < 4.20≥ 5.4.162 and < 5.5version 5.16	Vulnerable	CVE Program (cve.org) e CISA ADP
Linux	Linux Kernel	≥ 6.13 and < 6.18.4≥ 4.9.291 and < 4.10≥ 4.14.256 and < 4.15≥ 4.19.218 and < 4.20≥ 5.4.162 and < 5.5≥ 5.10.82 and < 5.10.248≥ 5.15.5 and < 5.15.198≥ 5.16.1 and < 6.1.160 and 12 more ≥ 6.2 and < 6.6.120≥ 6.7 and < 6.12.64≥ 4.4.293 and < 4.5version 5.16version 6.19-rc1version 6.19-rc2version 6.19-rc3version 6.19-rc4version 6.19-rc5version 6.19-rc6version 6.19-rc7version 6.19-rc8	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.5	CVSS 3.1	Medium	1.8	3.6	nvd@nist.gov via NIST National Vulnerability Database
5.5	CVSS 3.1	Medium	—	—	GitHub, Inc. via GitHub Security Advisories

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-667

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.10%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · linux/linux
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 5.5
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jan 13, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

2× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

git.kernel.org/stable/c/8fc4632fb508432895430cd02b38086bdd649083
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/2e0831e9fc46a06daa6d4d8d57a2738e343130c3
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/f3a8a7c1aa278f2378b2f3a10500c6674dffdfda
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/6b93c8ab6f6cda8818983a4ae3fcf84b023037b4
Patch, NIST National Vulnerability Database
git.kernel.org/stable/c/1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5
Patch, NIST National Vulnerability Database
github.com/advisories/GHSA-q63x-gg9g-q34f
GitHub Security Advisories
cert-portal.siemens.com/productcert/html/ssa-457936.html
NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2025-71079
GitHub Security Advisories
cert-portal.siemens.com/productcert/html/ssa-019113.html
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

CWE-667
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-71079 is "net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.