LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-71079 is a Linux kernel NFC issue that can deadlock kernel paths handling device unregister and rfkill writes. The described impact is availability: affected systems could hang in this code path. No CVSS score, CWE, or confirmed active exploitation is provided in the source bundle.

Executive priority

Treat this as a targeted availability risk, not an emergency internet-wide threat based on current evidence. Prioritize patching in Linux fleets, embedded devices, and operational environments where NFC is enabled or vendor advisories identify exposure.

Technical view

The flaw is an ABBA lock-ordering deadlock between device_lock and rfkill_global_mutex in nfc_unregister_device() and rfkill_fop_write(). The kernel fix moves rfkill_unregister() and rfkill_destroy() outside the device_lock critical section while preserving cleanup ordering through rfkill_global_mutex synchronization.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with NFC/rfkill code paths present. The bundle names Linux as the affected product and lists multiple stable kernel branches and commit references. Product-specific downstream exposure is not fully described except for a Siemens advisory reference.

Exploitation context

The source describes a concurrency deadlock, not a memory-corruption flaw or remote exploit path. KEV is false, and no cited source states active exploitation. Practical exploitability, required privileges, and trigger reliability are not established in the provided evidence.

Researcher notes

The key evidence is the lock inversion description and stable kernel commit references. The bundle lacks CVSS, CWE, attacker prerequisites, and exploit observations. Avoid assuming remote reachability or broad product impact beyond Linux and explicitly cited downstream advisories.

Mitigation direction

  • Identify Linux kernels in the affected ranges and prioritize systems with NFC functionality.
  • Apply vendor kernel updates containing the referenced stable fixes when available.
  • Review Siemens SSA-019113 for any product-specific status or update guidance.
  • If updates are unavailable, follow vendor guidance for temporary NFC or rfkill risk reduction.

Validation and detection

  • Compare deployed kernel versions against the CVE record and vendor advisories.
  • Inventory whether NFC and rfkill functionality are present or enabled on affected systems.
  • Confirm patched kernels include the referenced stable commits or downstream equivalents.
  • Monitor for unexplained hangs involving NFC device removal or rfkill operations.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71079 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux73a0d12114b4bc1a9def79a623264754b9df698e, 8a9c61c3ef187d8891225f9b932390670a43a0d3, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102, 5ef16d2d172ee56714cff37cd005b98aba08ef5a, ff169909eac9e00bf1aa0af739ba6ddfb1b1d135, 47244ac0b65bd74cc70007d8e1bac68bd2baad19, c45cea83e13699bdfd47842e04d09dd43af4c371, 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6, 5.10.82, 5.15.5, 4.4.293, 4.9.291, 4.14.256, 4.19.218, 5.4.162unaffected
LinuxLinux5.16, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.