af_unix: Reject SIOCATMARK on non-stream sockets
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 314001f0bf927015e459c9d387d62a231fe93af3 · < 3147ddf5a41c20c45c2eb69e00b62f10f822056a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
af_unix: Reject SIOCATMARK on non-stream sockets
SIOCATMARK reports whether the receive queue is at the urgent mark for MSG_OOB.
In AF_UNIX, MSG_OOB is supported only for SOCK_STREAM sockets. SOCK_DGRAM and SOCK_SEQPACKET reject MSG_OOB in sendmsg() and recvmsg(), so they should not support SIOCATMARK either.
Return -EOPNOTSUPP for non-stream sockets before checking the receive queue.
From the CVE record · Linux
The Linux kernel allows SIOCATMARK to check the receive queue on AF_UNIX SOCK_DGRAM and SOCK_SEQPACKET sockets, even though those socket types do not support MSG_OOB. A local caller able to issue the ioctl on one of these sockets can trigger that unsupported check. The input does not specify a further impact or an authentication requirement.
Engineers running Linux kernels should check for this issue; affected versions were not provided.