io_uring/net: ensure vectored buffer node import is tied to notification
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
io_uring/net: ensure vectored buffer node import is tied to notification
When support for vectored registered buffers was added, the import itself is using 'req' rather than the notification io_kiocb, sr->notif. For non-vectored imports, sr->notif is correctly used. This is important as the lifetime of the two may be different. Use the correct io_kiocb for the vectored buffer import.
From the CVE record · Linux
The Linux kernel’s io_uring/net code ties vectored registered-buffer imports to the request rather than the notification, whose lifetime may differ. The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Operators running the Linux kernel should check their versions against the vendor advisory; affected versions were not provided.