CVE-2026-23167

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.7 from GitHub Security Advisory published 2026-02-14. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-5871 (ENISA EUVD) · GHSA-mg8f-6pj8-cf5j (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

nfc: nci: Fix race between rfkill and nci_unregister_device().

syzbot reported the splat below [0] without a repro.

It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill.

nci_dev.cmd_wq is only destroyed in nci_unregister_device(), which (I think) was called from virtual_ncidev_close() when syzbot close()d an fd of virtual_ncidev.

The problem is that nci_unregister_device() destroys nci_dev.cmd_wq first and then calls nfc_unregister_device(), which removes the device from rfkill by rfkill_unregister().

So, the device is still visible via rfkill even after nci_dev.cmd_wq is destroyed.

Let's unregister the device from rfkill first in nci_unregister_device().

Note that we cannot call nfc_unregister_device() before nci_close_device() because

1) nfc_unregister_device() calls device_del() which frees all memory allocated by devm_kzalloc() and linked to ndev->conn_info_list

2) nci_rx_work() could try to queue nci_conn_info to ndev->conn_info_list which could be leaked

Thus, nfc_unregister_device() is split into two functions so we can remove rfkill interfaces only before nci_close_device().

[0]: DEBUG_LOCKS_WARN_ON(1) WARNING: kernel/locking/lockdep.c:238 at hlock_class kernel/locking/lockdep.c:238 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at check_wait_context kernel/locking/lockdep.c:4854 [inline], CPU#0: syz.0.8675/6349 WARNING: kernel/locking/lockdep.c:238 at __lock_acquire+0x39d/0x2cf0 kernel/locking/lockdep.c:5187, CPU#0: syz.0.8675/6349 Modules linked in: CPU: 0 UID: 0 PID: 6349 Comm: syz.0.8675 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/13/2026 RIP: 0010:hlock_class kernel/locking/lockdep.c:238 [inline] RIP: 0010:check_wait_context kernel/locking/lockdep.c:4854 [inline] RIP: 0010:__lock_acquire+0x3a4/0x2cf0 kernel/locking/lockdep.c:5187 Code: 18 00 4c 8b 74 24 08 75 27 90 e8 17 f2 fc 02 85 c0 74 1c 83 3d 50 e0 4e 0e 00 75 13 48 8d 3d 43 f7 51 0e 48 c7 c6 8b 3a de 8d <67> 48 0f b9 3a 90 31 c0 0f b6 98 c4 00 00 00 41 8b 45 20 25 ff 1f RSP: 0018:ffffc9000c767680 EFLAGS: 00010046 RAX: 0000000000000001 RBX: 0000000000040000 RCX: 0000000000080000 RDX: ffffc90013080000 RSI: ffffffff8dde3a8b RDI: ffffffff8ff24ca0 RBP: 0000000000000003 R08: ffffffff8fef35a3 R09: 1ffffffff1fde6b4 R10: dffffc0000000000 R11: fffffbfff1fde6b5 R12: 00000000000012a2 R13: ffff888030338ba8 R14: ffff888030338000 R15: ffff888030338b30 FS: 00007fa5995f66c0(0000) GS:ffff8881256f8000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7e72f842d0 CR3: 00000000485a0000 CR4: 00000000003526f0 Call Trace: lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 touch_wq_lockdep_map+0xcb/0x180 kernel/workqueue.c:3940 __flush_workqueue+0x14b/0x14f0 kernel/workqueue.c:3982 nci_close_device+0x302/0x630 net/nfc/nci/core.c:567 nci_dev_down+0x3b/0x50 net/nfc/nci/core.c:639 nfc_dev_down+0x152/0x290 net/nfc/core.c:161 nfc_rfkill_set_block+0x2d/0x100 net/nfc/core.c:179 rfkill_set_block+0x1d2/0x440 net/rfkill/core.c:346 rfkill_fop_write+0x461/0x5a0 net/rfkill/core.c:1301 vfs_write+0x29a/0xb90 fs/read_write.c:684 ksys_write+0x150/0x270 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa59b39acb9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fa5995f6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fa59b615fa0 RCX: 00007fa59b39acb9 RDX: 0000000000000008 RSI: 0000200000000080 RDI: 0000000000000007 RBP: 00007fa59b408bf7 R08: ---truncated---

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 9, 2026
Patch available.
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eaa5da5130deda26420273d4610cf6e4f794ed75
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2492688bb9fed6ab6e313682c387ae71a66ebae
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd4412d5905ee580e96c48360dc98fcd9e6f3208
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3369fc5e6120a72169e71acd72e987907a682af
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ea4d96419fb20f15a52ce657d49f1e7c91eb7ac
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/546eba0b10989de9ccc7fd619e874a30561e2b88
Web page

nfc: nci: Fix race between rfkill and nci_unregister_device(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/126cd30cad37bc7c2c85fe2df2a522d4edf0a5c5

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1105.95) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.186~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1110.95) @ jammy2026-10-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1099.97) @ jammy2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1070 (5.15.0-1070.74) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1030.30) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-10-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.161) @ jammy2026-10-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1018.20~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-10-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1099.102~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57) @ jammy2026-10-23ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1097.93) @ jammy2026-10-23ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-10-23ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1019.19~24.04.3+1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1106.115~20.04.1) @ focal2026-10-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1031.31) @ noble2026-10-23ubuntu
linuxKernel @ 5.10.249 (fixes >=3.2.0)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)
  • every version up to 6.1.162-1: fixed in 6.1.162-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)
  • every version up to 6.12.69-1: fixed in 6.12.69-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)
  • every version up to 6.18.9-1: fixed in 6.18.9-1
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 180 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23167?
CVE-2026-23167 is a medium-severity vulnerability; its CVE record was published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: nfc: nci: Fix race between rfkill and nci_unregister_device(). syzbot reported the splat below [0] without a repro. It indicates that struct nci_dev.cmd_wq had been destroyed before nci_close_device() was called via rfkill.…
When was the CVE record for CVE-2026-23167 published?
The CVE record for CVE-2026-23167 was published on February 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-23167 actively exploited?
CVE-2026-23167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23167?
CVE-2026-23167 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-23167?
A fix for CVE-2026-23167 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-23167?

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

Book a Demo →Browse All CVEs