CVE-2026-97420 (GCVE-0-2026-97420)
Vulnerability from cvelistv5 – Published: 2026-09-24 16:03 – Updated: 2026-10-03 10:58
VLAI
EPSS
VEX
Title
bpf: NUL-terminate replaced sysctl value
Summary
In the Linux kernel, the following vulnerability has been resolved:
bpf: NUL-terminate replaced sysctl value
When writing to sysctls, proc_sys_call_handler() guarantees that the
buffer passed to proc handlers is NUL-terminated. If
bpf_sysctl_set_new_value() replaces the pending sysctl value, it can
hand a replacement buffer directly to proc handlers. However, the
helper currently copies only buf_len bytes into that buffer without
appending a NUL terminator, leaving downstream parsers vulnerable to
out-of-bounds access.
Fix this by appending a '\0' after the replaced value to restore the
expected sysctl semantics. Since the helper already rejects buf_len
greater than PAGE_SIZE - 1, there is always room for the extra byte.
Reproduced in a QEMU x86_64 guest booted with KASAN while exercising
the sysctl replacement path with a cgroup/sysctl BPF program. The
reproducer targets `/proc/sys/net/core/flow_limit_cpu_bitmap`, fills
the original user write buffer with non-zero bytes, and overrides the
sysctl value so the replacement buffer lacks a terminating NUL. Under
that setup, the pre-fix kernel reported:
BUG: KASAN: slab-out-of-bounds in strnchrnul+0x72/0x90
Read of size 1 at addr ffff88800de57000 by task repro_patch3/66
CPU: 0 UID: 0 PID: 66 Comm: repro_patch3 Not tainted 7.1.0-rc3-00269-g8370ca1f87cc #6 PREEMPT(lazy)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x68/0xa0
print_report+0xcb/0x5e0
? __virt_addr_valid+0x21d/0x3f0
? strnchrnul+0x72/0x90
? strnchrnul+0x72/0x90
kasan_report+0xca/0x100
? strnchrnul+0x72/0x90
strnchrnul+0x72/0x90
bitmap_parse+0x37/0x2e0
flow_limit_cpu_sysctl+0xc6/0x840
? __pfx_flow_limit_cpu_sysctl+0x10/0x10
? __kvmalloc_node_noprof+0x5ba/0x870
proc_sys_call_handler+0x31d/0x480
? __pfx_proc_sys_call_handler+0x10/0x10
? selinux_file_permission+0x39f/0x500
? lock_is_held_type+0x9e/0x120
vfs_write+0x98e/0x1000
...
</TASK>
The buggy address is located 0 bytes to the right of
allocated 4096-byte region [ffff88800de56000, ffff88800de57000)
With this fix applied, rerunning the same sysctl-targeted path yields
no corresponding KASAN reports.
Severity
No CVSS data available.
Assigner
References
7 references
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
32927393dc1ccd60fb2bdc05b9e8e88753761469 , < bfcee1f79aaefa90679ad47690107fb7682724ec
(git)
Affected: 32927393dc1ccd60fb2bdc05b9e8e88753761469 , < c73e4a04eedc677fe91a736d7a5db45100adba5e (git) Affected: 32927393dc1ccd60fb2bdc05b9e8e88753761469 , < 36d3e9f62dc2beb9299d3bb6f589cb9e07f773fe (git) Affected: 32927393dc1ccd60fb2bdc05b9e8e88753761469 , < 31377675c3d75603d957c08e338a9ac27e9f6cd5 (git) Affected: 32927393dc1ccd60fb2bdc05b9e8e88753761469 , < 76c14b10f50eb0afcc76e244562fa2d8c661e224 (git) Affected: 32927393dc1ccd60fb2bdc05b9e8e88753761469 , < 3b2814dd842a565fcf9cc370156e1ba9eae16239 (git) Affected: 32927393dc1ccd60fb2bdc05b9e8e88753761469 , < a66e3b5bacf38d6ab29fa05a9754f7a114485605 (git) |
guessed | |
| Linux | Linux |
Affected:
5.8
Unaffected: 0 , < 5.8 (semver) Unaffected: 5.10.271 , ≤ 5.10.* (semver) Unaffected: 5.15.222 , ≤ 5.15.* (semver) Unaffected: 6.1.189 , ≤ 6.1.* (semver) Unaffected: 6.6.158 , ≤ 6.6.* (semver) Unaffected: 6.12.111 , ≤ 6.12.* (semver) Unaffected: 6.18.53 , ≤ 6.18.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/bpf/cgroup.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "bfcee1f79aaefa90679ad47690107fb7682724ec",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "c73e4a04eedc677fe91a736d7a5db45100adba5e",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "36d3e9f62dc2beb9299d3bb6f589cb9e07f773fe",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "31377675c3d75603d957c08e338a9ac27e9f6cd5",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "76c14b10f50eb0afcc76e244562fa2d8c661e224",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "3b2814dd842a565fcf9cc370156e1ba9eae16239",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "a66e3b5bacf38d6ab29fa05a9754f7a114485605",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"kernel/bpf/cgroup.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.8"
},
{
"lessThan": "5.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.271",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.222",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.189",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.53",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.271",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.222",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.189",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.158",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.111",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.53",
"versionStartIncluding": "5.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "5.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: NUL-terminate replaced sysctl value\n\nWhen writing to sysctls, proc_sys_call_handler() guarantees that the\nbuffer passed to proc handlers is NUL-terminated. If\nbpf_sysctl_set_new_value() replaces the pending sysctl value, it can\nhand a replacement buffer directly to proc handlers. However, the\nhelper currently copies only buf_len bytes into that buffer without\nappending a NUL terminator, leaving downstream parsers vulnerable to\nout-of-bounds access.\n\nFix this by appending a \u0027\\0\u0027 after the replaced value to restore the\nexpected sysctl semantics. Since the helper already rejects buf_len\ngreater than PAGE_SIZE - 1, there is always room for the extra byte.\n\nReproduced in a QEMU x86_64 guest booted with KASAN while exercising\nthe sysctl replacement path with a cgroup/sysctl BPF program. The\nreproducer targets `/proc/sys/net/core/flow_limit_cpu_bitmap`, fills\nthe original user write buffer with non-zero bytes, and overrides the\nsysctl value so the replacement buffer lacks a terminating NUL. Under\nthat setup, the pre-fix kernel reported:\n\n BUG: KASAN: slab-out-of-bounds in strnchrnul+0x72/0x90\n Read of size 1 at addr ffff88800de57000 by task repro_patch3/66\n CPU: 0 UID: 0 PID: 66 Comm: repro_patch3 Not tainted 7.1.0-rc3-00269-g8370ca1f87cc #6 PREEMPT(lazy)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x68/0xa0\n print_report+0xcb/0x5e0\n ? __virt_addr_valid+0x21d/0x3f0\n ? strnchrnul+0x72/0x90\n ? strnchrnul+0x72/0x90\n kasan_report+0xca/0x100\n ? strnchrnul+0x72/0x90\n strnchrnul+0x72/0x90\n bitmap_parse+0x37/0x2e0\n flow_limit_cpu_sysctl+0xc6/0x840\n ? __pfx_flow_limit_cpu_sysctl+0x10/0x10\n ? __kvmalloc_node_noprof+0x5ba/0x870\n proc_sys_call_handler+0x31d/0x480\n ? __pfx_proc_sys_call_handler+0x10/0x10\n ? selinux_file_permission+0x39f/0x500\n ? lock_is_held_type+0x9e/0x120\n vfs_write+0x98e/0x1000\n ...\n \u003c/TASK\u003e\n The buggy address is located 0 bytes to the right of\n allocated 4096-byte region [ffff88800de56000, ffff88800de57000)\nWith this fix applied, rerunning the same sysctl-targeted path yields\nno corresponding KASAN reports."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-03T10:58:12.202Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/bfcee1f79aaefa90679ad47690107fb7682724ec"
},
{
"url": "https://git.kernel.org/stable/c/c73e4a04eedc677fe91a736d7a5db45100adba5e"
},
{
"url": "https://git.kernel.org/stable/c/36d3e9f62dc2beb9299d3bb6f589cb9e07f773fe"
},
{
"url": "https://git.kernel.org/stable/c/31377675c3d75603d957c08e338a9ac27e9f6cd5"
},
{
"url": "https://git.kernel.org/stable/c/76c14b10f50eb0afcc76e244562fa2d8c661e224"
},
{
"url": "https://git.kernel.org/stable/c/3b2814dd842a565fcf9cc370156e1ba9eae16239"
},
{
"url": "https://git.kernel.org/stable/c/a66e3b5bacf38d6ab29fa05a9754f7a114485605"
}
],
"title": "bpf: NUL-terminate replaced sysctl value",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-97420",
"datePublished": "2026-09-24T16:03:30.084Z",
"dateReserved": "2026-09-24T14:53:16.868Z",
"dateUpdated": "2026-10-03T10:58:12.202Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-97420",
"date": "2026-11-15",
"epss": "0.00173",
"percentile": "0.06745"
},
"microsoft_vex": {
"current_release_date": "2026-10-22T01:11:52.000Z",
"cve": "CVE-2026-97420",
"id": "msrc_CVE-2026-97420",
"initial_release_date": "2026-09-27T23:42:31.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "1",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "bpf: NUL-terminate replaced sysctl value",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-97420.json",
"version": "4"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/bpf/cgroup.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "bfcee1f79aaefa90679ad47690107fb7682724ec",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "c73e4a04eedc677fe91a736d7a5db45100adba5e",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "36d3e9f62dc2beb9299d3bb6f589cb9e07f773fe",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "31377675c3d75603d957c08e338a9ac27e9f6cd5",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "76c14b10f50eb0afcc76e244562fa2d8c661e224",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "3b2814dd842a565fcf9cc370156e1ba9eae16239",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
},
{
"lessThan": "a66e3b5bacf38d6ab29fa05a9754f7a114485605",
"status": "affected",
"version": "32927393dc1ccd60fb2bdc05b9e8e88753761469",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"kernel/bpf/cgroup.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.8"
},
{
"lessThan": "5.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.271",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.222",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.189",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.53",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: NUL-terminate replaced sysctl value\n\nWhen writing to sysctls, proc_sys_call_handler() guarantees that the\nbuffer passed to proc handlers is NUL-terminated. If\nbpf_sysctl_set_new_value() replaces the pending sysctl value, it can\nhand a replacement buffer directly to proc handlers. However, the\nhelper currently copies only buf_len bytes into that buffer without\nappending a NUL terminator, leaving downstream parsers vulnerable to\nout-of-bounds access.\n\nFix this by appending a \u0027\\0\u0027 after the replaced value to restore the\nexpected sysctl semantics. Since the helper already rejects buf_len\ngreater than PAGE_SIZE - 1, there is always room for the extra byte.\n\nReproduced in a QEMU x86_64 guest booted with KASAN while exercising\nthe sysctl replacement path with a cgroup/sysctl BPF program. The\nreproducer targets `/proc/sys/net/core/flow_limit_cpu_bitmap`, fills\nthe original user write buffer with non-zero bytes, and overrides the\nsysctl value so the replacement buffer lacks a terminating NUL. Under\nthat setup, the pre-fix kernel reported:\n\n BUG: KASAN: slab-out-of-bounds in strnchrnul+0x72/0x90\n Read of size 1 at addr ffff88800de57000 by task repro_patch3/66\n CPU: 0 UID: 0 PID: 66 Comm: repro_patch3 Not tainted 7.1.0-rc3-00269-g8370ca1f87cc #6 PREEMPT(lazy)\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x68/0xa0\n print_report+0xcb/0x5e0\n ? __virt_addr_valid+0x21d/0x3f0\n ? strnchrnul+0x72/0x90\n ? strnchrnul+0x72/0x90\n kasan_report+0xca/0x100\n ? strnchrnul+0x72/0x90\n strnchrnul+0x72/0x90\n bitmap_parse+0x37/0x2e0\n flow_limit_cpu_sysctl+0xc6/0x840\n ? __pfx_flow_limit_cpu_sysctl+0x10/0x10\n ? __kvmalloc_node_noprof+0x5ba/0x870\n proc_sys_call_handler+0x31d/0x480\n ? __pfx_proc_sys_call_handler+0x10/0x10\n ? selinux_file_permission+0x39f/0x500\n ? lock_is_held_type+0x9e/0x120\n vfs_write+0x98e/0x1000\n ...\n \u003c/TASK\u003e\n The buggy address is located 0 bytes to the right of\n allocated 4096-byte region [ffff88800de56000, ffff88800de57000)\nWith this fix applied, rerunning the same sysctl-targeted path yields\nno corresponding KASAN reports."
}
],
"id": "CVE-2026-97420",
"lastModified": "2026-10-03T11:17:54.123",
"metrics": {},
"published": "2026-09-24T17:17:19.853",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/31377675c3d75603d957c08e338a9ac27e9f6cd5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/36d3e9f62dc2beb9299d3bb6f589cb9e07f773fe"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3b2814dd842a565fcf9cc370156e1ba9eae16239"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/76c14b10f50eb0afcc76e244562fa2d8c661e224"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a66e3b5bacf38d6ab29fa05a9754f7a114485605"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bfcee1f79aaefa90679ad47690107fb7682724ec"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c73e4a04eedc677fe91a736d7a5db45100adba5e"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-06T02:18:28+00:00",
"cve": "CVE-2026-97420",
"id": "CVE-2026-97420",
"initial_release_date": "2026-09-24T00:00:00+00:00",
"product_status:known_affected": "112",
"product_status:known_not_affected": "91",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: bpf: NUL-terminate replaced sysctl value",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97420.json",
"version": "3"
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.