2025-01-05 03:03:46 +00:00

37 lines
1.9 KiB
JSON

{
"id": "CVE-2024-56604",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"published": "2024-12-27T15:15:19.887",
"lastModified": "2024-12-27T15:15:19.887",
"vulnStatus": "Awaiting Analysis",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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()."
},
{
"lang": "es",
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: Bluetooth: RFCOMM: evitar dejar el puntero sk colgando en rfcomm_sock_alloc() bt_sock_alloc() adjunta el objeto sk asignado al objeto sock proporcionado. Si rfcomm_dlc_alloc() falla, liberamos el objeto sk, pero dejamos el puntero colgando en el objeto sock, lo que puede provocar un use-after-free. Solucione esto intercambiando las llamadas a bt_sock_alloc() y rfcomm_dlc_alloc()."
}
],
"metrics": {},
"references": [
{
"url": "https://git.kernel.org/stable/c/32df687e129ef0f9afcbcc914f7c32deb28fd481",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3945c799f12b8d1f49a3b48369ca494d981ac465",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/6021ccc2471b7b95e29b7cfc7938e042bf56e281",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ac3eaac4cf142a15fe67be747a682b1416efeb6e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
]
}