ghsa-w5j3-3j83-3j22
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:
iwlwifi: fix use-after-free
If no firmware was present at all (or, presumably, all of the firmware files failed to parse), we end up unbinding by calling device_release_driver(), which calls remove(), which then in iwlwifi calls iwl_drv_stop(), freeing the 'drv' struct. However the new code I added will still erroneously access it after it was freed.
Set 'failure=false' in this case to avoid the access, all data was already freed anyway.
{ affected: [], aliases: [ "CVE-2022-48787", ], 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\niwlwifi: fix use-after-free\n\nIf no firmware was present at all (or, presumably, all of the\nfirmware files failed to parse), we end up unbinding by calling\ndevice_release_driver(), which calls remove(), which then in\niwlwifi calls iwl_drv_stop(), freeing the 'drv' struct. However\nthe new code I added will still erroneously access it after it\nwas freed.\n\nSet 'failure=false' in this case to avoid the access, all data\nwas already freed anyway.", id: "GHSA-w5j3-3j83-3j22", modified: "2024-08-07T21:31:43Z", published: "2024-07-16T12:30:39Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2022-48787", }, { type: "WEB", url: "https://git.kernel.org/stable/c/008508c16af0087cda0394e1ac6f0493b01b6063", }, { type: "WEB", url: "https://git.kernel.org/stable/c/494de920d98f125b099f27a2d274850750aff957", }, { type: "WEB", url: "https://git.kernel.org/stable/c/7d6475179b85a83186ccce59cdc359d4f07d0bcb", }, { type: "WEB", url: "https://git.kernel.org/stable/c/9958b9cbb22145295ee1ffaea0904c383da2c05d", }, { type: "WEB", url: "https://git.kernel.org/stable/c/bea2662e7818e15d7607d17d57912ac984275d94", }, { type: "WEB", url: "https://git.kernel.org/stable/c/d3b98fe36f8a06ce654049540773256ab59cb53d", }, { type: "WEB", url: "https://git.kernel.org/stable/c/ddd46059f7d99119b62d44c519df7a79f2e6a515", }, ], 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.