diff options
| author | Josh Bleecher Snyder <josh@tailscale.com> | 2021-02-09 09:53:00 -0800 |
|---|---|---|
| committer | Josh Bleecher Snyder <josh@tailscale.com> | 2021-02-09 09:53:00 -0800 |
| commit | 4eab21a7b7192dc806a3d60c46827866fc8942fe (patch) | |
| tree | fba61d85d5c4b8d16e050af626ff180b3193eb0b /device/device.go | |
| parent | 30b96ba083e4ef61051f125770b50bd278712539 (diff) | |
| download | wireguard-go-4eab21a7b7192dc806a3d60c46827866fc8942fe.tar.gz wireguard-go-4eab21a7b7192dc806a3d60c46827866fc8942fe.zip | |
device: make RoutineReadFromTUN keep encryption queue alive
RoutineReadFromTUN can trigger a call to SendStagedPackets.
SendStagedPackets attempts to protect against sending
on the encryption queue by checking peer.isRunning and device.isClosed.
However, those are subject to TOCTOU bugs.
If that happens, we get this:
goroutine 1254 [running]:
golang.zx2c4.com/wireguard/device.(*Peer).SendStagedPackets(0xc000798300)
.../wireguard-go/device/send.go:321 +0x125
golang.zx2c4.com/wireguard/device.(*Device).RoutineReadFromTUN(0xc000014780)
.../wireguard-go/device/send.go:271 +0x21c
created by golang.zx2c4.com/wireguard/device.NewDevice
.../wireguard-go/device/device.go:315 +0x298
Fix this with a simple, big hammer: Keep the encryption queue
alive as long as it might be written to.
Signed-off-by: Josh Bleecher Snyder <josh@tailscale.com>
Diffstat (limited to 'device/device.go')
| -rw-r--r-- | device/device.go | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/device/device.go b/device/device.go index 586715e..9375448 100644 --- a/device/device.go +++ b/device/device.go @@ -311,7 +311,8 @@ func NewDevice(tunDevice tun.Device, logger *Logger) *Device { go device.RoutineHandshake() } - device.state.stopping.Add(1) // read from TUN + device.state.stopping.Add(1) // RoutineReadFromTUN + device.queue.encryption.wg.Add(1) // RoutineReadFromTUN go device.RoutineReadFromTUN() go device.RoutineTUNEventReader() |