{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-50214 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50214 is a high-severity use after free vulnerability in Linux kernel, published on 18 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50214 and fix it if it is affected.\n\nWhat it is: CVE-2022-50214 is a high-severity use after free vulnerability in Linux kernel, published on 18 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50214 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50214/ (Markdown: https://insights.sbomify.com/CVE-2022-50214/index.md)","id":"CVE-2022-50214","markdown":"https://insights.sbomify.com/CVE-2022-50214/index.md","name":"CVE-2022-50214","record":{"aliases":["DEBIAN-CVE-2022-50214","GHSA-c35q-x63g-2qfh","UBUNTU-CVE-2022-50214"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the Linux kernel's coresight subsystem allows attackers to cause denial of service or potentially execute code.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: Clear the connection field properly\n\ncoresight devices track their connections (output connections) and\nhold a reference to the fwnode. When a device goes away, we walk through\nthe devices on the coresight bus and make sure that the references\nare dropped. This happens both ways:\n a) For all output connections from the device, drop the reference to\n    the target device via coresight_release_platform_data()\n\nb) Iterate over all the devices on the coresight bus and drop the\n   reference to fwnode if *this* device is the target of the output\n   connection, via coresight_remove_conns()-\u003ecoresight_remove_match().\n\nHowever, the coresight_remove_match() doesn't clear the fwnode field,\nafter dropping the reference, this causes use-after-free and\nadditional refcount drops on the fwnode.\n\ne.g., if we have two devices, A and B, with a connection, A -\u003e B.\nIf we remove B first, B would clear the reference on B, from A\nvia coresight_remove_match(). But when A is removed, it still has\na connection with fwnode still pointing to B. Thus it tries to  drops\nthe reference in coresight_release_platform_data(), raising the bells\nlike :\n\n[   91.990153] ------------[ cut here ]------------\n[   91.990163] refcount_t: addition on 0; use-after-free.\n[   91.990212] WARNING: CPU: 0 PID: 461 at lib/refcount.c:25 refcount_warn_saturate+0xa0/0x144\n[   91.990260] Modules linked in: coresight_funnel coresight_replicator coresight_etm4x(-)\n crct10dif_ce coresight ip_tables x_tables ipv6 [last unloaded: coresight_cpu_debug]\n[   91.990398] CPU: 0 PID: 461 Comm: rmmod Tainted: G        W       T 5.19.0-rc2+ #53\n[   91.990418] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Feb  1 2019\n[   91.990434] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   91.990454] pc : refcount_warn_saturate+0xa0/0x144\n[   91.990476] lr : refcount_warn_saturate+0xa0/0x144\n[   91.990496] sp : ffff80000c843640\n[   91.990509] x29: ffff80000c843640 x28: ffff800009957c28 x27: ffff80000c8439a8\n[   91.990560] x26: ffff00097eff1990 x25: ffff8000092b6ad8 x24: ffff00097eff19a8\n[   91.990610] x23: ffff80000c8439a8 x22: 0000000000000000 x21: ffff80000c8439c2\n[   91.990659] x20: 0000000000000000 x19: ffff00097eff1a10 x18: ffff80000ab99c40\n[   91.990708] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80000abf6fa0\n[   91.990756] x14: 000000000000001d x13: 0a2e656572662d72 x12: 657466612d657375\n[   91.990805] x11: 203b30206e6f206e x10: 6f69746964646120 x9 : ffff8000081aba28\n[   91.990854] x8 : 206e6f206e6f6974 x7 : 69646461203a745f x6 : 746e756f63666572\n[   91.990903] x5 : ffff00097648ec58 x4 : 0000000000000000 x3 : 0000000000000027\n[   91.990952] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00080260ba00\n[   91.991000] Call trace:\n[   91.991012]  refcount_warn_saturate+0xa0/0x144\n[   91.991034]  kobject_get+0xac/0xb0\n[   91.991055]  of_node_get+0x2c/0x40\n[   91.991076]  of_fwnode_get+0x40/0x60\n[   91.991094]  fwnode_handle_get+0x3c/0x60\n[   91.991116]  fwnode_get_nth_parent+0xf4/0x110\n[   91.991137]  fwnode_full_name_string+0x48/0xc0\n[   91.991158]  device_node_string+0x41c/0x530\n[   91.991178]  pointer+0x320/0x3ec\n[   91.991198]  vsnprintf+0x23c/0x750\n[   91.991217]  vprintk_store+0x104/0x4b0\n[   91.991238]  vprintk_emit+0x8c/0x360\n[   91.991257]  vprintk_default+0x44/0x50\n[   91.991276]  vprintk+0xcc/0xf0\n[   91.991295]  _printk+0x68/0x90\n[   91.991315]  of_node_release+0x13c/0x14c\n[   91.991334]  kobject_put+0x98/0x114\n[   91.991354]  of_node_put+0x24/0x34\n[   91.991372]  of_fwnode_put+0x40/0x5c\n[   91.991390]  fwnode_handle_put+0x38/0x50\n[   91.991411]  coresight_release_platform_data+0x74/0xb0 [coresight]\n[   91.991472]  coresight_unregister+0x64/0xcc [coresight]\n[   91.991525]  etm4_remove_dev+0x64/0x78 [coresight_etm4x]\n[   91.991563]  etm4_remove_amba+0x1c/0x2c [coresight_etm4x]\n[   91.991598]  amba_remove+0x3c/0x19c\n---truncated---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"coresight: Clear the connection field properly","id":"CVE-2022-50214","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"use_after_free","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"scsi: sg: Allow waiting for commands to complete on removed device","id":"CVE-2022-50215"},"packages":[],"prev":{"headline":"netfilter: nf_tables: do not allow SET_ID to refer to another table","id":"CVE-2022-50213"},"products":["Linux"],"published":"2025-06-18","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel's coresight subsystem allows attackers to cause denial of service or potentially execute code.","url":"https://insights.sbomify.com/CVE-2022-50214/"}