From: Stephen Moorby <steve.moorby@ntlworld.com>
To: davem@davemloft.net, sasha.levin@oracle.com,
akpm@linux-foundation.org, paulmck@linux.vnet.ibm.com,
jiri@resnulli.us, linux-x25@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stephen Moorby <steve.moorby@ntlworld.com>
Subject: [PATCH 1/1] net/x25: fix address parsing bug in x25_parse_address_block.
Date: Wed, 19 Jun 2013 21:32:36 +0100 [thread overview]
Message-ID: <1371673956-471-1-git-send-email-steve.moorby@ntlworld.com> (raw)
This problem was discovered when a linux box was incorrectly rejecting
calls from some X.25 equipment. The problem was diagnosed to an incorrect
address length calculation in 'x25_parse_address_block', the calculation
did not account for the address digits being BCD encoded. The correct
calculation is already performed on line 155.
Patched on linux-next 18-Jun-2013
Tested on 2.6.32-45-generic
Signed-off-by: Stephen Moorby <steve.moorby@ntlworld.com>
---
net/x25/af_x25.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/x25/af_x25.c b/net/x25/af_x25.c
index 1d964e2..eb6c1f9 100644
--- a/net/x25/af_x25.c
+++ b/net/x25/af_x25.c
@@ -98,7 +98,8 @@ int x25_parse_address_block(struct sk_buff *skb,
}
len = *skb->data;
- needed = 1 + (len >> 4) + (len & 0x0f);
+ /* need 1 for address length + bytes for BCD encoding of 2 addresses */
+ needed = 1 + (((len >> 4) + (len & 0x0f) + 1) >> 1);
if (!pskb_may_pull(skb, needed)) {
/* packet is too short to hold the addresses it claims
--
1.8.1.2
next reply other threads:[~2013-06-19 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 20:32 Stephen Moorby [this message]
2013-06-20 0:59 ` [PATCH 1/1] net/x25: fix address parsing bug in x25_parse_address_block David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-06-19 11:13 Stephen Moorby
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=1371673956-471-1-git-send-email-steve.moorby@ntlworld.com \
--to=steve.moorby@ntlworld.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).