data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-98867 in the interactive tracker

CVE-2026-98867

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

Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/md. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-98867 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixienot affected6.12.113-1Nothing to do. trixie never shipped the vulnerable code.
Debian 14forkyfixed7.2.10-1Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.10-1Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/md/dm-pcache/cache_key.c

What this is
DEVICE-MAPPER PCACHE TARGETMAINTAINERS section matched on drivers/md/dm-pcache/ · dm-devel@lists.linux.dev · Maintained

Check it on the machine

grep -wE 'CONFIG_DM_PCACHE|CONFIG_MD' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code in 2 releases. The build rule could not be established for 2 releases, so nothing is claimed about those.

  • bookworm, trixie?
  • forky, sidn
?
not established - no Makefile entry for the affected file
n
not enabled on any flavour - this release does not build the code

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switches
CONFIG_DM_PCACHE, CONFIG_MD
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-10-18 (today)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
not scored
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
drivers/md

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.186.18.523d5a87cb909c
6.187.2.10104497032000
6.187.397fc4b53dbe4

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98867, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.