CVE-2026-31509

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-22. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

April 22, 2026

Last Modified

April 28, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb435d150ca74b4d40f77f1a2266f3636ed64a79
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d89b74bf08f067b55c03d7f999ba0a0e73177eb3
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca54e904a071aa65ef3ad46ba42d51aaac6b73b4
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ed00a3edc8597fe2333f524401e2889aa1b5edf
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5eef9ebec7f5738f12cadede3545c05b34bf5ac3
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4527025d440ce84bf56e75ce1df2e84cb8178616
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1edc12d2bbcb7a8d0f1088e6fccb9d8c01bb1289
generic

nfc: nci: fix circular locking dependency in nci_close_device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09143c0e8f3b03517e6233aad42f45c794d8df8e

Vendor Advisories for CVE-2026-31509(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 03:04 UTCOSV refresh
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-24 14:17 UTCEPSS rescore
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 17:03 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 05:59 UTCEG score recompute
  25. 2026-08-16 05:59 UTCVendor advisory
Show 75 more
  1. 2026-08-16 05:59 UTCGHSA enrichment
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 04:19 UTCEG score recompute
  5. 2026-08-14 04:19 UTCVendor advisory
  6. 2026-08-14 04:19 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 18:30 UTCEG score recompute
  9. 2026-08-12 18:30 UTCVendor advisory
  10. 2026-08-12 18:30 UTCGHSA enrichment
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-11 16:45 UTCEG score recompute
  13. 2026-08-11 16:45 UTCVendor advisory
  14. 2026-08-11 16:45 UTCGHSA enrichment
  15. 2026-08-10 12:10 UTCVendor advisory
  16. 2026-08-10 12:10 UTCGHSA enrichment
  17. 2026-08-09 12:41 UTCEG score recompute
  18. 2026-08-09 12:41 UTCVendor advisory
  19. 2026-08-09 12:41 UTCGHSA enrichment
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 12:28 UTCEG score recompute
  22. 2026-08-08 12:28 UTCVendor advisory
  23. 2026-08-08 12:28 UTCGHSA enrichment
  24. 2026-08-07 12:48 UTCEG score recompute
  25. 2026-08-07 12:48 UTCVendor advisory
  26. 2026-08-07 12:47 UTCGHSA enrichment
  27. 2026-08-06 13:46 UTCEPSS rescore
  28. 2026-08-05 23:05 UTCEG score recompute
  29. 2026-08-05 23:05 UTCVendor advisory
  30. 2026-08-05 23:05 UTCGHSA enrichment
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-04 10:38 UTCEPSS rescore
  34. 2026-08-03 21:14 UTCVendor advisory
  35. 2026-08-03 21:14 UTCGHSA enrichment
  36. 2026-08-02 12:09 UTCEG score recompute
  37. 2026-08-02 12:09 UTCVendor advisory
  38. 2026-08-02 12:09 UTCGHSA enrichment
  39. 2026-08-02 02:27 UTCEPSS rescore
  40. 2026-08-01 04:16 UTCEPSS rescore
  41. 2026-07-30 16:27 UTCEPSS rescore
  42. 2026-07-30 01:30 UTCEPSS rescore
  43. 2026-07-28 15:36 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-24 14:17 UTCEPSS rescore
  47. 2026-07-23 14:18 UTCEPSS rescore
  48. 2026-07-23 14:18 UTCEPSS rescore
  49. 2026-07-23 03:08 UTCEG score recompute
  50. 2026-07-22 14:08 UTCEPSS rescore
  51. 2026-07-22 14:08 UTCEPSS rescore
  52. 2026-07-21 15:24 UTCEPSS rescore
  53. 2026-07-21 15:24 UTCEPSS rescore
  54. 2026-07-20 17:08 UTCEPSS rescore
  55. 2026-07-20 17:08 UTCEPSS rescore
  56. 2026-07-19 23:48 UTCOSV refresh
  57. 2026-07-19 14:31 UTCEPSS rescore
  58. 2026-07-19 14:31 UTCEPSS rescore
  59. 2026-07-19 02:29 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-18 10:04 UTCEPSS rescore
  62. 2026-07-16 17:03 UTCEPSS rescore
  63. 2026-07-16 17:03 UTCEPSS rescore
  64. 2026-07-15 02:00 UTCEPSS rescore
  65. 2026-07-15 02:00 UTCEPSS rescore
  66. 2026-07-13 22:30 UTCEPSS rescore
  67. 2026-07-13 06:13 UTCEPSS rescore
  68. 2026-07-13 06:13 UTCEPSS rescore
  69. 2026-07-12 05:46 UTCEPSS rescore
  70. 2026-07-09 19:10 UTCEPSS rescore
  71. 2026-07-08 15:15 UTCEPSS rescore
  72. 2026-07-07 13:46 UTCEPSS rescore
  73. 2026-07-06 16:27 UTCEPSS rescore
  74. 2026-07-06 16:27 UTCEPSS rescore
  75. 2026-07-06 02:23 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31509?
CVE-2026-31509 is a medium vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: nfc: nci: fix circular locking dependency in nciclosedevice nciclosedevice() flushes rxwq and txwq while holding req_lock. This causes a circular locking dependency because ncirxwork() running on rxwq can end up taking reqlock too:…
When was CVE-2026-31509 disclosed?
CVE-2026-31509 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31509 actively exploited?
CVE-2026-31509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31509?
CVE-2026-31509 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31509, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31509

Explore →

Is Your Infrastructure Affected by CVE-2026-31509?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs