Menu

Star on GitHub · 3.2k

CVE-2022-50005

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout When the pn532 uart device is detaching, the pn532_uart_remove(…

Published Jun 18, 2025CWE-416EPSS 0.25%

Overview

CVE-2022-50005 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout

When the pn532 uart device is detaching, the pn532_uart_remove()

is called. But there are no functions in pn532_uart_remove() that

could delete the cmd_timeout timer, which will cause use-after-free

bugs. The process is shown below:

(thread 1) | (thread 2)

| pn532_uart_send_frame

pn532_uart_remove | mod_timer(&pn532->cmd_timeout,...)

... | (wait a time)

kfree(pn532) //FREE | pn532_cmd_timeout

| pn532_uart_send_frame

| pn532->... //USE

This patch adds del_timer_sync() in pn532_uart_remove() in order to

prevent the use-after-free bugs. What's more, the pn53x_unregister_nfc()

is well synchronized, it sets nfc_dev->shutting_down to true and there

are no syscal

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50005?

CVE-2022-50005 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-50005?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-50005?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50005?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50005 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all