io_uring/net: don't overconsume buffers when using MSG_TRUNC
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2e70ea75c7bb38a6dc212975f887310f14f7c043, Kernel 41d24d2fb168fa05fcaf9ec4e55478411dbbf8e1, Kernel 6028b543884f8735e057ec9eea4908cd61cab230 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't overconsume buffers when using MSG_TRUNC When a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is larger than the provided buffer, the net layer returns the full length of the packet rather than the number of bytes actually copied into the buffer. As a result, io_uring advances more of the provided buffer ring than was actually filled. Use the actual filled region size to consume the buffer, but still return the full size to preserve MSG_TRUNC semantics. Take care with multishot, because that seems to already truncate the consumption based on the available payload size. This was reported in https://github.com/axboe/liburing/issues/1619. [axboe: fold in size_t unsigned fix]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.12, >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <2e70ea75c7bb38a6dc212975f887310f14f7c043, >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <41d24d2fb168fa05fcaf9ec4e55478411dbbf8e1, >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <6028b543884f8735e057ec9eea4908cd61cab230, >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <927d96f91c582b319d104ecf50ec935a8dc29193 | 2e70ea75c7bb38a6dc212975f887310f14f7c043, 41d24d2fb168fa05fcaf9ec4e55478411dbbf8e1, 6028b543884f8735e057ec9eea4908cd61cab230, 927d96f91c582b319d104ecf50ec935a8dc29193 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket