qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH v2 for v2.3.0] fw_cfg: add check to validate current entry value
@ 2016-01-06  6:16 P J P
  2016-01-11  7:23 ` P J P
  0 siblings, 1 reply; 4+ messages in thread
From: P J P @ 2016-01-06  6:16 UTC (permalink / raw)
  To: Stefan Weil; +Cc: Peter Maydell, Prasad J Pandit, Qemu devel, Donghai Zdh

From: Prasad J Pandit <pjp@fedoraproject.org>

When processing firmware configurations, an OOB r/w access occurs
if 's->cur_entry' is set to be invalid(FW_CFG_INVALID=0xffff).
Add a check to validate 's->cur_entry' to avoid such access.

Reported-by: Donghai Zdh <donghai.zdh@alibaba-inc.com>
Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
---
 hw/nvram/fw_cfg.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

Updated as per review in
  -> https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg00398.html

diff --git a/hw/nvram/fw_cfg.c b/hw/nvram/fw_cfg.c
index 68eff77..e73c0fb 100644
--- a/hw/nvram/fw_cfg.c
+++ b/hw/nvram/fw_cfg.c
@@ -233,12 +233,15 @@ static void fw_cfg_reboot(FWCfgState *s)
 static void fw_cfg_write(FWCfgState *s, uint8_t value)
 {
     int arch = !!(s->cur_entry & FW_CFG_ARCH_LOCAL);
-    FWCfgEntry *e = &s->entries[arch][s->cur_entry & FW_CFG_ENTRY_MASK];
+    FWCfgEntry *e = (s->cur_entry == FW_CFG_INVALID) ? NULL :
+                     &s->entries[arch][s->cur_entry & FW_CFG_ENTRY_MASK];
 
     trace_fw_cfg_write(s, value);
 
-    if (s->cur_entry & FW_CFG_WRITE_CHANNEL && e->callback &&
-        s->cur_offset < e->len) {
+    if (s->cur_entry & FW_CFG_WRITE_CHANNEL
+        && e != NULL
+        && e->callback
+        && s->cur_offset < e->len) {
         e->data[s->cur_offset++] = value;
         if (s->cur_offset == e->len) {
             e->callback(e->callback_opaque, e->data);
@@ -267,7 +270,8 @@ static int fw_cfg_select(FWCfgState *s, uint16_t key)
 static uint8_t fw_cfg_read(FWCfgState *s)
 {
     int arch = !!(s->cur_entry & FW_CFG_ARCH_LOCAL);
-    FWCfgEntry *e = &s->entries[arch][s->cur_entry & FW_CFG_ENTRY_MASK];
+    FWCfgEntry *e = (s->cur_entry == FW_CFG_INVALID) ? NULL :
+                     &s->entries[arch][s->cur_entry & FW_CFG_ENTRY_MASK];
     uint8_t ret;
 
     if (s->cur_entry == FW_CFG_INVALID || !e->data || s->cur_offset >= e->len)
-- 
2.4.3

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [Qemu-devel] [PATCH v2 for v2.3.0] fw_cfg: add check to validate current entry value
  2016-01-06  6:16 [Qemu-devel] [PATCH v2 for v2.3.0] fw_cfg: add check to validate current entry value P J P
@ 2016-01-11  7:23 ` P J P
  2016-01-11 12:28   ` Paolo Bonzini
  0 siblings, 1 reply; 4+ messages in thread
From: P J P @ 2016-01-11  7:23 UTC (permalink / raw)
  To: Stefan Weil; +Cc: Peter Maydell, Qemu devel, Donghai Zdh

  Hello,

+-- On Wed, 6 Jan 2016, P J P wrote --+
| When processing firmware configurations, an OOB r/w access occurs
| if 's->cur_entry' is set to be invalid(FW_CFG_INVALID=0xffff).
| Add a check to validate 's->cur_entry' to avoid such access.
| 
| Reported-by: Donghai Zdh <donghai.zdh@alibaba-inc.com>
| Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
| ---
|  hw/nvram/fw_cfg.c | 12 ++++++++----
|  1 file changed, 8 insertions(+), 4 deletions(-)
| 
| Updated as per review in
|   -> https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg00398.html


  -> https://patchwork.ozlabs.org/patch/563706/

Ping...! Does it look okay? (just checking)

Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Qemu-devel] [PATCH v2 for v2.3.0] fw_cfg: add check to validate current entry value
  2016-01-11  7:23 ` P J P
@ 2016-01-11 12:28   ` Paolo Bonzini
  2016-01-11 16:34     ` P J P
  0 siblings, 1 reply; 4+ messages in thread
From: Paolo Bonzini @ 2016-01-11 12:28 UTC (permalink / raw)
  To: P J P, Stefan Weil; +Cc: Peter Maydell, Qemu devel, Donghai Zdh



On 11/01/2016 08:23, P J P wrote:
>   Hello,
> 
> +-- On Wed, 6 Jan 2016, P J P wrote --+
> | When processing firmware configurations, an OOB r/w access occurs
> | if 's->cur_entry' is set to be invalid(FW_CFG_INVALID=0xffff).
> | Add a check to validate 's->cur_entry' to avoid such access.
> | 
> | Reported-by: Donghai Zdh <donghai.zdh@alibaba-inc.com>
> | Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> | ---
> |  hw/nvram/fw_cfg.c | 12 ++++++++----
> |  1 file changed, 8 insertions(+), 4 deletions(-)
> | 
> | Updated as per review in
> |   -> https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg00398.html
> 
> 
>   -> https://patchwork.ozlabs.org/patch/563706/
> 
> Ping...! Does it look okay? (just checking)

Yes, it looks good.

Paolo

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Qemu-devel] [PATCH v2 for v2.3.0] fw_cfg: add check to validate current entry value
  2016-01-11 12:28   ` Paolo Bonzini
@ 2016-01-11 16:34     ` P J P
  0 siblings, 0 replies; 4+ messages in thread
From: P J P @ 2016-01-11 16:34 UTC (permalink / raw)
  To: Paolo Bonzini; +Cc: Stefan Weil, Donghai Zdh, Qemu devel, Peter Maydell

+-- On Mon, 11 Jan 2016, Paolo Bonzini wrote --+
| > +-- On Wed, 6 Jan 2016, P J P wrote --+
| >   -> https://patchwork.ozlabs.org/patch/563706/
| > Ping...! Does it look okay? (just checking)
| 
| Yes, it looks good.

Okay, thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-01-11 16:35 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-06  6:16 [Qemu-devel] [PATCH v2 for v2.3.0] fw_cfg: add check to validate current entry value P J P
2016-01-11  7:23 ` P J P
2016-01-11 12:28   ` Paolo Bonzini
2016-01-11 16:34     ` P J P

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).