Menu

Star on GitHub · 3.4k

CVE-2026-98867

In the Linux kernel, the following vulnerability has been resolved: dm-pcache: bound the logical key offset from persistent memory cache_key_decode() takes a key's logical off from the cache devi…

Published Oct 18, 2026EPSS 0.15%

Overview

CVE-2026-98867 is a known-severity vulnerability. It was published on October 18, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

dm-pcache: bound the logical key offset from persistent memory

cache_key_decode() takes a key's logical off from the cache device and

later indexes req_key_tree->subtrees[] by it in get_subtree(). An off

past the device forms a subtree pointer outside the array, which

rb_insert() writes through during replay.

Reject a key of zero length, or whose off+len (computed in 64 bits)

exceeds the device size, before it is used.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-98867?

CVE-2026-98867 is a known-severity vulnerability. It was published on October 18, 2026.

How severe is CVE-2026-98867?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-98867?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-98867?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98867 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

LiveWatch live →