nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.140, 5.15.64, 5.19.6
- CVEs
- CVE-2022-50005
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:52 UTC · Revision 1
Source evidence
nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout
core-osv · Original sourcePublished 18 Jun 2025, 11:01 UTC
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.
osv:CVE-2022-50005
Kernel
Fixed versions: 5.10.140, 5.15.64, 5.19.6
Complete source record
{
"id": "f8df84e3a6c51eb90b6911557162a2a14215cbaa3a9afa25de4ec54245fa67bf",
"url": "https://osv.dev/vulnerability/CVE-2022-50005",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout",
"summary": "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.",
"evidence": "osv:CVE-2022-50005",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.140",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.64",
"evidence": "/affected/1/ranges"
},
{
"value": "5.19.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-50005",
"aliases": [
"CVE-2022-50005"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "c656aa4c27b17a8c70da223ed5ab42145800d6b5"
},
{
"fixed": "50403ee6daddf0d7a14e9d3b51a377c39a08ec8c"
},
{
"fixed": "9c34c33893db7a80d0e4b55c23d3b65e29609cfb"
},
{
"fixed": "2c71f5d55a86fd5969428abf525c1ae6b1c7b0f5"
},
{
"fixed": "f1e941dbf80a9b8bab0bffbc4cbe41cc7f4c6fb6"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50005.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.140"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.64"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.19.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50005.json"
}
}
],
"modified": "2026-10-28T02:30:26.662027213Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/2c71f5d55a86fd5969428abf525c1ae6b1c7b0f5",
"https://git.kernel.org/stable/c/50403ee6daddf0d7a14e9d3b51a377c39a08ec8c",
"https://git.kernel.org/stable/c/9c34c33893db7a80d0e4b55c23d3b65e29609cfb",
"https://git.kernel.org/stable/c/f1e941dbf80a9b8bab0bffbc4cbe41cc7f4c6fb6",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50005.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50005",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50005.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50005",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 493157,
"published_at": "2025-06-18T11:01:10.61+00:00"
}