net/iucv: fix the recvmsg window update

Overview

In the Linux kernel, the following vulnerability has been resolved:

net/iucv: fix the recvmsg window update

iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.

It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.

Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.

Affected

• Linux >= 3881ac441f642d56503818123446f7298442236b < 8f2efa742f4cfe7dd756154f8bc07350dbe3ec92
• Linux >= 3881ac441f642d56503818123446f7298442236b < fe7393a627db2d093e8c0cae69d619b30fefae5f
• Linux >= 3881ac441f642d56503818123446f7298442236b < fa5acd038ea657ad5033713d6916214cbd349151
• Linux 3.2

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.