From: Peter Maydell <1904954@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1904954] Re: lan9118 bug peeked received message size not equal to actual received message size
Date: Fri, 15 Jan 2021 16:13:57 -0000 [thread overview]
Message-ID: <161072723726.6313.9377507324411037925.malone@wampee.canonical.com> (raw)
In-Reply-To: 160584191813.16356.9445911921619079194.malonedeb@chaenomeles.canonical.com
Fix now in master: commit e7e29fdbbe07f.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1904954
Title:
lan9118 bug peeked received message size not equal to actual received
message size
Status in QEMU:
Fix Committed
Bug description:
peeked message size is not equal to read message size
Bug in the code at line:
https://github.com/qemu/qemu/blob/master/hw/net/lan9118.c#L1209
s->tx_status_fifo_head should be s->rx_status_fifo_head
Could also be a security bug, as the user could allocate a buffer of
size peeked data smaller than the actual packet received, which could
cause a buffer overflow.
Thanks,
Alfred
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1904954/+subscriptions
next prev parent reply other threads:[~2021-01-15 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 3:11 [Bug 1904954] [NEW] lan9118 bug peeking receive massage size not equal to received message size alfred gedeon
2020-11-20 4:08 ` [Bug 1904954] " alfred gedeon
2020-12-23 6:15 ` [Bug 1904954] Re: lan9118 bug peeked received message size not equal to actual " alfred gedeon
2021-01-08 17:27 ` Peter Maydell
2021-01-08 17:30 ` Peter Maydell
2021-01-08 18:08 ` Peter Maydell
2021-01-08 19:06 ` Peter Maydell
2021-01-08 23:54 ` alfred gedeon
2021-01-15 16:13 ` Peter Maydell [this message]
2021-04-29 10:45 ` Thomas Huth
2021-04-30 7:18 ` Thomas Huth
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=161072723726.6313.9377507324411037925.malone@wampee.canonical.com \
--to=1904954@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).