CVE-2025-71312

{"id": "CVE-2025-71312", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}]}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "129b0a64fe9ac5b4138cc123cccbcce7c65afdf4", "lessThan": "d977b979081ef2585a15453f309a6311c95ede02", "versionType": "git"}, {"status": "affected", "version": "aee4d5a521e94f658e46c904e08a473daa9c8fc0", "lessThan": "dac871d833b09495198dcac81d2ebaa8db11acbc", "versionType": "git"}, {"status": "affected", "version": "aee4d5a521e94f658e46c904e08a473daa9c8fc0", "lessThan": "f7edab0cee03a1cbe0e55a7bcab8d2d8b6b74278", "versionType": "git"}], "programFiles": ["fs/ntfs3/super.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.19"}, {"status": "unaffected", "version": "0", "lessThan": "6.19", "versionType": "semver"}, {"status": "unaffected", "version": "6.19.4", "versionType": "semver", "lessThanOrEqual": "6.19.*"}, {"status": "unaffected", "version": "7.0", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["fs/ntfs3/super.c"], "defaultStatus": "affected"}]}], "published": "2026-05-27T14:16:43.763", "references": [{"url": "https://git.kernel.org/stable/c/d977b979081ef2585a15453f309a6311c95ede02", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/dac871d833b09495198dcac81d2ebaa8db11acbc", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/f7edab0cee03a1cbe0e55a7bcab8d2d8b6b74278", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-401"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: fix ntfs_mount_options leak in ntfs_fill_super()\n\nIn ntfs_fill_super(), the fc->fs_private pointer is set to NULL without\nfirst freeing the memory it points to. This causes the subsequent call to\nntfs_fs_free() to skip freeing the ntfs_mount_options structure.\n\nThis results in a kmemleak report:\n\n unreferenced object 0xff1100015378b800 (size 32):\n comm \"mount\", pid 582, jiffies 4294890685\n hex dump (first 32 bytes):\n 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n 00 00 00 00 00 00 00 00 ed ff ed ff 00 04 00 00 ................\n backtrace (crc ed541d8c):\n __kmalloc_cache_noprof+0x424/0x5a0\n __ntfs_init_fs_context+0x47/0x590\n alloc_fs_context+0x5d8/0x960\n __x64_sys_fsopen+0xb1/0x190\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThis issue can be reproduced using the following commands:\n fallocate -l 100M test.file\n mount test.file /tmp/test\n\nSince sbi->options is duplicated from fc->fs_private and does not\ndirectly use the memory allocated for fs_private, it is unnecessary to\nset fc->fs_private to NULL.\n\nAdditionally, this patch simplifies the code by utilizing the helper\nfunction put_mount_options() instead of open-coding the cleanup logic."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nfs/ntfs3: correcci\u00f3n de fuga de ntfs_mount_options en ntfs_fill_super()\n\nEn ntfs_fill_super(), el puntero fc -> fs_private se establece en NULL sin liberar primero la memoria a la que apunta. Esto provoca que la llamada subsiguiente a ntfs_fs_free() omita liberar la estructura ntfs_mount_options.\n\nEsto resulta en un informe de kmemleak:\n\n objeto sin referencia 0xff1100015378b800 (tama\u00f1o 32):\n comm 'mount', pid 582, jiffies 4294890685\n volcado hexadecimal (primeros 32 bytes):\n 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n 00 00 00 00 00 00 00 00 ed ff ed ff 00 04 00 00 ................\n rastreo de pila (crc ed541d8c):\n __kmalloc_cache_noprof+0x424/0x5a0\n __ntfs_init_fs_context+0x47/0x590\n alloc_fs_context+0x5d8/0x960\n __x64_sys_fsopen+0xb1/0x190\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nEste problema puede reproducirse usando los siguientes comandos:\n fallocate -l 100M test.file\n mount test.file /tmp/test\n\nDado que sbi -> options se duplica de fc -> fs_private y no utiliza directamente la memoria asignada para fs_private, es innecesario establecer fc -> fs_private en NULL.\n\nAdem\u00e1s, este parche simplifica el c\u00f3digo al utilizar la funci\u00f3n auxiliar put_mount_options() en lugar de codificar directamente la l\u00f3gica de limpieza."}], "lastModified": "2026-10-26T16:17:09.720", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "672A3E79-EC03-479D-8503-361DFBDC8092", "versionEndExcluding": "6.19.4", "versionStartIncluding": "6.19"}], "operator": "OR"}]}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}