CVE-2022-49791

In the Linux kernel, the following vulnerability has been resolved:

io_uring: fix multishot accept request leaks

Having REQ_F_POLLED set doesnt guarantee that the request is executed as a multishot from the polling path. Fortunately for us, if the code thinks its multishot issue when its not, it can only ask to skip completion so leaking the request. Use issue_flags to mark multipoll issues.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Software

Potential Mitigations

• Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
• For example, glibc in Linux provides protection against free of invalid pointers.
• When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
• To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References

• https://git.kernel.org/stable/c/0e4626de856ef8f25ecd9c716e76d4f95ce95639
• https://git.kernel.org/stable/c/91482864768a874c4290ef93b84a78f4f1dac51b