CVE-2026-74702
In the Linux kernel, the following vulnerability has been resolved:
vhost-scsi: reject feature changes after endpoint
vhost_scsi_setup_vq_cmds() runs from VHOST_SCSI_SET_ENDPOINT and allocates each command's protection scatterlist array (prot_sgl) according to the acknowledged VIRTIO_SCSI_F_T10_PI bit. The command pools are not rebuilt when VHOST_SET_FEATURES changes that bit later.
Although virtio feature bits must not change after feature negotiation, vhost_scsi_set_features() currently accepts such a request after the endpoint is active and updates acked_features. Enabling T10-PI after endpoint setup therefore leaves prot_sgl NULL while the I/O path follows the new feature bit.
Leer descripción completaMostrar menos
For a 129-page protection payload, vhost_scsi_mapal() passes the missing first chunk to sg_alloc_table_chained():
sg_pool_index() then hits:
The kernel reported the following call trace and register state:
VHOST_F_LOG_ALL is a vhost-specific runtime feature and remains the only exception.
Reject changes to any feature other than VHOST_F_LOG_ALL while the endpoint is active. This preserves the existing runtime log toggle while preventing feature-dependent command resources and data-path state from becoming inconsistent. Userspace must clear the endpoint before changing any other negotiated feature and set the endpoint up again afterward.
Detalles técnicos trazas, registros y código del informe original
sg_alloc_table_chained(table, 129, first_chunk=NULL,
nents_first_chunk=inline_sg_cnt)
BUG_ON(nents > SG_CHUNK_SIZE); /* 129 > 128 */
Call Trace:
<TASK>
? __sg_alloc_table+0x1d8/0x250
? __pfx_vhost_run_work_list+0x10/0x10 [vhost]
sg_alloc_table_chained+0x59/0xf0
? __pfx_sg_pool_alloc+0x10/0x10
? vhost_scsi_calc_sgls.constprop.0+0x43/0x60 [vhost_scsi]
vhost_scsi_handle_vq+0xf02/0x1700 [vhost_scsi]
? __pfx_vhost_scsi_handle_vq+0x10/0x10 [vhost_scsi]
vhost_scsi_handle_kick+0x37/0x50 [vhost_scsi]
vhost_run_work_list+0x8e/0xd0 [vhost]
vhost_task_fn+0xe1/0x210
ret_from_fork+0x348/0x540
</TASK>
RIP: 0010:0x4
CR2 = 0x4
RSP: 0018:ffffc90000dbf940 EFLAGS: 00010202
RAX: ffffffff82396810 RBX: ffff88811dc28b80 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000820 RDI: 0000000000000081CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Puntuación base: 8.8
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: 5/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
T1499.004Application or System Exploitationimpact80 % - Impacto secundario
T1561.002Disk Structure Wipeimpact70 %
Vulnerabilidad local (AV:L/PR:L) que causa BUG_ON() y null pointer dereference al cambiar features después de endpoint setup, permitiendo DoS por crash del kernel o corrupción de datos en vhost-scsi.
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-74702",
"cveTags": [],
"metrics": {
"cvssMetricV31": [
{
"type": "Secondary",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"cvssData": {
"scope": "CHANGED",
"version": "3.1",
"baseScore": 8.8,
"attackVector": "LOCAL",
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "HIGH",
"privilegesRequired": "LOW",
"confidentialityImpact": "HIGH"
},
"impactScore": 6,
"exploitabilityScore": 2
}
]
},
"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": "bf2d650391be508dd8b5e188b65ed32300cf3489",
"lessThan": "a06e4611d45518896fbff4f45d9581578b107e91",
"versionType": "git"
},
{
"status": "affected",
"version": "bf2d650391be508dd8b5e188b65ed32300cf3489",
"lessThan": "9a3eb77a612f9d158e4d27df43677a014e9cfa55",
"versionType": "git"
},
{
"status": "affected",
"version": "bf2d650391be508dd8b5e188b65ed32300cf3489",
"lessThan": "42bc45df5905e2b7dccb72adaf7730f66cfbe03f",
"versionType": "git"
}
],
"programFiles": [
"drivers/vhost/scsi.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.15"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.15",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.45",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.1.9",
"versionType": "semver",
"lessThanOrEqual": "7.1.*"
},
{
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/vhost/scsi.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-08-22T16:16:44.873",
"references": [
{
"url": "https://git.kernel.org/stable/c/42bc45df5905e2b7dccb72adaf7730f66cfbe03f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9a3eb77a612f9d158e4d27df43677a014e9cfa55",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a06e4611d45518896fbff4f45d9581578b107e91",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nvhost-scsi: reject feature changes after endpoint\n\nvhost_scsi_setup_vq_cmds() runs from VHOST_SCSI_SET_ENDPOINT and allocates\neach command's protection scatterlist array (prot_sgl) according to the\nacknowledged VIRTIO_SCSI_F_T10_PI bit. The command pools are not rebuilt\nwhen VHOST_SET_FEATURES changes that bit later.\n\nAlthough virtio feature bits must not change after feature negotiation,\nvhost_scsi_set_features() currently accepts such a request after the\nendpoint is active and updates acked_features. Enabling T10-PI after\nendpoint setup therefore leaves prot_sgl NULL while the I/O path follows\nthe new feature bit.\n\nFor a 129-page protection payload, vhost_scsi_mapal() passes the missing\nfirst chunk to sg_alloc_table_chained():\n\n sg_alloc_table_chained(table, 129, first_chunk=NULL,\n nents_first_chunk=inline_sg_cnt)\n\nsg_pool_index() then hits:\n\n BUG_ON(nents > SG_CHUNK_SIZE); /* 129 > 128 */\n\nThe kernel reported the following call trace and register state:\n\n Call Trace:\n <TASK>\n ? __sg_alloc_table+0x1d8/0x250\n ? __pfx_vhost_run_work_list+0x10/0x10 [vhost]\n sg_alloc_table_chained+0x59/0xf0\n ? __pfx_sg_pool_alloc+0x10/0x10\n ? vhost_scsi_calc_sgls.constprop.0+0x43/0x60 [vhost_scsi]\n vhost_scsi_handle_vq+0xf02/0x1700 [vhost_scsi]\n ? __pfx_vhost_scsi_handle_vq+0x10/0x10 [vhost_scsi]\n vhost_scsi_handle_kick+0x37/0x50 [vhost_scsi]\n vhost_run_work_list+0x8e/0xd0 [vhost]\n vhost_task_fn+0xe1/0x210\n ret_from_fork+0x348/0x540\n </TASK>\n\n RIP: 0010:0x4\n CR2 = 0x4\n RSP: 0018:ffffc90000dbf940 EFLAGS: 00010202\n RAX: ffffffff82396810 RBX: ffff88811dc28b80 RCX: 0000000000000000\n RDX: 0000000000000000 RSI: 0000000000000820 RDI: 0000000000000081\n\nVHOST_F_LOG_ALL is a vhost-specific runtime feature and remains the only\nexception.\n\nReject changes to any feature other than VHOST_F_LOG_ALL while the\nendpoint is active. This preserves the existing runtime log toggle while\npreventing feature-dependent command resources and data-path state from\nbecoming inconsistent. Userspace must clear the endpoint before changing\nany other negotiated feature and set the endpoint up again afterward."
}
],
"lastModified": "2026-08-25T06:18:54.117",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}