ghsa-grc2-v3f8-wj3j
Vulnerability from github
Published
2024-07-16 12:30
Modified
2024-08-07 21:31
Severity ?
Details
In the Linux kernel, the following vulnerability has been resolved:
nvme-rdma: fix possible use-after-free in transport error_recovery work
While nvme_rdma_submit_async_event_work is checking the ctrl and queue state before preparing the AER command and scheduling io_work, in order to fully prevent a race where this check is not reliable the error recovery work must flush async_event_work before continuing to destroy the admin queue after setting the ctrl state to RESETTING such that there is no race .submit_async_event and the error recovery handler itself changing the ctrl state.
{ affected: [], aliases: [ "CVE-2022-48788", ], database_specific: { cwe_ids: [ "CWE-416", ], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2024-07-16T12:15:03Z", severity: "HIGH", }, details: "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-rdma: fix possible use-after-free in transport error_recovery work\n\nWhile nvme_rdma_submit_async_event_work is checking the ctrl and queue\nstate before preparing the AER command and scheduling io_work, in order\nto fully prevent a race where this check is not reliable the error\nrecovery work must flush async_event_work before continuing to destroy\nthe admin queue after setting the ctrl state to RESETTING such that\nthere is no race .submit_async_event and the error recovery handler\nitself changing the ctrl state.", id: "GHSA-grc2-v3f8-wj3j", modified: "2024-08-07T21:31:43Z", published: "2024-07-16T12:30:39Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2022-48788", }, { type: "WEB", url: "https://git.kernel.org/stable/c/324f5bdc52ecb6a6dadb31a62823ef8c709d1439", }, { type: "WEB", url: "https://git.kernel.org/stable/c/5593f72d1922403c11749532e3a0aa4cf61414e9", }, { type: "WEB", url: "https://git.kernel.org/stable/c/646952b2210f19e584d2bf9eb5d092abdca2fcc1", }, { type: "WEB", url: "https://git.kernel.org/stable/c/b6bb1722f34bbdbabed27acdceaf585d300c5fd2", }, { type: "WEB", url: "https://git.kernel.org/stable/c/d411b2a5da68b8a130c23097014434ac140a2ace", }, { type: "WEB", url: "https://git.kernel.org/stable/c/ea86027ac467a055849c4945906f799e7f65ab99", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", type: "CVSS_V3", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
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.