Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31509: nfc: nci: fix circular locking dependency in nci_close_device

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.09% (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 09143c0e8f3b03517e6233aad42f45c794d8df8e, 1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289, 4527025d440ce84bf56e75ce1df2e84cb8178616; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 09143c0e8f3b03517e6233aad42f45c794d8df8e, 1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289, 4527025d440ce84bf56e75ce1df2e84cb8178616; azl3 kernel 6.6.130.1-3 on Azure Linux 3.0 6.6.134.1-2; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: nfc: nci: fix circular locking dependency in nci_close_device nci_close_device() flushes rx_wq and tx_wq while holding req_lock. This causes a circular locking dependency because nci_rx_work() running on rx_wq can end up taking req_lock too: nci_rx_work -> nci_rx_data_packet -> nci_data_exchange_complete -> __sk_destruct -> rawsock_destruct -> nfc_deactivate_target -> nci_deactivate_target -> nci_request -> mutex_lock(&ndev->req_lock) Move the flush of rx_wq after req_lock has been released. This should safe (I think) because NCI_UP has already been cleared and the transport is closed, so the work will see it and return -ENETDOWN. NIPA has been hitting this running the nci selftest with a debug kernel on roughly 4% of the runs.

Published
Apr 22, 2026
Updated
Nov 11, 2026
EPSS
0.0% · 0th 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.0%

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-2026-31509

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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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

    • 3.2affected
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before 7ed00a3edc8597fe2333f524401e2889aa1b5edfaffected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before 5eef9ebec7f5738f12cadede3545c05b34bf5ac3affected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before ca54e904a071aa65ef3ad46ba42d51aaac6b73b4affected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before eb435d150ca74b4d40f77f1a2266f3636ed64a79affected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before 1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289affected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before d89b74bf08f067b55c03d7f999ba0a0e73177eb3affected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before 09143c0e8f3b03517e6233aad42f45c794d8df8eaffected · git
    • 6a2968aaf50c7a22fced77a5e24aa636281efca8 and later · before 4527025d440ce84bf56e75ce1df2e84cb8178616affected · git
    • before 3.2not affected · semver
Affected versions · NVD (9)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.2.1 and later · before 5.10.253
  • linux linux kernel5.11 and later · before 5.15.203
  • linux linux kernel5.16 and later · before 6.1.168
  • linux linux kernel6.2 and later · before 6.6.131
  • linux linux kernel6.7 and later · before 6.12.80
  • linux linux kernel6.13 and later · before 6.18.21
  • linux linux kernel6.19 and later · before 6.19.11
  • linux linux kernel3.2
  • linux linux kernel7.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.11-16.19.11-1

Same product

linux: all records

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-2026-31507Apr 22, 2026 · net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer
    31Monitor
  • ← EarlierCVE-2026-31508Apr 22, 2026 · net: openvswitch: Avoid releasing netdev before teardown completes
    31Monitor
  • Later →CVE-2026-31510Apr 22, 2026 · Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb
    22Monitor

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 Linux09143c0e8f3b03517e6233aad42f45c794d8df8eVendor (CNA)
Linux Linux1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289Vendor (CNA)
Linux Linux4527025d440ce84bf56e75ce1df2e84cb8178616Vendor (CNA)
Linux Linux5eef9ebec7f5738f12cadede3545c05b34bf5ac3Vendor (CNA)
Linux Linux7ed00a3edc8597fe2333f524401e2889aa1b5edfVendor (CNA)
Linux Linuxca54e904a071aa65ef3ad46ba42d51aaac6b73b4Vendor (CNA)
Linux Linuxd89b74bf08f067b55c03d7f999ba0a0e73177eb3Vendor (CNA)
Linux Linuxeb435d150ca74b4d40f77f1a2266f3636ed64a79Vendor (CNA)
azl3 kernel 6.6.130.1-3 on Azure Linux 3.06.6.134.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.170-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

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records