CVE-2026-43388

{"id": "CVE-2026-43388", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.8, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "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": "bf0eaba0ff9c9c8e6fd58ddfa1a8b6df4b813f61", "lessThan": "ce0aa47c963b8c3e5beace89e2b5a665a64b5b6b", "versionType": "git"}, {"status": "affected", "version": "bf0eaba0ff9c9c8e6fd58ddfa1a8b6df4b813f61", "lessThan": "9320c77134ab8d7701e20608bbf08517df4fa321", "versionType": "git"}, {"status": "affected", "version": "bf0eaba0ff9c9c8e6fd58ddfa1a8b6df4b813f61", "lessThan": "d210fdcac9c0d1380eab448aebc93f602c1cd4e6", "versionType": "git"}], "programFiles": ["mm/damon/core.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.14"}, {"status": "unaffected", "version": "0", "lessThan": "6.14", "versionType": "semver"}, {"status": "unaffected", "version": "6.18.19", "versionType": "semver", "lessThanOrEqual": "6.18.*"}, {"status": "unaffected", "version": "6.19.9", "versionType": "semver", "lessThanOrEqual": "6.19.*"}, {"status": "unaffected", "version": "7.0", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["mm/damon/core.c"], "defaultStatus": "affected"}]}], "published": "2026-05-08T15:16:50.180", "references": [{"url": "https://git.kernel.org/stable/c/9320c77134ab8d7701e20608bbf08517df4fa321", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/ce0aa47c963b8c3e5beace89e2b5a665a64b5b6b", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/d210fdcac9c0d1380eab448aebc93f602c1cd4e6", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-416"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: clear walk_control on inactive context in damos_walk()\n\ndamos_walk() sets ctx->walk_control to the caller-provided control\nstructure before checking whether the context is running. If the context\nis inactive (damon_is_running() returns false), the function returns\n-EINVAL without clearing ctx->walk_control. This leaves a dangling\npointer to a stack-allocated structure that will be freed when the caller\nreturns.\n\nThis is structurally identical to the bug fixed in commit f9132fbc2e83\n(\"mm/damon/core: remove call_control in inactive contexts\") for\ndamon_call(), which had the same pattern of linking a control object and\nreturning an error without unlinking it.\n\nThe dangling walk_control pointer can cause:\n1. Use-after-free if the context is later started and kdamond\n\u00a0 \u00a0dereferences ctx->walk_control (e.g., in damos_walk_cancel()\n\u00a0 \u00a0which writes to control->canceled and calls complete())\n2. Permanent -EBUSY from subsequent damos_walk() calls, since the\n\u00a0 \u00a0stale pointer is non-NULL\n\nNonetheless, the real user impact is quite restrictive. The\nuse-after-free is impossible because there is no damos_walk() callers who\nstarts the context later. The permanent -EBUSY can actually confuse\nusers, as DAMON is not running. But the symptom is kept only while the\ncontext is turned off. Turning it on again will make DAMON internally\nuses a newly generated damon_ctx object that doesn't have the invalid\ndamos_walk_control pointer, so everything will work fine again.\n\nFix this by clearing ctx->walk_control under walk_control_lock before\nreturning -EINVAL, mirroring the fix pattern from f9132fbc2e83."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nmm/damon/core: limpiar walk_control en contexto inactivo en damos_walk()\n\ndamos_walk() establece ctx -> walk_control a la estructura de control proporcionada por el llamador antes de verificar si el contexto est\u00e1 en ejecuci\u00f3n. Si el contexto est\u00e1 inactivo (damon_is_running() devuelve falso), la funci\u00f3n devuelve -EINVAL sin limpiar ctx -> walk_control. Esto deja un puntero colgante a una estructura asignada en la pila que ser\u00e1 liberada cuando el llamador regrese.\n\nEsto es estructuralmente id\u00e9ntico al error corregido en el commit f9132fbc2e83 (\u2019mm/damon/core: eliminar call_control en contextos inactivos\u2019) para damon_call(), que ten\u00eda el mismo patr\u00f3n de vincular un objeto de control y devolver un error sin desvincularlo.\n\nEl puntero colgante walk_control puede causar:\n1. Uso despu\u00e9s de liberaci\u00f3n si el contexto se inicia m\u00e1s tarde y kdamond desreferencia ctx -> walk_control (por ejemplo, en damos_walk_cancel() que escribe en control -> canceled y llama a complete())\n2. -EBUSY permanente de llamadas posteriores a damos_walk(), ya que el puntero obsoleto no es nulo\n\nNo obstante, el impacto real para el usuario es bastante restrictivo. El uso despu\u00e9s de liberaci\u00f3n es imposible porque no hay llamadores de damos_walk() que inicien el contexto m\u00e1s tarde. El -EBUSY permanente puede de hecho confundir a los usuarios, ya que DAMON no est\u00e1 en ejecuci\u00f3n. Pero el s\u00edntoma se mantiene solo mientras el contexto est\u00e1 desactivado. Volver a activarlo har\u00e1 que DAMON use internamente un objeto damon_ctx reci\u00e9n generado que no tiene el puntero damos_walk_control inv\u00e1lido, por lo que todo volver\u00e1 a funcionar correctamente.\n\nSolucione esto limpiando ctx -> walk_control bajo walk_control_lock antes de devolver -EINVAL, replicando el patr\u00f3n de correcci\u00f3n de f9132fbc2e83."}], "lastModified": "2026-11-11T20:10:00.273", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "7484E98E-61F0-4DCE-9DBF-83D2F75F99EB", "versionEndExcluding": "6.18.19", "versionStartIncluding": "6.14"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "E825E7C3-FEAC-4FD3-8A81-78D7387948C9", "versionEndExcluding": "6.19.9", "versionStartIncluding": "6.19"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F253B622-8837-4245-BCE5-A7BF8FC76A16"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4AE85AD8-4641-4E7C-A2F4-305E2CD9EE64"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "F666C8D8-6538-46D4-B318-87610DE64C34"}], "operator": "OR"}]}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}