Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2025-71079

net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write

Medium5.5EPSS 0.11%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-71079, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 99% of all CVEs (9 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 73a0d12114b4bc1a9def79a623264754b9df698e – < 2e0831e9fc46a06daa6d4d8d57a2738e343130c3
    • affected 8a9c61c3ef187d8891225f9b932390670a43a0d3 – < e02a1c33f10a0ed3aba855ab8ae2b6c4c5be8012
    • affected 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 – < ee41f4f3ccf8cd6ba3732e867abbec7e6d8d12e5
    • affected 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 – < 6b93c8ab6f6cda8818983a4ae3fcf84b023037b4
    • affected 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 – < 8fc4632fb508432895430cd02b38086bdd649083
    • affected 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 – < f3a8a7c1aa278f2378b2f3a10500c6674dffdfda
    • affected 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 – < 1ab526d97a57e44d26fadcc0e9adeb9c0c0182f5
    • affected 5ef16d2d172ee56714cff37cd005b98aba08ef5a
    • affected ff169909eac9e00bf1aa0af739ba6ddfb1b1d135
    • affected 47244ac0b65bd74cc70007d8e1bac68bd2baad19
    • affected c45cea83e13699bdfd47842e04d09dd43af4c371
    • affected 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6
    • affected 5.10.82 – < 5.10.248
    • affected 5.15.5 – < 5.15.198
    • affected 4.4.293 – < 4.5
    • affected 4.9.291 – < 4.10
    • affected 4.14.256 – < 4.15
    • affected 4.19.218 – < 4.20
    • affected 5.4.162 – < 5.5
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.4 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71079 badge
[![CVE-2025-71079](https://cveledger.app/badge/CVE-2025-71079.svg)](https://cveledger.app/cve/CVE-2025-71079)

Record last updated .