CVE-2022-49767
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2022
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
9p/trans_fd: always use O_NONBLOCK read/write
In the Linux kernel, the following vulnerability has been resolved: 9p/trans_fd: always use O_NONBLOCK read/write syzbot is reporting hung task at p9_fd_close() [1], for p9_mux_poll_stop() from p9_conn_destroy() from p9_fd_close() is failing to interrupt already started kernel_read() from p9_fd_read() from p9_read_work() and/or kernel_write() from p9_fd_write() from p9_write_work() requests. Since p9_socket_open() sets O_NONBLOCK flag, p9_mux_poll_stop() does not need to interrupt kernel_read()/kernel_write(). However, since p9_fd_open() does not set O_NONBLOCK flag, but pipe blocks unless signal is pending, p9_mux_poll_stop() needs to interrupt kernel_read()/kernel_write() when the file descriptor refers to a pipe. In other words, pipe file descriptor needs to be handled as if socket file descriptor. We somehow need to interrupt kernel_read()/kernel_write() on pipes. A minimal change, which this patch is doing, is to set O_NONBLOCK flag from p9_fd_open(), for O_NONBLOCK flag does not affect reading/writing of regular files. But this approach changes O_NONBLOCK flag on userspace- supplied file descriptors (which might break userspace programs), and O_NONBLOCK flag could be changed by userspace. It would be possible to set O_NONBLOCK flag every time p9_fd_read()/p9_fd_write() is invoked, but still remains small race window for clearing O_NONBLOCK flag. If we don't want to manipulate O_NONBLOCK flag, we might be able to surround kernel_read()/kernel_write() with set_thread_flag(TIF_SIGPENDING) and recalc_sigpending(). Since p9_read_work()/p9_write_work() works are processed by kernel threads which process global system_wq workqueue, signals could not be delivered from remote threads when p9_mux_poll_stop() from p9_conn_destroy() from p9_fd_close() is called. Therefore, calling set_thread_flag(TIF_SIGPENDING)/recalc_sigpending() every time would be needed if we count on signals for making kernel_read()/kernel_write() non-blocking. [Dominique: add comment at Christian's suggestion]
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | 0b5e6bd72b8171364616841603a70e4ba9837063 | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | 9f8554615df668e4bf83294633ee9d232b28ce45 | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | 7abf40f06a76c0dff42eada10597917e9776fbd4 | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | b1ad04da7fe4515e2ce2d5f2dcab3b5b6d45614b | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | a8e2fc8f7b41fa9d9ca5f624f4e4d34fce5b40a9 | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | 0e07032b4b4724b8ad1003698cb81083c1818999 | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | 5af16182c5639349415118e9e9aecd8355f7a08b | Unavailable | None listed |
| 27979bb2ff748613dba96ae66392a76fb0678527 | affected | git | ef575281b21e9a34dfae544a187c6aac2ae424a9 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 2.6.17 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 2.6.17 | Unavailable | None listed |
| 4.9.334 | unaffected | semver | Unavailable | 4.9.* | None listed |
| 4.14.300 | unaffected | semver | Unavailable | 4.14.* | None listed |
| 4.19.267 | unaffected | semver | Unavailable | 4.19.* | None listed |
| 5.4.225 | unaffected | semver | Unavailable | 5.4.* | None listed |
| 5.10.156 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.80 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 6.0.10 | unaffected | semver | Unavailable | 6.0.* | None listed |
| 6.1 | unaffected | original_commit_for_fix | Unavailable | * | None listed |