ghsa-q4c9-gg27-f3pq
Vulnerability from github
Published
2022-05-24 19:04
Modified
2022-05-24 19:04
Details
The io_uring subsystem in the Linux kernel allowed the MAX_RW_COUNT limit to be bypassed in the PROVIDE_BUFFERS operation, which led to negative values being usedin mem_rw when reading /proc/
{ "affected": [], "aliases": [ "CVE-2021-3491" ], "database_specific": { "cwe_ids": [ "CWE-787" ], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2021-06-04T02:15:00Z", "severity": "HIGH" }, "details": "The io_uring subsystem in the Linux kernel allowed the MAX_RW_COUNT limit to be bypassed in the PROVIDE_BUFFERS operation, which led to negative values being usedin mem_rw when reading /proc/\u003cPID\u003e/mem. This could be used to create a heap overflow leading to arbitrary code execution in the kernel. It was addressed via commit d1f82808877b (\"io_uring: truncate lengths larger than MAX_RW_COUNT on provide buffers\") (v5.13-rc1) and backported to the stable kernels in v5.12.4, v5.11.21, and v5.10.37. It was introduced in ddf0322db79c (\"io_uring: add IORING_OP_PROVIDE_BUFFERS\") (v5.7-rc1).", "id": "GHSA-q4c9-gg27-f3pq", "modified": "2022-05-24T19:04:07Z", "published": "2022-05-24T19:04:07Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3491" }, { "type": "WEB", "url": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1f82808877bb10d3deee7cf3374a4eb3fb582db" }, { "type": "WEB", "url": "https://security.netapp.com/advisory/ntap-20210716-0004" }, { "type": "WEB", "url": "https://ubuntu.com/security/notices/USN-4949-1" }, { "type": "WEB", "url": "https://ubuntu.com/security/notices/USN-4950-1" }, { "type": "WEB", "url": "https://www.openwall.com/lists/oss-security/2021/05/11/13" }, { "type": "WEB", "url": "https://www.zerodayinitiative.com/advisories/ZDI-21-589" } ], "schema_version": "1.4.0", "severity": [] }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.