Open Source Vulnerability in Kernel: nfc: nci: add flush_workqueue to prevent uaf
Summary
GSD-2022-1001658: nfc: nci: add flush_workqueue to prevent uaf. Affects Kernel versions >= 6a2968aaf50c7a22fced77a5e24aa636281efca8, < 9ded5ae40f4fe37fcc28f36d76bf45df20be5432. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Kernel is a crucial component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. The vulnerability in question affects the nfc (Near Field Communication) subsystem within the Kernel. NFC enables short-range wireless communication between devices, commonly used for contactless payments, data transfer, and device pairing. The vulnerability arises from a use-after-free (UAF) bug in the nci (NFC Controller Interface) module, which can be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition.
Vulnerability Detail
The vulnerability originates from a lack of proper memory management in the nci module of the nfc subsystem. Specifically, a use-after-free bug occurs when a workqueue is not properly flushed, leading to a situation where a pointer to freed memory is still accessible. This can be exploited by an attacker to manipulate the freed memory and execute arbitrary code or trigger a system crash. The impact of this vulnerability can range from unauthorized access to sensitive information to a complete system compromise. It is crucial to address this vulnerability promptly to ensure the security and stability of the affected systems.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.15.35 or later. The fix for this vulnerability was implemented in commit 9ded5ae40f4fe37fcc28f36d76bf45df20be5432. Updating the Kernel to the patched version will ensure that the necessary changes are applied to prevent the use-after-free vulnerability. It is advisable to follow the official documentation and guidelines provided by the Linux Kernel development team to ensure a successful update.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users can manually apply the patch provided in commit 9ded5ae40f4fe37fcc28f36d76bf45df20be5432 to their existing Kernel version. This involves modifying the affected code to include the necessary flush_workqueue function call. However, it is highly recommended to update to the latest stable version of the Kernel instead of relying solely on workarounds.
Conclusion
In conclusion, the nfc subsystem in the Linux Kernel is vulnerable to a use-after-free bug in the nci module. This vulnerability can be exploited to execute arbitrary code or cause a denial-of-service condition. It is crucial to update the Kernel to version v5.15.35 or later to mitigate this vulnerability. Alternatively, users can apply the provided patch as a temporary workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from unauthorized access to sensitive information to a complete system compromise. Attackers can exploit the use-after-free bug to execute arbitrary code or cause a denial-of-service (DoS) condition.
You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your application's manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.
Yes, a workaround is available. Users can manually apply the patch provided in commit 9ded5ae40f4fe37fcc28f36d76bf45df20be5432 to their existing Kernel version. However, it is recommended to update to the latest stable version of the Kernel for comprehensive vulnerability mitigation.
You can refer to the official Linux Kernel documentation and the commit 9ded5ae40f4fe37fcc28f36d76bf45df20be5432 in the Linux Kernel repository for more information about the fix for this vulnerability.
The discovery of this vulnerability was automated and reported by Vulert, a platform that monitors and alerts for open-source vulnerabilities in software. Vulert provides real-time vulnerability information without requiring access to the code or installation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.