CVE-2026-74472
In the Linux kernel, the following vulnerability has been resolved:
ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()
ublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into ub->dev_info and then fixes up the fields the driver owns, but misses ->state and ->ublksrv_pid.
A device added with ->state = UBLK_S_DEV_LIVE passes the "->state != UBLK_S_DEV_DEAD" test that ublk_stop_dev_unlocked() uses as its proxy for "a disk is attached", while ->ub_disk is still NULL, so DEL_DEV right after ADD_DEV oopses in del_gendisk().
Leer descripción completaMostrar menos
UBLK_S_DEV_QUIESCED plus UBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev(). A poisoned ->state also gets START_USER_RECOVERY and the char device read/write path onto a device that was never started, and wedges START_DEV at -EEXIST. A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an unrelated task as the ublk server.
Reset both after the memcpy(), as ublk_detach_disk() does. Userspace only ever reads these back, so correcting them silently breaks nothing.
ADD_DEV has copied ->state in unsanitized since ublk was merged, but back then it was harmless: the gendisk was allocated during ADD_DEV, and both teardown and the START_DEV -EEXIST check keyed off disk_live() rather than ->state. The oops became reachable once the disk allocation moved to START_DEV and those checks switched to ->state.
CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.21%
- Percentil entre todas las CVEs puntuadas: 11
- 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).
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
- https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124
- https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9
- https://git.kernel.org/stable/c/787c944502e7e63d20a9201bada77e0dd924f458
- https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea
- https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f
- https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-74472",
"cveTags": [],
"metrics": {},
"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": "6d9e6dfdf3b207701471f364121c67eefb000682",
"lessThan": "787c944502e7e63d20a9201bada77e0dd924f458",
"versionType": "git"
},
{
"status": "affected",
"version": "6d9e6dfdf3b207701471f364121c67eefb000682",
"lessThan": "ee41b00858ca65b4428e99efe39a4277c1f043d2",
"versionType": "git"
},
{
"status": "affected",
"version": "6d9e6dfdf3b207701471f364121c67eefb000682",
"lessThan": "b67ce16b26ad0f14cfd6071013840aa95f823bea",
"versionType": "git"
},
{
"status": "affected",
"version": "6d9e6dfdf3b207701471f364121c67eefb000682",
"lessThan": "205feb72e5beb3140e4e1403b6cff30cf739bab9",
"versionType": "git"
},
{
"status": "affected",
"version": "6d9e6dfdf3b207701471f364121c67eefb000682",
"lessThan": "127033b79383a3e78361d7e971588aa8849f5124",
"versionType": "git"
},
{
"status": "affected",
"version": "6d9e6dfdf3b207701471f364121c67eefb000682",
"lessThan": "e65848e4ce352bac9e3465099354c8b8f845391f",
"versionType": "git"
}
],
"programFiles": [
"drivers/block/ublk_drv.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.0"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.1.183",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.151",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.103",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.44",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.1.8",
"versionType": "semver",
"lessThanOrEqual": "7.1.*"
},
{
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/block/ublk_drv.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-08-15T13:17:51.953",
"references": [
{
"url": "https://git.kernel.org/stable/c/127033b79383a3e78361d7e971588aa8849f5124",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/205feb72e5beb3140e4e1403b6cff30cf739bab9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/787c944502e7e63d20a9201bada77e0dd924f458",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/b67ce16b26ad0f14cfd6071013840aa95f823bea",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e65848e4ce352bac9e3465099354c8b8f845391f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ee41b00858ca65b4428e99efe39a4277c1f043d2",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev()\n\nublk_ctrl_add_dev() memcpy()s the userspace ublksrv_ctrl_dev_info into\nub->dev_info and then fixes up the fields the driver owns, but misses\n->state and ->ublksrv_pid.\n\nA device added with ->state = UBLK_S_DEV_LIVE passes the\n\"->state != UBLK_S_DEV_DEAD\" test that ublk_stop_dev_unlocked() uses as its\nproxy for \"a disk is attached\", while ->ub_disk is still NULL, so DEL_DEV\nright after ADD_DEV oopses in del_gendisk(). UBLK_S_DEV_QUIESCED plus\nUBLK_F_USER_RECOVERY dies one step earlier, in ublk_force_abort_dev(). A\npoisoned ->state also gets START_USER_RECOVERY and the char device\nread/write path onto a device that was never started, and wedges START_DEV\nat -EEXIST. A poisoned ->ublksrv_pid just makes GET_DEV_INFO report an\nunrelated task as the ublk server.\n\nReset both after the memcpy(), as ublk_detach_disk() does. Userspace only\never reads these back, so correcting them silently breaks nothing.\n\nADD_DEV has copied ->state in unsanitized since ublk was merged, but back\nthen it was harmless: the gendisk was allocated during ADD_DEV, and both\nteardown and the START_DEV -EEXIST check keyed off disk_live() rather than\n->state. The oops became reachable once the disk allocation moved to\nSTART_DEV and those checks switched to ->state."
}
],
"lastModified": "2026-08-19T17:21:04.490",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}