From: Luciano Coelho <coelho@ti.com>
To: Pontus Fuchs <pontus.fuchs@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/2] wl12xx: Fix problems in nvs file parsing
Date: Thu, 01 Dec 2011 16:23:43 +0200 [thread overview]
Message-ID: <1322749423.8996.29.camel@cumari> (raw)
In-Reply-To: <1318922622-8356-1-git-send-email-pontus.fuchs@gmail.com>
On Tue, 2011-10-18 at 09:23 +0200, Pontus Fuchs wrote:
> A crafted nvs file could trick the driver into reading and writing
> beyond end of buffers.
>
> Pontus Fuchs (2):
> wl12xx: Validate FEM index from ini file and FW
> wl12xx: Check buffer bound when processing nvs data
>
> drivers/net/wireless/wl12xx/boot.c | 14 ++++++++++++++
> drivers/net/wireless/wl12xx/cmd.c | 22 ++++++++++++++++++++++
> 2 files changed, 36 insertions(+), 0 deletions(-)
Applied both, tack!
--
Cheers,
Luca.
prev parent reply other threads:[~2011-12-01 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 7:23 [PATCH 0/2] wl12xx: Fix problems in nvs file parsing Pontus Fuchs
2011-10-18 7:23 ` [PATCH 1/2] wl12xx: Validate FEM index from ini file and FW Pontus Fuchs
2011-10-18 7:23 ` [PATCH 2/2] wl12xx: Check buffer bound when processing nvs data Pontus Fuchs
2011-12-01 14:23 ` Luciano Coelho [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=1322749423.8996.29.camel@cumari \
--to=coelho@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pontus.fuchs@gmail.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