From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80957: dm-pcache: detect a cycle in the last-kset chain during replay
Date: Fri, 11 Sep 2026 21:41:03 +0200 [thread overview]
Message-ID: <2026091141-CVE-2026-80957-296f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dm-pcache: detect a cycle in the last-kset chain during replay
cache_replay() follows the on-media last-kset chain by next_cache_seg_id
with no cond_resched(). A forged chain that points back into a segment it
has already visited makes the replay loop follow it forever.
Cap the last-kset hops at cache->n_segs; a valid chain visits each segment
at most once.
The Linux kernel CVE team has assigned CVE-2026-80957 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 and fixed in 6.18.50 with commit 663ee2f3824a505b983162de44134e789f8230da
Issue introduced in 6.18 with commit 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 and fixed in 7.2.4 with commit 5311dfc5cd70edccd110257e3f30b2c1dcd3768d
Issue introduced in 6.18 with commit 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 and fixed in 7.3-rc1 with commit 16c3b3a326e70f246a605b3dc27b7f83ba4743e3
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80957
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/md/dm-pcache/cache_key.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/663ee2f3824a505b983162de44134e789f8230da
https://git.kernel.org/stable/c/5311dfc5cd70edccd110257e3f30b2c1dcd3768d
https://git.kernel.org/stable/c/16c3b3a326e70f246a605b3dc27b7f83ba4743e3
reply other threads:[~2026-09-11 19:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091141-CVE-2026-80957-296f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.