Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-71079: net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
  • 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.
  • Fixed version: Linux Linux 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5, 2e0831e9fc46a06daa6d4d8d57a2738e343130c3, 4.10; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5, 2e0831e9fc46a06daa6d4d8d57a2738e343130c3, 4.10; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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
Nov 10, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

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%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-71079

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.5-16.18.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-71077Jan 13, 2026 · tpm: Cap the number of PCR banks
    22Monitor
  • ← EarlierCVE-2025-71078Jan 13, 2026 · powerpc/64s/slb: Fix SLB multihit issue during SLB preload
    31Monitor
  • Later →CVE-2025-71082Jan 13, 2026 · Bluetooth: btusb: revert use of devm_kzalloc in btusb
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5Vendor (CNA)
Linux Linux2e0831e9fc46a06daa6d4d8d57a2738e343130c3Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux5.10.248Vendor (CNA)
Linux Linux5.15.198Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux6b93c8ab6f6cda8818983a4ae3fcf84b023037b4Vendor (CNA)
Linux Linux8fc4632fb508432895430cd02b38086bdd649083Vendor (CNA)
Linux Linuxe02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012Vendor (CNA)
Linux Linuxee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5Vendor (CNA)
Linux Linuxf3a8a7c1aa278f2378b2f3a10500c6674dffdfdaVendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.162-1 · Debian:12Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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 Locking

CVSS 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.

References

All records