Skip to contentSkip to conversation

vhost/net: fix heads usage of ubuf_info

PATCH In review Michael S. Tsirkin 3 participants 8 messages Mar 17, 2013 – Mar 21, 2013

Subsystems (5)
lore
Share & tools
lore

Michael S. Tsirkin

author maintainer
#0 lore raw

PATCH 1/1 vhost/net: fix heads usage of ubuf_info

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

---

Rusty's working on switching to allocating ubufs dynamically but that's not 3.9 material.
This patch is against latest net master,
needed for 3.9-rc2 and older kernels.

 drivers/vhost/net.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/vhost/net.c +2 -1
index 959b1cd..ec6fb3f 100644
@@ -339,7 +339,8 @@ static void handle_tx(struct vhost_net *net)
 				msg.msg_controllen = 0;
 				ubufs = NULL;
 			} else {
-				struct ubuf_info *ubuf = &vq->ubuf_info[head];
+				struct ubuf_info *ubuf;
+				ubuf = vq->ubuf_info + vq->upend_idx;
 
 				vq->heads[vq->upend_idx].len =
 					VHOST_DMA_IN_PROGRESS;
Signature · 1 line
MST
maintainer
#1 lore raw

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 7 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Applied and queued up for -stable, thanks.

And thankfully you got the stable URL wrong, please do not CC:
networking patches to stable, just make sure I apply them and in your post-commit text explicitly ask me to queue it up to my -stable queue.

Thanks.

author maintainer
#2 lore raw
Quoted 8 lines · David Miller

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 5 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Quoted 4 lines
Quoted 2 lines

Applied and queued up for -stable, thanks.

OK I'll drop it from my tree then.

author maintainer
#3 lore raw
In reply to David Miller
Quoted 8 lines · David Miller

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 5 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Quoted 6 lines
Quoted 2 lines

Applied and queued up for -stable, thanks.

And thankfully you got the stable URL wrong,

Yes I wrote [email protected] that's what an old copy says here:
https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt

I should have known better than look at it on the 'net. The top 'Everything you ever wanted to know about Linux 2.6 -stable releases.' is a big hint that it's stale.
Any idea who maintains this? Better update it or remove it or redirect to git.

Quoted 6 lines

please do not CC:
networking patches to stable, just make sure I apply them and in your post-commit text explicitly ask me to queue it up to my -stable queue.

Thanks.

#4 lore raw
Quoted 16 lines · Michael S. Tsirkin
Quoted 8 lines · David Miller

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 5 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Quoted 6 lines
Quoted 2 lines

Applied and queued up for -stable, thanks.

And thankfully you got the stable URL wrong,

Quoted 8 lines

Yes I wrote [email protected] that's what an old copy says here:
https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt

I should have known better than look at it on the 'net. The top 'Everything you ever wanted to know about Linux 2.6 -stable releases.' is a big hint that it's stale.
Any idea who maintains this? Better update it or remove it or redirect to git.

Rob Landley maintains it, but he's been having trouble updating it since all the upload mechanisms were changed on kernel.org.

(My stable maintenance scripts still match the old address, anyway. Not sure about Greg's.)

Ben.

Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
author maintainer
#5 lore raw
Quoted 26 lines · Ben Hutchings
Quoted 16 lines · Michael S. Tsirkin
Quoted 8 lines · David Miller

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 5 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Quoted 6 lines
Quoted 2 lines

Applied and queued up for -stable, thanks.

And thankfully you got the stable URL wrong,

Quoted 8 lines

Yes I wrote [email protected] that's what an old copy says here:
https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt

I should have known better than look at it on the 'net. The top 'Everything you ever wanted to know about Linux 2.6 -stable releases.' is a big hint that it's stale.
Any idea who maintains this? Better update it or remove it or redirect to git.

Quoted 7 lines

Rob Landley maintains it, but he's been having trouble updating it since all the upload mechanisms were changed on kernel.org.

(My stable maintenance scripts still match the old address, anyway. Not sure about Greg's.)

Ben.

I hope you mean it will match both the old and the new address?

Quoted 4 lines
Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
#6 lore raw
Quoted 30 lines · Michael S. Tsirkin
Quoted 29 lines · Ben Hutchings
Quoted 16 lines · Michael S. Tsirkin
Quoted 8 lines · David Miller

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 5 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Quoted 6 lines
Quoted 2 lines

Applied and queued up for -stable, thanks.

And thankfully you got the stable URL wrong,

Quoted 8 lines

Yes I wrote [email protected] that's what an old copy says here:
https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt

I should have known better than look at it on the 'net. The top 'Everything you ever wanted to know about Linux 2.6 -stable releases.' is a big hint that it's stale.
Any idea who maintains this? Better update it or remove it or redirect to git.

Rob Landley maintains it, but he's been having trouble updating it since all the upload mechanisms were changed on kernel.org.

Quoted 6 lines
Quoted 4 lines

(My stable maintenance scripts still match the old address, anyway. Not sure about Greg's.)

Ben.

I hope you mean it will match both the old and the new address?

Yes, of course!

Ben.

Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
#7 lore raw
In reply to Michael S. Tsirkin
Quoted 16 lines · Michael S. Tsirkin
Quoted 8 lines · David Miller

From: "Michael S. Tsirkin" <[email protected]>
Date: Sun, 17 Mar 2013 14:46:09 +0200

Quoted 5 lines

ubuf info allocator uses guest controlled head as an index, so a malicious guest could put the same head entry in the ring twice, and we will get two callbacks on the same value.
To fix use upend_idx which is guaranteed to be unique.

Quoted 6 lines
Quoted 2 lines

Applied and queued up for -stable, thanks.

And thankfully you got the stable URL wrong,

Quoted 8 lines

Yes I wrote [email protected] that's what an old copy says here:
https://www.kernel.org/doc/Documentation/stable_kernel_rules.txt

I should have known better than look at it on the 'net. The top 'Everything you ever wanted to know about Linux 2.6 -stable releases.' is a big hint that it's stale.
Any idea who maintains this? Better update it or remove it or redirect to git.

Rob Landley maintains it, but he's been having trouble updating it since all the upload mechanisms were changed on kernel.org.

(My stable maintenance scripts still match the old address, anyway. Not sure about Greg's.)

Ben.

Signature · 3 lines
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.