From: Andrea Parri <parri.andrea@gmail.com>
To: Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
Anton Vorontsov <anton.vorontsov@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Colin Cross <ccross@android.com>,
John Stultz <john.stultz@linaro.org>
Cc: linux-kernel@vger.kernel.org, Andrea Parri <parri.andrea@gmail.com>
Subject: [PATCH 0/2] pstore: fix two ramoops error-path bugs
Date: Mon, 21 Sep 2026 22:23:14 +0200 [thread overview]
Message-ID: <20260921202317.70595-1-parri.andrea@gmail.com> (raw)
Two bugs in the ramoops error paths, found by review and confirmed with
test-only reproducers against an unfixed kernel:
- ramoops_init_prz() stores persistent_ram_new()'s ERR_PTR in the zone
pointer and returns without clearing it; the probe error path then
passes it to persistent_ram_free(), which dereferences it and oopses.
- persistent_ram_buffer_map() computes buffer_size = size -
sizeof(struct persistent_ram_buffer) with no lower bound, so a zone no
larger than the header underflows buffer_size to a huge value and
defeats the bounds checks in the write paths.
The second patch adds a new failure return from persistent_ram_new() for
undersized zones, which is exactly the error path that exposes the first
bug: a tiny zone now leaves an ERR_PTR behind on cleanup. Applied
without the first patch, it turns the memory-corruption bug into a
probe-time panic on the same input, so the ERR_PTR fix is sent first.
Andrea Parri (2):
pstore: don't leave an ERR_PTR in the ramoops zone pointer
pstore: reject persistent RAM zones too small for the buffer header
fs/pstore/ram.c | 1 +
fs/pstore/ram_core.c | 6 ++++++
2 files changed, 7 insertions(+)
--
2.53.0
next reply other threads:[~2026-09-21 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 20:23 Andrea Parri [this message]
2026-09-21 20:23 ` [PATCH 1/2] pstore: don't leave an ERR_PTR in the ramoops zone pointer Andrea Parri
2026-09-21 20:23 ` [PATCH 2/2] pstore: reject persistent RAM zones too small for the buffer header Andrea Parri
2026-09-21 21:35 ` Kees Cook
2026-09-21 22:38 ` Andrea Parri
2026-09-21 23:11 ` Kees Cook
2026-09-21 21:38 ` [PATCH 0/2] pstore: fix two ramoops error-path bugs Kees Cook
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=20260921202317.70595-1-parri.andrea@gmail.com \
--to=parri.andrea@gmail.com \
--cc=anton.vorontsov@linaro.org \
--cc=ccross@android.com \
--cc=gpiccoli@igalia.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®