From: patchwork-bot+netdevbpf@kernel.org
To: Marcin Kozlowski <marcinguy@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: usb: aqc111: Fix out-of-bounds accesses in RX fixup
Date: Wed, 06 Apr 2022 14:30:12 +0000 [thread overview]
Message-ID: <164925541238.21938.8958052455955539634.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220406080537.22026-1-marcinguy@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 6 Apr 2022 10:05:37 +0200 you wrote:
> aqc111_rx_fixup() contains several out-of-bounds accesses that can be
> triggered by a malicious (or defective) USB device, in particular:
>
> - The metadata array (desc_offset..desc_offset+2*pkt_count) can be out of bounds,
> causing OOB reads and (on big-endian systems) OOB endianness flips.
> - A packet can overlap the metadata array, causing a later OOB
> endianness flip to corrupt data used by a cloned SKB that has already
> been handed off into the network stack.
> - A packet SKB can be constructed whose tail is far beyond its end,
> causing out-of-bounds heap data to be considered part of the SKB's
> data.
>
> [...]
Here is the summary with links:
- net: usb: aqc111: Fix out-of-bounds accesses in RX fixup
https://git.kernel.org/netdev/net/c/afb8e2465275
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-06 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 8:05 [PATCH] net: usb: aqc111: Fix out-of-bounds accesses in RX fixup Marcin Kozlowski
2022-04-06 14:30 ` patchwork-bot+netdevbpf [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=164925541238.21938.8958052455955539634.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=marcinguy@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).