From: Matt Fleming <matt@console-pimps.org>
To: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Schroeder <mls@suse.com>, Josh Boyer <jwboyer@redhat.com>,
"Lee, Chun-Yi" <jlee@suse.com>, Peter Jones <pjones@redhat.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] efivarfs: fix abnormal GUID in variable name by using strcpy to replace null with dash
Date: Fri, 01 Mar 2013 15:17:48 +0000 [thread overview]
Message-ID: <1362151068.2842.440.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <1362108018-13117-1-git-send-email-jlee@suse.com>
On Fri, 2013-03-01 at 11:20 +0800, Lee, Chun-Yi wrote:
> From: Michael Schroeder <mls@suse.com>
>
> On HP z220 system (firmware version 1.54), some EFI variables are incorrectly
> named :
>
> ls -d /sys/firmware/efi/vars/*8be4d* | grep -v -- -8be returns
> /sys/firmware/efi/vars/dbxDefault-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/KEKDefault-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SecureBoot-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SetupMode-Information8be4df61-93ca-11d2-aa0d-00e098032b8c
>
> That causes by the following statement in efivar_create_sysfs_entry function:
>
> *(short_name + strlen(short_name)) = '-';
> efi_guid_unparse(vendor_guid, short_name + strlen(short_name));
>
> The trailing \0 is overwritten with '-', but the next char doesn't seem to be a \0
> as well for HP. So, the second strlen return the point of next '\0', causes there
> have garbage string attached before GUID.
>
> Tested on On HP z220.
What's more likely happening here is that GetNextVariable() is broken on
this HP firmware and variable_name_size is too big for the given
variable in variable_name. We've seen other reports of similar bugs,
https://bugzilla.kernel.org/show_bug.cgi?id=47631
Could someone try this patch against Linus' tree?
---
>From fe38d6f69c889b0f95c5548c724633aa58c2c99f Mon Sep 17 00:00:00 2001
From: Matt Fleming <matt.fleming@intel.com>
Date: Fri, 1 Mar 2013 14:49:12 +0000
Subject: [PATCH] efivars: Sanitise string length returned by
GetNextVariableName()
Some buggy firmware implementations return a string length from
GetNextVariableName() that is actually larger than the string in
'variable_name', as Michael Schroeder writes,
> On HP z220 system (firmware version 1.54), some EFI variables are
> incorrectly named :
>
> ls -d /sys/firmware/efi/vars/*8be4d* | grep -v -- -8be returns
> /sys/firmware/efi/vars/dbxDefault-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/KEKDefault-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SecureBoot-pport8be4df61-93ca-11d2-aa0d-00e098032b8c
> /sys/firmware/efi/vars/SetupMode-Information8be4df61-93ca-11d2-aa0d-00e098032b8c
Since 'variable_name' is a string, we can validate its size by
searching for the terminating NULL character.
Reported-by: Frederic Crozat <fcrozat@suse.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Josh Boyer <jwboyer@redhat.com>
Cc: Michael Schroeder <mls@suse.com>
Cc: Lee, Chun-Yi <jlee@suse.com>
Cc: Lingzhu Xiang <lxiang@redhat.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
---
drivers/firmware/efivars.c | 35 ++++++++++++++++++++++++++++++++++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/efivars.c b/drivers/firmware/efivars.c
index 7320bf8..b5af292 100644
--- a/drivers/firmware/efivars.c
+++ b/drivers/firmware/efivars.c
@@ -1653,6 +1653,33 @@ static bool variable_is_present(efi_char16_t *variable_name, efi_guid_t *vendor)
return found;
}
+/*
+ * Sanity check string length of a variable name.
+ */
+static unsigned long sanity_check_strlen(efi_char16_t *variable_name,
+ unsigned long variable_name_size)
+{
+ efi_char16_t c;
+ unsigned long len;
+
+ /*
+ * The variable name is, by definition, a NULL-terminated
+ * string, so make absolutely sure that variable_name_size is
+ * the value we expect it to be. If not, use whichever size is
+ * smaller.
+ */
+ for (len = 1; len <= variable_name_size; len++) {
+ c = variable_name[len - 1];
+ if (!c)
+ break;
+ }
+
+ if (len != variable_name_size)
+ printk(KERN_WARNING "efivars: bogus variable_name_size\n");
+
+ return min(len, variable_name_size);
+}
+
static void efivar_update_sysfs_entries(struct work_struct *work)
{
struct efivars *efivars = &__efivars;
@@ -1693,10 +1720,13 @@ static void efivar_update_sysfs_entries(struct work_struct *work)
if (!found) {
kfree(variable_name);
break;
- } else
+ } else {
+ variable_name_size = sanity_check_strlen(variable_name,
+ variable_name_size);
efivar_create_sysfs_entry(efivars,
variable_name_size,
variable_name, &vendor);
+ }
}
}
@@ -1941,8 +1971,11 @@ int register_efivars(struct efivars *efivars,
status = ops->get_next_variable(&variable_name_size,
variable_name,
&vendor_guid);
+
switch (status) {
case EFI_SUCCESS:
+ variable_name_size = sanity_check_strlen(variable_name,
+ variable_name_size);
efivar_create_sysfs_entry(efivars,
variable_name_size,
variable_name,
--
1.7.11.7
next prev parent reply other threads:[~2013-03-01 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 3:20 Lee, Chun-Yi
2013-03-01 9:31 ` Lingzhu Xiang
2013-03-01 14:49 ` joeyli
2013-03-01 15:17 ` Matt Fleming [this message]
2013-03-01 16:31 ` Matt Fleming
2013-03-01 23:41 ` joeyli
2013-03-06 7:34 ` joeyli
2013-03-06 7:39 ` joeyli
2013-03-06 9:20 ` Lingzhu Xiang
2013-03-06 11:21 ` Matt Fleming
2013-03-07 8:03 ` joeyli
2013-03-06 11:19 ` Matt Fleming
2013-03-06 11:58 ` Frederic Crozat
2013-03-06 12:36 ` Matt Fleming
2013-03-06 13:30 ` Frederic Crozat
2013-03-06 13:38 ` Matt Fleming
2013-03-07 10:34 ` joeyli
2013-03-07 11:39 ` Matt Fleming
2013-03-07 13:57 ` Matt Fleming
2013-03-07 14:03 ` joeyli
2013-03-11 13:17 ` joeyli
2013-03-18 15:29 ` Matt Fleming
2013-03-08 6:37 ` joeyli
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=1362151068.2842.440.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt@console-pimps.org \
--cc=jlee@suse.com \
--cc=joeyli.kernel@gmail.com \
--cc=jwboyer@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mls@suse.com \
--cc=pjones@redhat.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®