public inbox for opensbi@lists.infradead.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Deepak Gupta" <debug@rivosinc.com>, <opensbi@lists.infradead.org>
Cc: "opensbi" <opensbi-bounces@lists.infradead.org>
Subject: Re: [PATCH] lib: sbi: expected trap must always clear MPRV
Date: Tue, 25 Nov 2025 12:12:11 +0100	[thread overview]
Message-ID: <DEHQBF6B4C9L.125VJJV9WIVFK@ventanamicro.com> (raw)
In-Reply-To: <20251124220339.3695940-1-debug@rivosinc.com>

2025-11-24T14:03:39-08:00, Deepak Gupta <debug@rivosinc.com>:
> Expected trap must always clear MPRV. Currently it doesn't. There is a
> security issue here where if firmware was doing ld/st with MPRV=1 and
> since there would be a expected trap, opensbi will continue to run as
> MPRV=1. Security impact is DoS where opensbi will just keep trapping.

Does the DoS happen on some implementation?

The expected trap came from M-mode, therefore will have mstatus.MPP=3,
so MPRV=1 should behave the same as MPRV=0.

Thanks.

-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

  reply	other threads:[~2025-11-25 11:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 22:03 [PATCH] lib: sbi: expected trap must always clear MPRV Deepak Gupta
2025-11-25 11:12 ` Radim Krčmář [this message]
2025-11-25 18:03   ` Deepak Gupta
2025-11-25 18:51     ` Radim Krčmář
2025-11-25 19:17       ` Deepak Gupta
2025-11-25 19:48         ` Radim Krčmář
2025-11-25 20:04           ` Deepak Gupta
2025-11-26  8:21             ` Radim Krčmář
2025-12-26 11:06 ` Anup Patel

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=DEHQBF6B4C9L.125VJJV9WIVFK@ventanamicro.com \
    --to=rkrcmar@ventanamicro.com \
    --cc=debug@rivosinc.com \
    --cc=opensbi-bounces@lists.infradead.org \
    --cc=opensbi@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox