CVE-2026-97936
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix memory corruption from the histogram stacktrace modifier
parse_field() sets HIST_FIELD_FL_STACKTRACE from the ".stacktrace" modifier before it looks the field name up, and nothing afterwards checks that the name resolved to a field which holds a stacktrace. create_hist_field() picks HIST_FIELD_FN_STACK on the strength of the field pointer alone, which reads a __data_loc word from the record and follows its low 16 bits as an offset into the same record. event_hist_trigger() takes the first word there as an entry count and copies that many longs into a 31 entry array:
Leer descripción completaMostrar menos
Neither end of that copy is bounded, and the count is whatever the event holds at the offset, so any field will do:
The timer interrupt landed on the rbtree the copy had already run over. No debug options are needed for this; KASAN reports the same write as an out-of-bounds read of 13835058055416381440 bytes.
Documentation/trace/histogram.rst already states the rule, "must be a long[] type", so enforce it once the name has been resolved. Names which resolve to no field at all, "hitcount.stacktrace" and the common_* pseudo-fields, are refused for the same reason: they hold no stacktrace to read.
Detalles técnicos trazas, registros y código del informe original
n_entries = *stack; memcpy(entries, ++stack, n_entries * sizeof(unsigned long)); # cd /sys/kernel/tracing/events/sched/sched_process_fork # echo 'hist:keys=parent_pid.stacktrace' > trigger # (true) BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:rb_insert_color+0x18/0x130 timerqueue_linked_add+0x7e/0xd0 enqueue_hrtimer+0x39/0xb0 __hrtimer_run_queues+0x10f/0x1f0 </IRQ> RIP: 0010:memcpy+0xc/0x30 event_hist_trigger+0x165/0x690
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.20%
- Percentil entre todas las CVEs puntuadas: 9
- 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).
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/55caaf25da2c2bb9b75307e4c868726cb954b1d6
- https://git.kernel.org/stable/c/57bfc2a17954d173d2a4182f3b582ffbb23aff64
- https://git.kernel.org/stable/c/98da3379cdee343f671dac89b9afbd8b071f2591
- https://git.kernel.org/stable/c/a5e70ba87ca8ebc79b4e63de302d03b0625fe153
- https://git.kernel.org/stable/c/e183b84968d4a6ea476d806ea97668405aa56880
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-97936",
"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": "cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314",
"lessThan": "98da3379cdee343f671dac89b9afbd8b071f2591",
"versionType": "git"
},
{
"status": "affected",
"version": "cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314",
"lessThan": "e183b84968d4a6ea476d806ea97668405aa56880",
"versionType": "git"
},
{
"status": "affected",
"version": "cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314",
"lessThan": "57bfc2a17954d173d2a4182f3b582ffbb23aff64",
"versionType": "git"
},
{
"status": "affected",
"version": "cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314",
"lessThan": "55caaf25da2c2bb9b75307e4c868726cb954b1d6",
"versionType": "git"
},
{
"status": "affected",
"version": "cc5fc8bfc961eeb99b7e8dffbeff7a3f6995d314",
"lessThan": "a5e70ba87ca8ebc79b4e63de302d03b0625fe153",
"versionType": "git"
}
],
"programFiles": [
"kernel/trace/trace_events_hist.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.3"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.3",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.53",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.7",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"kernel/trace/trace_events_hist.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-25T11:17:20.963",
"references": [
{
"url": "https://git.kernel.org/stable/c/55caaf25da2c2bb9b75307e4c868726cb954b1d6",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/57bfc2a17954d173d2a4182f3b582ffbb23aff64",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/98da3379cdee343f671dac89b9afbd8b071f2591",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/a5e70ba87ca8ebc79b4e63de302d03b0625fe153",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/e183b84968d4a6ea476d806ea97668405aa56880",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix memory corruption from the histogram stacktrace modifier\n\nparse_field() sets HIST_FIELD_FL_STACKTRACE from the \".stacktrace\"\nmodifier before it looks the field name up, and nothing afterwards\nchecks that the name resolved to a field which holds a stacktrace.\ncreate_hist_field() picks HIST_FIELD_FN_STACK on the strength of the\nfield pointer alone, which reads a __data_loc word from the record and\nfollows its low 16 bits as an offset into the same record.\nevent_hist_trigger() takes the first word there as an entry count and\ncopies that many longs into a 31 entry array:\n\n\tn_entries = *stack;\n\tmemcpy(entries, ++stack, n_entries * sizeof(unsigned long));\n\nNeither end of that copy is bounded, and the count is whatever the event\nholds at the offset, so any field will do:\n\n # cd /sys/kernel/tracing/events/sched/sched_process_fork\n # echo 'hist:keys=parent_pid.stacktrace' > trigger\n # (true)\n\n BUG: kernel NULL pointer dereference, address: 0000000000000008\n RIP: 0010:rb_insert_color+0x18/0x130\n timerqueue_linked_add+0x7e/0xd0\n enqueue_hrtimer+0x39/0xb0\n __hrtimer_run_queues+0x10f/0x1f0\n </IRQ>\n RIP: 0010:memcpy+0xc/0x30\n event_hist_trigger+0x165/0x690\n\nThe timer interrupt landed on the rbtree the copy had already run over.\nNo debug options are needed for this; KASAN reports the same write as an\nout-of-bounds read of 13835058055416381440 bytes.\n\nDocumentation/trace/histogram.rst already states the rule, \"must be a\nlong[] type\", so enforce it once the name has been resolved. Names which\nresolve to no field at all, \"hitcount.stacktrace\" and the common_*\npseudo-fields, are refused for the same reason: they hold no stacktrace\nto read."
}
],
"lastModified": "2026-10-03T11:18:19.273",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}