Bug 2179153 (CVE-2023-1032)
| Summary: | CVE-2023-1032 kernel: io_uring IORING_OP_SOCKET double free | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Rohit Keshri <rkeshri> |
| Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | acaringi, allarkin, bhu, chwhite, crwood, ddepaula, debarbos, dfreiber, dhoward, dvlasenk, ezulian, fhrbata, hkrzesin, jarod, jburrell, jfaracco, jferlan, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, kernel-mgr, lgoncalv, lleshchi, lzampier, nmurray, ptalbert, qzhao, rogbas, rvrbovsk, scweaver, tyberry, vkumar, walters, williams |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Kernel 6.3 RC2 | Doc Type: | If docs needed, set a value |
| Doc Text: |
A double-free vulnerability was found in handling the IORING_OP_SOCKET operation with io_uring in the Linux kernel. This issue requires a memory allocation failure to happen, which is followed by a double-free of a recently allocated object.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-03-16 22:59:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2177910 | ||
There was no shipped kernel version were seen affected with this problem. This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2023-1032 |
A double-free vulnerability was found in the handling of IORING_OP_SOCKET operation with io_uring on the Linux kernel. It was fixed by commit: 649c15c7691e9b13cbe9bf6c65c365350e056067 ("net: avoid double iput when sock_alloc_file fails")