All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72097: dm-verity: fix a possible NULL pointer dereference
Date: Sat, 15 Aug 2026 15:02:56 +0900	[thread overview]
Message-ID: <2026081524-CVE-2026-72097-5688@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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

dm-verity: fix a possible NULL pointer dereference

Fix a possible NULL pointer dereference dm_verity_loadpin_is_bdev_trusted
if the device has no table.

The Linux kernel CVE team has assigned CVE-2026-72097 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.0 with commit b6c1c5745ccc68ac5d57c7ffb51ea25a86d0e97b and fixed in 6.1.178 with commit 7d4f1d307ac0f4f55cebeb192a90a235aa060ed1
	Issue introduced in 6.0 with commit b6c1c5745ccc68ac5d57c7ffb51ea25a86d0e97b and fixed in 6.6.145 with commit 1f04b390add2e14c5b36829a0a1529c4eb65a2e1
	Issue introduced in 6.0 with commit b6c1c5745ccc68ac5d57c7ffb51ea25a86d0e97b and fixed in 6.12.97 with commit 32f8231c81bd45ab92d49b646a154551f7d54f4f
	Issue introduced in 6.0 with commit b6c1c5745ccc68ac5d57c7ffb51ea25a86d0e97b and fixed in 6.18.40 with commit f15eaa3801f2f9207dff156f1ab3e7436ce52bb1
	Issue introduced in 6.0 with commit b6c1c5745ccc68ac5d57c7ffb51ea25a86d0e97b and fixed in 7.1.5 with commit 81f41d989a32458ff3512f6b05458eaf8926579c
	Issue introduced in 6.0 with commit b6c1c5745ccc68ac5d57c7ffb51ea25a86d0e97b and fixed in 7.2-rc3 with commit e72b793ae440f6900fb17a4b8518c707b5cd3e17

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-72097
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-verity-loadpin.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/7d4f1d307ac0f4f55cebeb192a90a235aa060ed1
	https://git.kernel.org/stable/c/1f04b390add2e14c5b36829a0a1529c4eb65a2e1
	https://git.kernel.org/stable/c/32f8231c81bd45ab92d49b646a154551f7d54f4f
	https://git.kernel.org/stable/c/f15eaa3801f2f9207dff156f1ab3e7436ce52bb1
	https://git.kernel.org/stable/c/81f41d989a32458ff3512f6b05458eaf8926579c
	https://git.kernel.org/stable/c/e72b793ae440f6900fb17a4b8518c707b5cd3e17

                 reply	other threads:[~2026-08-15  6:11 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=2026081524-CVE-2026-72097-5688@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.