From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68176: tracing: Fix mmiotrace possible NULL dereferencing of hiter->dev
Date: Mon, 10 Aug 2026 13:58:13 +0200 [thread overview]
Message-ID: <2026081006-CVE-2026-68176-670c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix mmiotrace possible NULL dereferencing of hiter->dev
If the mmio_pipe_open() fails to find a PCI device, the hiter->dev
will be assigned to NULL. The mmiotrace read() function dereferences the
hiter->dev if hiter exists.
Change the test of the read to not only check hiter being NULL, but also
the hiter->dev before dereferencing it.
The Linux kernel CVE team has assigned CVE-2026-68176 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.27 with commit f984b51e0779a6dd30feedc41404013ca54e5d05 and fixed in 6.6.148 with commit faaf95135184208ee3ac6f33175c8d1800669dfc
Issue introduced in 2.6.27 with commit f984b51e0779a6dd30feedc41404013ca54e5d05 and fixed in 6.12.101 with commit 201a01102c529772168181190cb084471082cf5c
Issue introduced in 2.6.27 with commit f984b51e0779a6dd30feedc41404013ca54e5d05 and fixed in 6.18.42 with commit 8464427e1c177809a9488a97dfa2807d9dcf323b
Issue introduced in 2.6.27 with commit f984b51e0779a6dd30feedc41404013ca54e5d05 and fixed in 7.1.6 with commit 724cd84b0546c07806840fa658714488553d13a2
Issue introduced in 2.6.27 with commit f984b51e0779a6dd30feedc41404013ca54e5d05 and fixed in 7.2-rc5 with commit 144f29e85702234b23d2a62abf723e6a17eb5427
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-68176
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:
kernel/trace/trace_mmiotrace.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/faaf95135184208ee3ac6f33175c8d1800669dfc
https://git.kernel.org/stable/c/201a01102c529772168181190cb084471082cf5c
https://git.kernel.org/stable/c/8464427e1c177809a9488a97dfa2807d9dcf323b
https://git.kernel.org/stable/c/724cd84b0546c07806840fa658714488553d13a2
https://git.kernel.org/stable/c/144f29e85702234b23d2a62abf723e6a17eb5427
reply other threads:[~2026-08-10 12:04 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=2026081006-CVE-2026-68176-670c@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.