From: Sergey Vlasov <vsu@altlinux.ru>
To: Konstantin Sharlaimov <konstantin.sharlaimov@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.21.3] ppp_mppe: account for osize too small errors in mppe_decompress()
Date: Tue, 19 Jun 2007 18:41:48 +0400 [thread overview]
Message-ID: <20070619184148.201f2521.vsu@altlinux.ru> (raw)
In-Reply-To: <46654796.3060800@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
On Tue, 05 Jun 2007 22:23:02 +1100 Konstantin Sharlaimov wrote:
> Prevent mppe_decompress() from generating "osize too small" errors when checking
> for output buffer size. When receiving a packet of mru size the output buffer
> for decrypted data is 1 byte too small since mppe_decompress() tries to account
> for possible PFC, however later in code it is assumed no PFC.
>
> Adjusting the check prevented there errors from occurring.
>
> Signed-off-by: Konstantin Sharlaimov <konstantin.sharlaimov@gmail.com>
> ---
> --- linux-2.6.21.3/drivers/net/ppp_mppe.c.orig 2007-06-01 20:57:04.000000000 +1100
> +++ linux-2.6.21.3/drivers/net/ppp_mppe.c 2007-06-05 21:46:30.000000000 +1100
> @@ -493,14 +493,14 @@ mppe_decompress(void *arg, unsigned char
>
> /*
> * Make sure we have enough room to decrypt the packet.
> - * Note that for our test we only subtract 1 byte whereas in
> - * mppe_compress() we added 2 bytes (+MPPE_OVHD);
> - * this is to account for possible PFC.
> + * To account for possible PFC we should only subtract 1
> + * byte whereas in mppe_compress() we added 2 bytes (+MPPE_OVHD);
> + * However, we assume no PFC, thus subtracting 2 bytes.
> */
> - if (osize < isize - MPPE_OVHD - 1) {
> + if (osize < isize - MPPE_OVHD - 2) {
> printk(KERN_DEBUG "mppe_decompress[%d]: osize too small! "
> "(have: %d need: %d)\n", state->unit,
> - osize, isize - MPPE_OVHD - 1);
> + osize, isize - MPPE_OVHD - 2);
> return DECOMP_ERROR;
> }
> osize = isize - MPPE_OVHD - 2; /* assume no PFC */
Seems that this patch is not correct - even though the comment above
says "assume no PFC", the subsequent code actually supports PFC:
/*
* Do PFC decompression.
* This would be nicer if we were given the actual sk_buff
* instead of a char *.
*/
if ((obuf[0] & 0x01) != 0) {
obuf[1] = obuf[0];
obuf[0] = 0;
obuf++;
osize++;
}
Therefore, depending on the packet contents, the decompressor may
really need that extra byte in the output buffer, and changing the
check may cause buffer overflows.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-19 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 11:23 [PATCH 2.6.21.3] ppp_mppe: account for osize too small errors in mppe_decompress() Konstantin Sharlaimov
2007-06-19 14:41 ` Sergey Vlasov [this message]
2007-06-19 21:33 ` Konstantin
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=20070619184148.201f2521.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=konstantin.sharlaimov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.