Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50214: coresight: Clear the connection field properly

Noroxi assessment

Priority: Monitor (action score 31/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.23% (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 2af89ebacf299b7fba5f3087d35e8a286ec33706, 847b9273dd61567fb77617eabc5fa002594db062, b49b29ee113a87997bcca0bb0585bb46582846c1.

Low priority for now. Upgrade to Linux Linux 2af89ebacf299b7fba5f3087d35e8a286ec33706, 847b9273dd61567fb77617eabc5fa002594db062, b49b29ee113a87997bcca0bb0585bb46582846c1 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: coresight: Clear the connection field properly coresight devices track their connections (output connections) and hold a reference to the fwnode. When a device goes away, we walk through the devices on the coresight bus and make sure that the references are dropped. This happens both ways: a) For all output connections from the device, drop the reference to the target device via coresight_release_platform_data() b) Iterate over all the devices on the coresight bus and drop the reference to fwnode if *this* device is the target of the output connection, via coresight_remove_conns()->coresight_remove_match(). However, the coresight_remove_match() doesn't clear the fwnode field, after dropping the reference, this causes use-after-free and additional refcount drops on the fwnode. e.g., if we have two devices, A and B, with a connection, A -> B. If we remove B first, B would clear the reference on B, from A via coresight_remove_match(). But when A is removed, it still has a connection with fwnode still pointing to B. Thus it tries to drops the reference in coresight_release_platform_data(), raising the bells like : [ 91.990153] ------------[ cut here ]------------ [ 91.990163] refcount_t: addition on 0; use-after-free. [ 91.990212] WARNING: CPU: 0 PID: 461 at lib/refcount.c:25 refcount_warn_saturate+0xa0/0x144 [ 91.990260] Modules linked in: coresight_funnel coresight_replicator coresight_etm4x(-) crct10dif_ce coresight ip_tables x_tables ipv6 [last unloaded: coresight_cpu_debug] [ 91.990398] CPU: 0 PID: 461 Comm: rmmod Tainted: G W T 5.19.0-rc2+ #53 [ 91.990418] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Feb 1 2019 [ 91.990434] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 91.990454] pc : refcount_warn_saturate+0xa0/0x144 [ 91.990476] lr : refcount_warn_saturate+0xa0/0x144 [ 91.990496] sp : ffff80000c843640 [ 91.990509] x29: ffff80000c843640 x28: ffff800009957c28 x27: ffff80000c8439a8 [ 91.990560] x26: ffff00097eff1990 x25: ffff8000092b6ad8 x24: ffff00097eff19a8 [ 91.990610] x23: ffff80000c8439a8 x22: 0000000000000000 x21: ffff80000c8439c2 [ 91.990659] x20: 0000000000000000 x19: ffff00097eff1a10 x18: ffff80000ab99c40 [ 91.990708] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80000abf6fa0 [ 91.990756] x14: 000000000000001d x13: 0a2e656572662d72 x12: 657466612d657375 [ 91.990805] x11: 203b30206e6f206e x10: 6f69746964646120 x9 : ffff8000081aba28 [ 91.990854] x8 : 206e6f206e6f6974 x7 : 69646461203a745f x6 : 746e756f63666572 [ 91.990903] x5 : ffff00097648ec58 x4 : 0000000000000000 x3 : 0000000000000027 [ 91.990952] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00080260ba00 [ 91.991000] Call trace: [ 91.991012] refcount_warn_saturate+0xa0/0x144 [ 91.991034] kobject_get+0xac/0xb0 [ 91.991055] of_node_get+0x2c/0x40 [ 91.991076] of_fwnode_get+0x40/0x60 [ 91.991094] fwnode_handle_get+0x3c/0x60 [ 91.991116] fwnode_get_nth_parent+0xf4/0x110 [ 91.991137] fwnode_full_name_string+0x48/0xc0 [ 91.991158] device_node_string+0x41c/0x530 [ 91.991178] pointer+0x320/0x3ec [ 91.991198] vsnprintf+0x23c/0x750 [ 91.991217] vprintk_store+0x104/0x4b0 [ 91.991238] vprintk_emit+0x8c/0x360 [ 91.991257] vprintk_default+0x44/0x50 [ 91.991276] vprintk+0xcc/0xf0 [ 91.991295] _printk+0x68/0x90 [ 91.991315] of_node_release+0x13c/0x14c [ 91.991334] kobject_put+0x98/0x114 [ 91.991354] of_node_put+0x24/0x34 [ 91.991372] of_fwnode_put+0x40/0x5c [ 91.991390] fwnode_handle_put+0x38/0x50 [ 91.991411] coresight_release_platform_data+0x74/0xb0 [coresight] [ 91.991472] coresight_unregister+0x64/0xcc [coresight] [ 91.991525] etm4_remove_dev+0x64/0x78 [coresight_etm4x] [ 91.991563] etm4_remove_amba+0x1c/0x2c [coresight_etm4x] [ 91.991598] amba_remove+0x3c/0x19c ---truncated---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
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-2022-50214

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel5.3 and later · before 5.4.211
  • linux linux kernel5.5 and later · before 5.10.137
  • linux linux kernel5.11 and later · before 5.15.61
  • linux linux kernel5.16 and later · before 5.18.18
  • linux linux kernel5.19 and later · before 5.19.2

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
    • 37ea1ffddffa63c920ce826786fe610c78f57842 and later · before e9205d8dd1cafb7cff689ef9ddf06276a68f54a4affected · git
    • 37ea1ffddffa63c920ce826786fe610c78f57842 and later · before 847b9273dd61567fb77617eabc5fa002594db062affected · git
    • 37ea1ffddffa63c920ce826786fe610c78f57842 and later · before b49b29ee113a87997bcca0bb0585bb46582846c1affected · git
    • 37ea1ffddffa63c920ce826786fe610c78f57842 and later · before d43e967963c4d1b2b49f894d2f1b12865f87b098affected · git
    • 37ea1ffddffa63c920ce826786fe610c78f57842 and later · before bc57850fcb7e4cb91b6321d0ce83357cefd55c54affected · git
    • 37ea1ffddffa63c920ce826786fe610c78f57842 and later · before 2af89ebacf299b7fba5f3087d35e8a286ec33706affected · git
    • before 5.3not affected · semver
    • 5.4.211 and later · up to and including 5.4.*not affected · semver
    • 5.10.137 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.0.2-16.0.2-1
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-64k-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-64k-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-rt-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-570.12.1.el9_60:5.14.0-570.12.1.el9_6

+68

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-2022-50212Jun 18, 2025 · netfilter: nf_tables: do not allow CHAIN_ID to refer to another table
    31Monitor
  • ← EarlierCVE-2022-50213Jun 18, 2025 · netfilter: nf_tables: do not allow SET_ID to refer to another table
    31Monitor
  • Later →CVE-2022-50217Jun 18, 2025 · fuse: write inode in fuse_release()
    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 Linux2af89ebacf299b7fba5f3087d35e8a286ec33706Vendor (CNA)
Linux Linux847b9273dd61567fb77617eabc5fa002594db062Vendor (CNA)
Linux Linuxb49b29ee113a87997bcca0bb0585bb46582846c1Vendor (CNA)
Linux Linuxbc57850fcb7e4cb91b6321d0ce83357cefd55c54Vendor (CNA)
Linux Linuxd43e967963c4d1b2b49f894d2f1b12865f87b098Vendor (CNA)
Linux Linuxe9205d8dd1cafb7cff689ef9ddf06276a68f54a4Vendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.12.1.el9_6 · 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

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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