From: Andrew Morton <akpm@linux-foundation.org>
To: Jiale Yao <yaojiale02@163.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Keith Busch <kbusch@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCH v2] lib/firmware_table: validate subtable bounds
Date: Thu, 29 Oct 2026 21:48:55 -0700 [thread overview]
Message-ID: <20261029214855.2e701d85caea73b491a6154d@linux-foundation.org> (raw)
In-Reply-To: <20261021150159.399043-1-yaojiale02@163.com>
On Wed, 21 Oct 2026 23:01:59 +0800 Jiale Yao <yaojiale02@163.com> wrote:
> The generic firmware table walker dispatches matching entries after only
> checking that a generic subtable header is present. A record whose
> declared length is shorter than its header or extends past the table can
> therefore reach a handler before its bounds have been established.
Then what happens? Kernel go oops?
When fixing a bug please always describe the userspace-visible runtime
effects of that bug.
How can this situation come about? A messed up firmware table?
> Once a complete generic header is available, validate the declared record
> range before looking up or invoking a handler. This rejects zero-length
> and truncated records while preserving the existing behavior of ignoring
> trailing table data too short to contain another subtable header.
>
> ...
>
> --- a/lib/fw_table.c
> +++ b/lib/fw_table.c
> @@ -172,7 +172,15 @@ acpi_parse_entries_array(char *id, unsigned long table_size,
> ((unsigned long)table_header + table_size);
> subtable_len = acpi_get_subtable_header_length(&entry);
>
> - while (((unsigned long)entry.hdr) + subtable_len < table_end) {
> + while ((unsigned long)entry.hdr + subtable_len <= table_end) {
> + entry_len = acpi_get_entry_length(&entry);
> + if (entry_len < subtable_len ||
> + entry_len > table_end - (unsigned long)entry.hdr) {
> + pr_err("[%4.4s:0x%02lx] Invalid length %lu\n", id,
> + acpi_get_entry_type(&entry), entry_len);
> + return -EINVAL;
> + }
> +
> for (i = 0; i < proc_num; i++) {
> if (acpi_get_entry_type(&entry) != proc[i].id)
> continue;
> @@ -186,16 +194,6 @@ acpi_parse_entries_array(char *id, unsigned long table_size,
> break;
> }
>
> - /*
> - * If entry->length is 0, break from this loop to avoid
> - * infinite loop.
> - */
> - entry_len = acpi_get_entry_length(&entry);
> - if (entry_len == 0) {
> - pr_err("[%4.4s:0x%02x] Invalid zero length\n", id, proc->id);
> - return -EINVAL;
> - }
> -
> entry.hdr = (union acpi_subtable_headers *)
> ((unsigned long)entry.hdr + entry_len);
> }
> --
> 2.34.1
prev parent reply other threads:[~2026-10-30 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:01 Jiale Yao
2026-10-30 4:48 ` Andrew Morton [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=20261029214855.2e701d85caea73b491a6154d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbusch@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yaojiale02@163.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®