From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
vojtech@ucw.cz, VANDROVE@vc.cvut.cz
Subject: Re: Not so theoretical race in atkbd_command
Date: Tue, 27 Apr 2004 00:49:11 +0200 [thread overview]
Message-ID: <20040426224911.GA276@elf.ucw.cz> (raw)
In-Reply-To: <20040426213555.GA1368@elf.ucw.cz>
Hi!
> There's quite real race in atkbd_command:
>
> static int atkbd_command(struct atkbd *atkbd, unsigned char *param,
> int command)
> {
> int timeout = 500000; /* 500 msec */
> int send = (command >> 12) & 0xf;
> int receive = (command >> 8) & 0xf;
> int i;
>
> atkbd->cmdcnt = receive;
> [user presses key here]
>
> atkbd_interrupt eats user keypress, thinking its reply. Boom. To
> exploit:
>
> while true; do setleds +num; setleds -num; done
>
> then try typing.
Petr suggested following follow-up patch. I'm not quite sure it is
effective. I still get lost keys with
while true; do setleds +num; setleds -num; done
Pavel
--- tmp/linux/drivers/input/keyboard/atkbd.c 2004-04-27 00:41:19.000000000 +0200
+++ linux/drivers/input/keyboard/atkbd.c 2004-04-27 00:36:10.000000000 +0200
@@ -244,7 +244,7 @@
goto out;
}
- if (atkbd->cmdcnt) {
+ if (atkbd->cmdcnt && atomic_read(&atkbd->ack) == 1) {
atkbd->cmdbuf[--atkbd->cmdcnt] = code;
goto out;
}
@@ -366,10 +366,12 @@
* replacement anyway, and they only make a mess in the protocol.
*/
-static int atkbd_sendbyte(struct atkbd *atkbd, unsigned char byte)
+static int atkbd_sendbyte(struct atkbd *atkbd, unsigned char byte, int cmdcnt)
{
int timeout = 20000; /* 200 msec */
- atomic_set(&atkbd->ack, 0); mb();
+ atomic_set(&atkbd->ack, 0);
+ mb(); /* First clear ACK, then write how many reply bytes we want... though maybe it would want real spinlock */
+ atkbd->cmdcnt = cmdcnt;
#ifdef ATKBD_DEBUG
printk(KERN_DEBUG "atkbd.c: Sent: %02x\n", byte);
@@ -397,8 +399,6 @@
int receive = (command >> 8) & 0xf;
int i;
- atkbd->cmdcnt = receive;
-
if (command == ATKBD_CMD_RESET_BAT)
timeout = 2000000; /* 2 sec */
@@ -407,11 +407,11 @@
atkbd->cmdbuf[(receive - 1) - i] = param[i];
if (command & 0xff)
- if (atkbd_sendbyte(atkbd, command & 0xff))
+ if (atkbd_sendbyte(atkbd, command & 0xff, send ? 0 : receive))
return (atkbd->cmdcnt = 0) - 1;
for (i = 0; i < send; i++)
- if (atkbd_sendbyte(atkbd, param[i]))
+ if (atkbd_sendbyte(atkbd, param[i], (i != send - 1) ? 0 : receive))
return (atkbd->cmdcnt = 0) - 1;
while (atkbd->cmdcnt && timeout--) {
--
934a471f20d6580d5aad759bf0d97ddc
prev parent reply other threads:[~2004-04-26 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 21:35 Not so theoretical race in atkbd_command Pavel Machek
2004-04-26 22:49 ` Pavel Machek [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=20040426224911.GA276@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@ucw.cz \
/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