All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@domain.hid>,
	xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH][STABLE] posix: Fix access checks in select
Date: Fri, 08 May 2009 01:24:42 +0200	[thread overview]
Message-ID: <4A036DBA.8080107@domain.hid> (raw)
In-Reply-To: <4A036C0F.6090202@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 4433 bytes --]

Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> [ Please pull from git://git.xenomai.org/xenomai-jki.git for-2.4.x ]
>>>
>>> The test for __xn_access_ok was inverted, thus rejected valid requests.
>>> Fix this and refactor the code in order to check for the actual size of
>>> the passed fd sets.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
>>> ---
>>>
>>>  ksrc/skins/posix/syscall.c |   21 +++++++++------------
>>>  1 files changed, 9 insertions(+), 12 deletions(-)
>>>
>>> diff --git a/ksrc/skins/posix/syscall.c b/ksrc/skins/posix/syscall.c
>>> index 5c62a45..f0111f8 100644
>>> --- a/ksrc/skins/posix/syscall.c
>>> +++ b/ksrc/skins/posix/syscall.c
>>> @@ -2384,17 +2384,16 @@ static int __select(struct task_struct *curr, struct pt_regs *regs)
>>>  	struct timeval tv;
>>>  	pthread_t thread;
>>>  	int i, err, nfds;
>>> +	size_t fds_size;
>>>  
>>>  	thread = pse51_current_thread();
>>>  	if (!thread)
>>>  		return -EPERM;
>>>  
>>>  	if (__xn_reg_arg5(regs)) {
>>> -		if (__xn_access_ok(curr, VERIFY_WRITE,
>>> -				   __xn_reg_arg5(regs), sizeof(tv)))
>>> -			return -EFAULT;
>>> -
>>> -		if (__xn_copy_from_user(curr, &tv,
>>> +		if (!__xn_access_ok(curr, VERIFY_WRITE,
>>> +				    __xn_reg_arg5(regs), sizeof(tv)) ||
>>> +		    __xn_copy_from_user(curr, &tv,
>>>  					(void __user *)__xn_reg_arg5(regs),
>>>  					sizeof(tv)))
>>>  			return -EFAULT;
>> Ok.
>>
>>> @@ -2407,19 +2406,17 @@ static int __select(struct task_struct *curr, struct pt_regs *regs)
>>>  	}
>>>  
>>>  	nfds = __xn_reg_arg1(regs);
>>> +	fds_size = __FDELT(nfds + __NFDBITS - 1) * sizeof(long);
>>>  
>>>  	for (i = 0; i < XNSELECT_MAX_TYPES; i++)
>>>  		if (ufd_sets[i]) {
>>>  			in_fds[i] = &in_fds_storage[i];
>>>  			out_fds[i] = & out_fds_storage[i];
>>> -			if (__xn_access_ok(curr, VERIFY_WRITE,
>>> -					   ufd_sets[i], sizeof(fd_set)))
>>> -				return -EFAULT;
>>> -
>>> -			if (__xn_copy_from_user(curr, in_fds[i],
>>> +			if (!__xn_access_ok(curr, VERIFY_WRITE,
>>> +					    ufd_sets[i], fds_size) ||
>> I do not think this is a good idea. There is no special mention to it in
>> select specification, but at least select prototype suggests that the
>> user-space structure should be a valid fd_set, not a partial subset of it.
> 
> Yeah, and we copy a full set back. Missed that, will update both patches.

This (and the corresponding head patch) is now available via git:

---------->

The test for __xn_access_ok was inverted, thus rejected valid requests.
Fix this and refactor the code in order to check for the actual size of
the passed fd sets.

Signed-off-by: Jan Kiszka <jan.kiszka@domain.hid>
---

 ksrc/skins/posix/syscall.c |   21 +++++++++------------
 1 files changed, 9 insertions(+), 12 deletions(-)

diff --git a/ksrc/skins/posix/syscall.c b/ksrc/skins/posix/syscall.c
index 5c62a45..3791071 100644
--- a/ksrc/skins/posix/syscall.c
+++ b/ksrc/skins/posix/syscall.c
@@ -2384,17 +2384,16 @@ static int __select(struct task_struct *curr, struct pt_regs *regs)
 	struct timeval tv;
 	pthread_t thread;
 	int i, err, nfds;
+	size_t fds_size;
 
 	thread = pse51_current_thread();
 	if (!thread)
 		return -EPERM;
 
 	if (__xn_reg_arg5(regs)) {
-		if (__xn_access_ok(curr, VERIFY_WRITE,
-				   __xn_reg_arg5(regs), sizeof(tv)))
-			return -EFAULT;
-
-		if (__xn_copy_from_user(curr, &tv,
+		if (!__xn_access_ok(curr, VERIFY_WRITE,
+				    __xn_reg_arg5(regs), sizeof(tv)) ||
+		    __xn_copy_from_user(curr, &tv,
 					(void __user *)__xn_reg_arg5(regs),
 					sizeof(tv)))
 			return -EFAULT;
@@ -2407,19 +2406,17 @@ static int __select(struct task_struct *curr, struct pt_regs *regs)
 	}
 
 	nfds = __xn_reg_arg1(regs);
+	fds_size = __FDELT(nfds + __NFDBITS - 1) * sizeof(long);
 
 	for (i = 0; i < XNSELECT_MAX_TYPES; i++)
 		if (ufd_sets[i]) {
 			in_fds[i] = &in_fds_storage[i];
 			out_fds[i] = & out_fds_storage[i];
-			if (__xn_access_ok(curr, VERIFY_WRITE,
-					   ufd_sets[i], sizeof(fd_set)))
-				return -EFAULT;
-
-			if (__xn_copy_from_user(curr, in_fds[i],
+			if (!__xn_access_ok(curr, VERIFY_WRITE,
+					    ufd_sets[i], sizeof(fd_set)) ||
+			    __xn_copy_from_user(curr, in_fds[i],
 						(void __user *) ufd_sets[i],
-						__FDELT(nfds + __NFDBITS - 1)
-						* sizeof(long)))
+						fds_size))
 				return -EFAULT;
 		}
 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-05-07 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 19:25 [Xenomai-core] [PATCH][STABLE] posix: Fix access checks in select Jan Kiszka
2009-05-07 22:50 ` Gilles Chanteperdrix
2009-05-07 23:17   ` Jan Kiszka
2009-05-07 23:24     ` Jan Kiszka [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=4A036DBA.8080107@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=vladimir.zapolskiy@domain.hid \
    --cc=xenomai@xenomai.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.