CVE-2021-46924: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: NFC: st21nfca: Fix memory leak in device probe and remove 'phy->pending_skb' is alloced when device probe, but forgot to free in the error handling path and remove path, this cause memory leak as follows: unreferenced object 0xffff88800bc06800 (size 512): comm "8", pid 11775, jiffies 4295159829 (age 9.032s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000d66c09ce>] __kmalloc_node_track_caller+0x1ed/0x450 [<00000000c93382b3>] kmalloc_reserve+0x37/0xd0 [<000000005fea522c>] __alloc_skb+0x124/0x380 [<0000000019f29f9a>] st21nfca_hci_i2c_probe+0x170/0x8f2 Fix it by freeing 'pending_skb' in error and remove.
AI Analysis
Technical Summary
CVE-2021-46924 is a vulnerability identified in the Linux kernel's NFC subsystem, specifically within the st21nfca driver responsible for interfacing with NFC hardware over I2C. The issue arises from a memory leak caused by improper error handling during the device probe and removal processes. When the device probe function allocates memory for 'phy->pending_skb' (a socket buffer), it fails to free this memory if an error occurs or when the device is removed. This results in unreferenced memory objects accumulating over time, which can degrade system performance and stability. The vulnerability is rooted in the kernel's failure to release allocated resources under error conditions, leading to resource exhaustion. The technical details include a backtrace showing the allocation path through __kmalloc_node_track_caller, kmalloc_reserve, __alloc_skb, and the st21nfca_hci_i2c_probe function. The fix involves ensuring that 'pending_skb' is properly freed in both error and removal paths, preventing the leak. This vulnerability affects specific Linux kernel versions identified by the provided commit hashes. There are no known exploits in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of this vulnerability is primarily related to system reliability and availability. Systems running affected Linux kernel versions with NFC hardware using the st21nfca driver may experience gradual memory leaks leading to increased memory consumption, potential system slowdowns, or crashes if the leak is severe and persistent. This can disrupt services relying on NFC functionality, such as contactless payment systems, access control, or secure authentication mechanisms. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting denial of service through resource exhaustion can impact critical infrastructure and business operations. Organizations with embedded Linux devices or IoT deployments using NFC may be particularly vulnerable. Given the lack of known exploits, the immediate risk is low, but unpatched systems could become targets for attackers aiming to degrade system availability.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Identify and inventory all Linux systems using NFC hardware with the st21nfca driver, particularly those running affected kernel versions. 2) Apply the official Linux kernel patches that fix the memory leak by ensuring 'pending_skb' is freed in error and removal paths. If official patches are not yet available, consider backporting the fix or upgrading to a kernel version that includes the patch. 3) Monitor system memory usage and logs for signs of memory leaks or abnormal resource consumption related to NFC device probing. 4) Implement proactive system restarts or resource cleanup procedures for embedded devices where patching is delayed. 5) Restrict access to NFC hardware interfaces to trusted users and processes to reduce the risk of triggering the vulnerability through malformed device interactions. 6) Engage with hardware vendors to confirm compatibility and patch availability for embedded devices. These steps go beyond generic advice by focusing on NFC-specific hardware and driver considerations and emphasizing proactive monitoring and inventory management.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2021-46924: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: NFC: st21nfca: Fix memory leak in device probe and remove 'phy->pending_skb' is alloced when device probe, but forgot to free in the error handling path and remove path, this cause memory leak as follows: unreferenced object 0xffff88800bc06800 (size 512): comm "8", pid 11775, jiffies 4295159829 (age 9.032s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000d66c09ce>] __kmalloc_node_track_caller+0x1ed/0x450 [<00000000c93382b3>] kmalloc_reserve+0x37/0xd0 [<000000005fea522c>] __alloc_skb+0x124/0x380 [<0000000019f29f9a>] st21nfca_hci_i2c_probe+0x170/0x8f2 Fix it by freeing 'pending_skb' in error and remove.
AI-Powered Analysis
Technical Analysis
CVE-2021-46924 is a vulnerability identified in the Linux kernel's NFC subsystem, specifically within the st21nfca driver responsible for interfacing with NFC hardware over I2C. The issue arises from a memory leak caused by improper error handling during the device probe and removal processes. When the device probe function allocates memory for 'phy->pending_skb' (a socket buffer), it fails to free this memory if an error occurs or when the device is removed. This results in unreferenced memory objects accumulating over time, which can degrade system performance and stability. The vulnerability is rooted in the kernel's failure to release allocated resources under error conditions, leading to resource exhaustion. The technical details include a backtrace showing the allocation path through __kmalloc_node_track_caller, kmalloc_reserve, __alloc_skb, and the st21nfca_hci_i2c_probe function. The fix involves ensuring that 'pending_skb' is properly freed in both error and removal paths, preventing the leak. This vulnerability affects specific Linux kernel versions identified by the provided commit hashes. There are no known exploits in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of this vulnerability is primarily related to system reliability and availability. Systems running affected Linux kernel versions with NFC hardware using the st21nfca driver may experience gradual memory leaks leading to increased memory consumption, potential system slowdowns, or crashes if the leak is severe and persistent. This can disrupt services relying on NFC functionality, such as contactless payment systems, access control, or secure authentication mechanisms. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting denial of service through resource exhaustion can impact critical infrastructure and business operations. Organizations with embedded Linux devices or IoT deployments using NFC may be particularly vulnerable. Given the lack of known exploits, the immediate risk is low, but unpatched systems could become targets for attackers aiming to degrade system availability.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Identify and inventory all Linux systems using NFC hardware with the st21nfca driver, particularly those running affected kernel versions. 2) Apply the official Linux kernel patches that fix the memory leak by ensuring 'pending_skb' is freed in error and removal paths. If official patches are not yet available, consider backporting the fix or upgrading to a kernel version that includes the patch. 3) Monitor system memory usage and logs for signs of memory leaks or abnormal resource consumption related to NFC device probing. 4) Implement proactive system restarts or resource cleanup procedures for embedded devices where patching is delayed. 5) Restrict access to NFC hardware interfaces to trusted users and processes to reduce the risk of triggering the vulnerability through malformed device interactions. 6) Engage with hardware vendors to confirm compatibility and patch availability for embedded devices. These steps go beyond generic advice by focusing on NFC-specific hardware and driver considerations and emphasizing proactive monitoring and inventory management.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-25T13:45:52.719Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9835c4522896dcbea6f2
Added to database: 5/21/2025, 9:09:09 AM
Last enriched: 6/26/2025, 9:52:34 AM
Last updated: 8/5/2025, 2:30:51 AM
Views: 19
Related Threats
CVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.