CVE-2025-38451

{"id": "CVE-2025-38451", "cveTags": [], "metrics": {}, "published": "2025-07-25T16:15:30.680", "references": [{"url": "https://git.kernel.org/stable/c/3d82a729530bd2110ba66e4a1f73461c776edec2", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/3e0542701b37aa25b025d8531583458e4f014c2e", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/a18f9b08c70e10ea3a897058fee8a4f3b4c146ec", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/a23b16ba3274961494f5ad236345d238364349ff", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/c17fb542dbd1db745c9feac15617056506dd7195", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd/md-bitmap: fix GPF in bitmap_get_stats()\n\nThe commit message of commit 6ec1f0239485 (\"md/md-bitmap: fix stats\ncollection for external bitmaps\") states:\n\n Remove the external bitmap check as the statistics should be\n available regardless of bitmap storage location.\n\n Return -EINVAL only for invalid bitmap with no storage (neither in\n superblock nor in external file).\n\nBut, the code does not adhere to the above, as it does only check for\na valid super-block for \"internal\" bitmaps. Hence, we observe:\n\nOops: GPF, probably for non-canonical address 0x1cd66f1f40000028\nRIP: 0010:bitmap_get_stats+0x45/0xd0\nCall Trace:\n\n seq_read_iter+0x2b9/0x46a\n seq_read+0x12f/0x180\n proc_reg_read+0x57/0xb0\n vfs_read+0xf6/0x380\n ksys_read+0x6d/0xf0\n do_syscall_64+0x8c/0x1b0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nWe fix this by checking the existence of a super-block for both the\ninternal and external case."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: md/md-bitmap: correcci\u00f3n de GPF en bitmap_get_stats(). El mensaje del commit 6ec1f0239485 (\"md/md-bitmap: correcci\u00f3n de la recopilaci\u00f3n de estad\u00edsticas para mapas de bits externos\") indica: Se elimina la comprobaci\u00f3n de mapas de bits externos, ya que las estad\u00edsticas deben estar disponibles independientemente de su ubicaci\u00f3n de almacenamiento. Se devuelve -EINVAL solo para mapas de bits no v\u00e1lidos sin almacenamiento (ni en superbloque ni en archivo externo). Sin embargo, el c\u00f3digo no cumple con lo anterior, ya que solo comprueba si hay un superbloque v\u00e1lido para mapas de bits \"internos\". Por lo tanto, observamos: Oops: GPF, probablemente para la direcci\u00f3n no can\u00f3nica 0x1cd66f1f40000028 RIP: 0010:bitmap_get_stats+0x45/0xd0 Rastreo de llamadas: seq_read_iter+0x2b9/0x46a seq_read+0x12f/0x180 proc_reg_read+0x57/0xb0 vfs_read+0xf6/0x380 ksys_read+0x6d/0xf0 do_syscall_64+0x8c/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Solucionamos esto verificando la existencia de un superbloque tanto para el caso interno como para el externo."}], "lastModified": "2025-07-29T14:14:55.157", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}