Critical Logical Key Offset Vulnerability in Linux Kernel's dm-pcache

Updated 19 Oct 2026

Summary

18/10/2026
N/A
Yes i
Unrated
Not published

CVE-2026-98867: dm-pcache: bound the logical key offset from persistent memory. Affects across 5 version ranges.

>= 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0, < 3d5a87cb909c1f375f08065b20123fa5db5958d8 >= 6.18.0, < 6.18.52 >= 6.19.0, < 7.2.10 < 97fc4b53dbe4a983fdf093243067fa6a64562307 < 10449703200076980704894c3d68d6796182371b

Fixed in 6.18.52 or 7.2.10, depending on the release line you run. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux Kernel is a core component of many operating systems, providing essential services and managing hardware resources. The dm-pcache module is responsible for caching data to improve performance. However, it has been found to have a vulnerability that could lead to serious security issues if exploited.

Vulnerability Detail

The vulnerability, identified as CVE-2026-98867, arises from the dm-pcache module's handling of logical key offsets from persistent memory. Specifically, the cache_key_decode() function does not properly validate the key's logical offset before using it to index into an array. This oversight can lead to out-of-bounds memory access, allowing an attacker to manipulate memory and potentially execute arbitrary code. The vulnerability affects versions of the Linux Kernel prior to the fixed versions, making it critical for users to address it promptly.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.18.0, < 6.18.52 6.18.52
  • >= 6.19.0, < 7.2.10 7.2.10

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, users can avoid using the dm-pcache module until the kernel is updated. This can be done by disabling the module in the kernel configuration or by not using features that rely on it.

Conclusion

The CVE-2026-98867 vulnerability in the Linux Kernel's dm-pcache module poses a serious risk due to improper handling of logical key offsets. Users are strongly encouraged to update their kernels to the latest patched versions to mitigate this risk. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for →

Share this vulnerability

FAQ

CVE-2026-98867 is a vulnerability in the Linux Kernel's dm-pcache module that allows for out-of-bounds memory access due to improper handling of logical key offsets.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Exploitation of this vulnerability could lead to memory corruption, arbitrary code execution, or system crashes, posing significant security risks.

You can update your Linux Kernel using your package manager. For example, on Debian-based systems, you can run 'sudo apt-get update' followed by 'sudo apt-get upgrade linux-image-$(uname -r)'.

Yes, the permanent fix is to update to the patched versions of the Linux Kernel that address this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for .

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.18.0, < 6.18.52 6.18.52
  • >= 6.19.0, < 7.2.10 7.2.10

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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