CVE-2022-50005

published 18 Jun 2025 · updated 11 May 2026

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

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2c71f5d55a86fd5969428abf525c1ae6b1c7b0f5, Kernel 50403ee6daddf0d7a14e9d3b51a377c39a08ec8c, Kernel 9c34c33893db7a80d0e4b55c23d3b65e29609cfb and 1 more.

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 syscalls could restart the cmd_timeout timer.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.5, >=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <2c71f5d55a86fd5969428abf525c1ae6b1c7b0f5, >=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <50403ee6daddf0d7a14e9d3b51a377c39a08ec8c, >=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <9c34c33893db7a80d0e4b55c23d3b65e29609cfb, >=c656aa4c27b17a8c70da223ed5ab42145800d6b5 <f1e941dbf80a9b8bab0bffbc4cbe41cc7f4c6fb62c71f5d55a86fd5969428abf525c1ae6b1c7b0f5, 50403ee6daddf0d7a14e9d3b51a377c39a08ec8c, 9c34c33893db7a80d0e4b55c23d3b65e29609cfb, f1e941dbf80a9b8bab0bffbc4cbe41cc7f4c6fb6

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50005 severity on Zeptric[![CVE-2022-50005](https://zeptric.io/badge/cve/CVE-2022-50005.svg)](https://zeptric.io/cve/CVE-2022-50005)