af_unix: Give up GC if MSG_PEEK intervened.
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 118f457da9ed58a79e24b73c2ef0aa1987241f0e · < e5b31d988a41549037b8d8721a3c3cae893d8670| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
af_unix: Give up GC if MSG_PEEK intervened.
Igor Ushakov reported that GC purged the receive queue of an alive socket due to a race with MSG_PEEK with a nice repro.
This is the exact same issue previously fixed by commit cbcf01128d0a ("af_unix: fix garbage collect vs MSG_PEEK").
After GC was replaced with the current algorithm, the cited commit removed the locking dance in unix_peek_fds() and reintroduced the same issue.
The problem is that MSG_PEEK bumps a file refcount without interacting with GC.
Consider an SCC containing sk-A and sk-B, where sk-A is close()d but can be recv()ed via sk-B.
The bad thing happens if sk-A is recv()ed with MSG_PEEK from sk-B and sk-B is close()d while GC is checking unix_vertex_dead() for sk-A and sk-B.
From the CVE record · Linux
A race between MSG_PEEK and garbage collection in the Linux kernel’s af_unix component can cause garbage collection to purge the receive queue of a live socket. The race requires concurrent socket operations, including MSG_PEEK and close(); the input does not specify authentication requirements or user interaction.
Engineers running the Linux kernel should check their installations; affected versions were not provided.