CVE-2026-72103
In the Linux kernel, the following vulnerability has been resolved:
dm: avoid leaking the caller's thread keyring via the table device file
The refactoring in commit a28d893eb327 ("md: port block device access to file") accidentally causes the caller's thread keyring to be kept alive long beyond the caller's lifetime.
As a result, "cryptsetup luksSuspend" silently fails to wipe the LUKS volume key from memory.
In detail: "cryptsetup luksOpen" uses its supposedly ephemeral thread keyring to pass the volume key to the kernel. dm-crypt's crypt_set_keyring_key() copies the key material into its own crypt_config structure and then drops its own reference to the key in the keyring with key_put().
Leer descripción completaMostrar menos
With this fix, restoring pre-v6.9 behavior, the copy in the thread keyring is then promptly garbage collected, such that exactly one copy of the volume key remains. This single copy is correctly wiped from memory on "cryptsetup luksSuspend".
Without this fix, the thread keyring and the volume key in it remains. This second copy is only freed on "luksClose". "luksSuspend" neither knows about this copy nor has any way to remove it, so the key remains recoverable from RAM after a suspend that is documented to have wiped it.
This fix should not introduce new security problems, as the code is anyway gated by CAP_SYS_ADMIN. The device-mapper core, not the calling task, is the legitimate owner of this long-lived file.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- Puntuación base: 7.3
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.17%
- Percentil entre todas las CVEs puntuadas: 6
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
🎯 Técnicas ATT&CK
Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.
- Explotación
T1068Exploitation for Privilege Escalationprivilege escalation85 % - Impacto principal
T1552.001Credentials In Filescredential access80 %
Vulnerabilidad local (AV:L/PR:L) que permite retener copias de claves criptográficas en memoria tras operaciones que deberían borrarlas, facilitando su recuperación por usuarios locales.
Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.
🛡️ Mitigaciones ATT&CK que cubren estas técnicas
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-72103",
"cveTags": [],
"metrics": {
"cvssMetricV31": [
{
"type": "Secondary",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 7.3,
"attackVector": "LOCAL",
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "LOW",
"privilegesRequired": "LOW",
"confidentialityImpact": "HIGH"
},
"impactScore": 5.5,
"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": "a28d893eb3270cf62c10dd8777af0d8452cdc072",
"lessThan": "d3eb8451d529ea452740d1a2bc395a1d20c48133",
"versionType": "git"
},
{
"status": "affected",
"version": "a28d893eb3270cf62c10dd8777af0d8452cdc072",
"lessThan": "8ced1d242c34e342defcccdb00663354f212aae6",
"versionType": "git"
},
{
"status": "affected",
"version": "a28d893eb3270cf62c10dd8777af0d8452cdc072",
"lessThan": "f00105be6a593920e9bc7949a069d4a116888851",
"versionType": "git"
},
{
"status": "affected",
"version": "a28d893eb3270cf62c10dd8777af0d8452cdc072",
"lessThan": "981ccd97f7153d310dfa92a534525bbaf46752c2",
"versionType": "git"
}
],
"programFiles": [
"drivers/md/dm.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.9"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.9",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.12.101",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.42",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver",
"lessThanOrEqual": "7.1.*"
},
{
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/md/dm.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-08-15T06:21:24.460",
"references": [
{
"url": "https://git.kernel.org/stable/c/8ced1d242c34e342defcccdb00663354f212aae6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/981ccd97f7153d310dfa92a534525bbaf46752c2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/d3eb8451d529ea452740d1a2bc395a1d20c48133",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/f00105be6a593920e9bc7949a069d4a116888851",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm: avoid leaking the caller's thread keyring via the table device file\n\nThe refactoring in commit a28d893eb327 (\"md: port block device access to file\")\naccidentally causes the caller's thread keyring to be kept alive long\nbeyond the caller's lifetime.\n\nAs a result, \"cryptsetup luksSuspend\" silently fails to wipe the\nLUKS volume key from memory.\n\nIn detail: \"cryptsetup luksOpen\" uses its supposedly ephemeral thread\nkeyring to pass the volume key to the kernel. dm-crypt's\ncrypt_set_keyring_key() copies the key material into its own\ncrypt_config structure and then drops its own reference to the key in\nthe keyring with key_put().\n\nWith this fix, restoring pre-v6.9 behavior, the copy in the thread\nkeyring is then promptly garbage collected, such that exactly one copy\nof the volume key remains. This single copy is correctly wiped from\nmemory on \"cryptsetup luksSuspend\".\n\nWithout this fix, the thread keyring and the volume key in it remains.\nThis second copy is only freed on \"luksClose\". \"luksSuspend\" neither\nknows about this copy nor has any way to remove it, so the key remains\nrecoverable from RAM after a suspend that is documented to have wiped it.\n\nThis fix should not introduce new security problems, as the code is\nanyway gated by CAP_SYS_ADMIN. The device-mapper core, not the calling\ntask, is the legitimate owner of this long-lived file."
}
],
"lastModified": "2026-08-17T06:18:09.253",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}