From: Jarkko Sakkinen <jarkko@kernel.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Peter Huewe <peterhuewe@gmx.de>,
falemi@asu.edu, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] tpm_tis_plat_probe -- maps a borrowed MEM resource by its own size, then reads at a FIXED 0xF00 offset
Date: Tue, 1 Sep 2026 13:30:01 +0300 [thread overview]
Message-ID: <apapKZSytIX19glD@kernel.org> (raw)
In-Reply-To: <CA+0ovCjBrrU0H0Z-fqBZ_mat4toQM_z2=+NC-9ONSXn=bD8mmg@mail.gmail.com>
On Thu, Aug 27, 2026 at 10:37:00PM -0700, Farhad Alemi wrote:
> Hello,
>
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/154-tpm_tis-borrowed-resource-fixed-offset-read/
Please describe instead in plain Enligsh what is going. Hopping into
random Github links is not the best possible way to communicate.
>
> BUG: unable to handle page fault for address: ffffc90000a17310
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> Oops: Oops: 0000 [#1] SMP KASAN NOPTI
> RIP: 0010:ioread32+0x1c/0x80
> Call Trace:
> ioread32+0x1c/0x80
> tpm_tcg_read_bytes+0xec/0x270
> tpm_tis_core_init+0x48c/0x1830
> tpm_tis_init+0x420/0x540
> tpm_tis_plat_probe+0x118/0x1a0
> platform_probe+0xf9/0x190
> really_probe+0x267/0xaf0
> device_driver_attach+0xe0/0x1d0
> bind_store+0x1d0/0x220
> kernfs_fop_write_iter+0x3af/0x540
> ksys_write+0x150/0x270
> Kernel panic - not syncing: Fatal exception
>
> Our reproducer.c is available upon request.
>
> Happy to test a patch if that would help.
>
> Regards,
BR, Jarkko
prev parent reply other threads:[~2026-09-01 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:37 [BUG] tpm_tis_plat_probe -- maps a borrowed MEM resource by its own size, then reads at a FIXED 0xF00 offset Farhad Alemi
2026-09-01 10:30 ` Jarkko Sakkinen [this message]
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=apapKZSytIX19glD@kernel.org \
--to=jarkko@kernel.org \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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.