Memory Leak in NFC: nci_allocate_device

Kernel Updated 02 Oct 2025

Summary

04/06/2021
N/A
No i
Unrated
Not published

UVI-2021-1000614: NFC: nci: fix memory leak in nci_allocate_device. Affects Kernel versions >= 11f54f228643d0248ec00ce8c9fb8d872f87e7b8, < b34cb7ac32cc8e5471dc773180ea9ae676b1a745. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The NFC (Near Field Communication) functionality in the Linux Kernel allows devices to communicate wirelessly over short distances. The nci_allocate_device function is responsible for allocating memory for an NFC device. However, a memory leak vulnerability has been identified in this function, which could lead to the exhaustion of system resources over time.

Vulnerability Detail

The memory leak vulnerability in nci_allocate_device arises from a failure to release allocated memory when an error condition occurs. This can result in a gradual depletion of available memory, potentially leading to system instability or denial of service. The vulnerability was introduced in version v4.0 of the Linux Kernel and has been fixed in version v5.10.41.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

No workaround has been provided for this vulnerability.

Conclusion

The memory leak vulnerability in nci_allocate_device can have serious consequences for system stability and availability. It is crucial to update the Linux Kernel to version v5.10.41 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The memory leak vulnerability in nci_allocate_device can result in the gradual depletion of system resources, potentially leading to system instability or denial of service.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you in real-time if the vulnerability is present.

Yes, the vulnerability has been fixed in version v5.10.41 of the Linux Kernel. It is recommended to update to this version or a later one to mitigate the risk.

The details regarding the exploitability of this vulnerability have not been provided. However, it is always recommended to apply security patches and updates to protect against potential remote exploitation.

You can find more information about this vulnerability in the Open Source Vulnerability database entry at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/UVI-2021-1000614.json

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback