Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54170: keys: Fix linking a duplicate key to a keyring's assoc_array

Noroxi assessment

Priority: Monitor (action score 0/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.20% (FIRST EPSS).
  • Fixed version: Linux Linux 00edfa6d4fe022942e2f2e6f3294ff13ef78b15c, 0a6b0ca58685be34979236f83f2b322635b80b32, 65bd66a794bfa059375ec834885bb610d75c0182.

Low priority for now. Upgrade to Linux Linux 00edfa6d4fe022942e2f2e6f3294ff13ef78b15c, 0a6b0ca58685be34979236f83f2b322635b80b32, 65bd66a794bfa059375ec834885bb610d75c0182 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: keys: Fix linking a duplicate key to a keyring's assoc_array When making a DNS query inside the kernel using dns_query(), the request code can in rare cases end up creating a duplicate index key in the assoc_array of the destination keyring. It is eventually found by a BUG_ON() check in the assoc_array implementation and results in a crash. Example report: [2158499.700025] kernel BUG at ../lib/assoc_array.c:652! [2158499.700039] invalid opcode: 0000 [#1] SMP PTI [2158499.700065] CPU: 3 PID: 31985 Comm: kworker/3:1 Kdump: loaded Not tainted 5.3.18-150300.59.90-default #1 SLE15-SP3 [2158499.700096] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 [2158499.700351] Workqueue: cifsiod cifs_resolve_server [cifs] [2158499.700380] RIP: 0010:assoc_array_insert+0x85f/0xa40 [2158499.700401] Code: ff 74 2b 48 8b 3b 49 8b 45 18 4c 89 e6 48 83 e7 fe e8 95 ec 74 00 3b 45 88 7d db 85 c0 79 d4 0f 0b 0f 0b 0f 0b e8 41 f2 be ff <0f> 0b 0f 0b 81 7d 88 ff ff ff 7f 4c 89 eb 4c 8b ad 58 ff ff ff 0f [2158499.700448] RSP: 0018:ffffc0bd6187faf0 EFLAGS: 00010282 [2158499.700470] RAX: ffff9f1ea7da2fe8 RBX: ffff9f1ea7da2fc1 RCX: 0000000000000005 [2158499.700492] RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000000 [2158499.700515] RBP: ffffc0bd6187fbb0 R08: ffff9f185faf1100 R09: 0000000000000000 [2158499.700538] R10: ffff9f1ea7da2cc0 R11: 000000005ed8cec8 R12: ffffc0bd6187fc28 [2158499.700561] R13: ffff9f15feb8d000 R14: ffff9f1ea7da2fc0 R15: ffff9f168dc0d740 [2158499.700585] FS: 0000000000000000(0000) GS:ffff9f185fac0000(0000) knlGS:0000000000000000 [2158499.700610] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [2158499.700630] CR2: 00007fdd94fca238 CR3: 0000000809d8c006 CR4: 00000000003706e0 [2158499.700702] Call Trace: [2158499.700741] ? key_alloc+0x447/0x4b0 [2158499.700768] ? __key_link_begin+0x43/0xa0 [2158499.700790] __key_link_begin+0x43/0xa0 [2158499.700814] request_key_and_link+0x2c7/0x730 [2158499.700847] ? dns_resolver_read+0x20/0x20 [dns_resolver] [2158499.700873] ? key_default_cmp+0x20/0x20 [2158499.700898] request_key_tag+0x43/0xa0 [2158499.700926] dns_query+0x114/0x2ca [dns_resolver] [2158499.701127] dns_resolve_server_name_to_ip+0x194/0x310 [cifs] [2158499.701164] ? scnprintf+0x49/0x90 [2158499.701190] ? __switch_to_asm+0x40/0x70 [2158499.701211] ? __switch_to_asm+0x34/0x70 [2158499.701405] reconn_set_ipaddr_from_hostname+0x81/0x2a0 [cifs] [2158499.701603] cifs_resolve_server+0x4b/0xd0 [cifs] [2158499.701632] process_one_work+0x1f8/0x3e0 [2158499.701658] worker_thread+0x2d/0x3f0 [2158499.701682] ? process_one_work+0x3e0/0x3e0 [2158499.701703] kthread+0x10d/0x130 [2158499.701723] ? kthread_park+0xb0/0xb0 [2158499.701746] ret_from_fork+0x1f/0x40 The situation occurs as follows: * Some kernel facility invokes dns_query() to resolve a hostname, for example, "abcdef". The function registers its global DNS resolver cache as current->cred.thread_keyring and passes the query to request_key_net() -> request_key_tag() -> request_key_and_link(). * Function request_key_and_link() creates a keyring_search_context object. Its match_data.cmp method gets set via a call to type->match_preparse() (resolves to dns_resolver_match_preparse()) to dns_resolver_cmp(). * Function request_key_and_link() continues and invokes search_process_keyrings_rcu() which returns that a given key was not found. The control is then passed to request_key_and_link() -> construct_alloc_key(). * Concurrently to that, a second task similarly makes a DNS query for "abcdef." and its result gets inserted into the DNS resolver cache. * Back on the first task, function construct_alloc_key() first runs __key_link_begin() to determine an assoc_array_edit operation to insert a new key. Index keys in the array are compared exactly as-is, using keyring_compare_object(). The operation ---truncated---

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-2023-54170

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Running WordPress? Scan your site free with WP Lens

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.

—

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

    • 5.3affected
    • df593ee23e05cdda16c8c995e5818779431bb29f and later · before 65bd66a794bfa059375ec834885bb610d75c0182affected · git
    • df593ee23e05cdda16c8c995e5818779431bb29f and later · before 0a6b0ca58685be34979236f83f2b322635b80b32affected · git
    • df593ee23e05cdda16c8c995e5818779431bb29f and later · before 9aecfebea24fe6071ace5cc9fd6d690b87276bbbaffected · git
    • df593ee23e05cdda16c8c995e5818779431bb29f and later · before 00edfa6d4fe022942e2f2e6f3294ff13ef78b15caffected · git
    • df593ee23e05cdda16c8c995e5818779431bb29f and later · before e091bb55af9a930801f83df78195a908a76e1479affected · git
    • df593ee23e05cdda16c8c995e5818779431bb29f and later · before d55901522f96082a43b9842d34867363c0cdbac5affected · git
    • before 5.3not affected · semver
    • 5.4.253 and later · up to and including 5.4.*not affected · semver
    • 5.10.188 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:7.2.0-362.13.1.el9_30:7.2.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-362.13.1.el9_30:5.14.0-362.13.1.el9_3

+56

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54167Dec 30, 2025 · m68k: mm: Move initrd phys_to_virt handling after paging_init()
    0Monitor
  • ← EarlierCVE-2023-54169Dec 30, 2025 · net/mlx5e: fix memory leak in mlx5e_ptp_open
    0Monitor
  • Later →CVE-2023-54171Dec 30, 2025 · tracing: Fix memory leak of iter->temp when reading trace_pipe
    0Monitor

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 Linux00edfa6d4fe022942e2f2e6f3294ff13ef78b15cVendor (CNA)
Linux Linux0a6b0ca58685be34979236f83f2b322635b80b32Vendor (CNA)
Linux Linux65bd66a794bfa059375ec834885bb610d75c0182Vendor (CNA)
Linux Linux9aecfebea24fe6071ace5cc9fd6d690b87276bbbVendor (CNA)
Linux Linuxd55901522f96082a43b9842d34867363c0cdbac5Vendor (CNA)
Linux Linuxe091bb55af9a930801f83df78195a908a76e1479Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.2.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-362.13.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

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

All records