From: Tristan Madani <tristmd@gmail.com>
To: Ajay Singh <ajay.kathat@microchip.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: [PATCH v2 0/2] wifi: wilc1000: fix integer underflow and OOB read from firmware packets
Date: Wed, 15 Apr 2026 22:24:15 +0000 [thread overview]
Message-ID: <20260415222418.1543832-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
Hi Ajay, Claudiu,
Note: this is a v2 resubmission. The original was sent via Gmail which
caused HTML rendering issues. This version uses git send-email for
proper plain-text formatting.
Two issues in wilc1000 where firmware-controlled packet fields are used
without validation:
Proposed fixes in the following patches.
Thanks,
Tristan
next reply other threads:[~2026-04-15 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 22:24 Tristan Madani [this message]
2026-04-15 22:24 ` [PATCH v2 1/2] wifi: wilc1000: fix integer underflow in wilc_network_info_received() Tristan Madani
2026-04-15 22:24 ` [PATCH v2 2/2] wifi: wilc1000: fix OOB read from firmware RX packet header fields Tristan Madani
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=20260415222418.1543832-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=ajay.kathat@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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