Shift-Out-of-Bound Vulnerability in nvmem Package

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1001975: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells. Affects Kernel versions >= 69aba7948cbe53f2f1827e84e9dd0ae470a5072e, < eb0fc8e7170e61eaf65d28dee4a8baf4e86b19ca. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The nvmem package is a component of the Linux Kernel ecosystem. It provides an interface for accessing non-volatile memory devices, such as EEPROMs and flash memory, from user space. This package is responsible for managing the storage and retrieval of data in these memory devices. However, a vulnerability has been discovered in the nvmem package that can lead to a shift-out-of-bound issue when byte size cells are used. This vulnerability can potentially result in undefined behavior and may be exploited by attackers to gain unauthorized access or cause system instability.

Vulnerability Detail

The shift-out-of-bound vulnerability in the nvmem package occurs when byte size cells are manipulated in a way that exceeds the valid range. This can lead to undefined behavior, including memory corruption or data loss. Attackers may exploit this vulnerability to execute arbitrary code, escalate privileges, or crash the system. The vulnerability was introduced in version v4.3 of the Linux Kernel and has been fixed in version v4.19.213. It is important for users to update to the fixed version to mitigate the risk of exploitation.

How To Fix

No fixed version is published for this vulnerability.

To fix the shift-out-of-bound vulnerability in the nvmem package, users should update their Linux Kernel to version v4.19.213 or later. This can be done by obtaining the updated kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions. Once the updated kernel is installed, the vulnerability will be resolved.

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

Workaround

There is no specific workaround available for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the patched version.

Conclusion

The shift-out-of-bound vulnerability in the nvmem package of the Linux Kernel can have serious security implications. It is crucial for users to update their Linux Kernel to version v4.19.213 or later to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The shift-out-of-bound vulnerability in the nvmem package can potentially allow attackers to execute arbitrary code, escalate privileges, or crash the system.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate the risk.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. Attackers can send specially crafted requests to trigger the shift-out-of-bound issue and potentially gain unauthorized access or disrupt the system.

The only recommended solution is to update the Linux Kernel to the fixed version. Applying any other patches or workarounds may not fully address the underlying issue.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix the shift-out-of-bound vulnerability in the nvmem package, users should update their Linux Kernel to version v4.19.213 or later. This can be done by obtaining the updated kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions. Once the updated kernel is installed, the vulnerability will be resolved.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.