ghsa-3h24-5m24-pxvw
Vulnerability from github
Published
2024-12-27 15:31
Modified
2025-01-14 15:30
Severity ?
Details
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but leave the dangling pointer in the sock object, which may cause use-after-free.
Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().
{ affected: [], aliases: [ "CVE-2024-56604", ], database_specific: { cwe_ids: [ "CWE-416", ], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2024-12-27T15:15:19Z", severity: "HIGH", }, details: "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()\n\nbt_sock_alloc() attaches allocated sk object to the provided sock object.\nIf rfcomm_dlc_alloc() fails, we release the sk object, but leave the\ndangling pointer in the sock object, which may cause use-after-free.\n\nFix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().", id: "GHSA-3h24-5m24-pxvw", modified: "2025-01-14T15:30:50Z", published: "2024-12-27T15:31:54Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-56604", }, { type: "WEB", url: "https://git.kernel.org/stable/c/32df687e129ef0f9afcbcc914f7c32deb28fd481", }, { type: "WEB", url: "https://git.kernel.org/stable/c/3945c799f12b8d1f49a3b48369ca494d981ac465", }, { type: "WEB", url: "https://git.kernel.org/stable/c/6021ccc2471b7b95e29b7cfc7938e042bf56e281", }, { type: "WEB", url: "https://git.kernel.org/stable/c/ac3eaac4cf142a15fe67be747a682b1416efeb6e", }, ], 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.