CVE-2026-89796 (GCVE-0-2026-89796)
Vulnerability from cvelistv5 – Published: 2026-09-16 10:30 – Updated: 2026-10-19 08:52
VLAI
EPSS
VEX
Title
mm/damon/core: avoid infinite kdamond_merge_regions() internal loop
Summary
In the Linux kernel, the following vulnerability has been resolved:
mm/damon/core: avoid infinite kdamond_merge_regions() internal loop
Patch series "mm/damon: unurgent fixes for infinite loop, NULL de-ref and
races", v1.1.
Sashiko found a few issues in DAMON that could cause infinite loop, NULL
dereference and monitoring results degradation. The first two sounds
scary but the infinite loop happens only under unreasonable user setup.
The NULL dereference is only in a unit test. Monitoring results
degradation is trivial since it is only best-effort, and those happens
from only unlikely races. Still those are bugs that better to fix if
possible. Fix those.
This patch (of 6):
Due to online parameter update like events, the number of DAMON regions
could be higher than the user-set upper limit. kdamond_merge_regions()
repeats merge regions until the number meets the limit, while doubling the
merge threshold up to the theoretical maximum threshold. It is tried only
up to the theoretical maximum threshold because even the aggressive
merging can fail from reducing the number of regions under the
user-defined upper limit. For example, there could be many user-defined
non-contiguous regions that cannot be merged.
The threshold based loop break condition is evaluated by comparing the
threshold for the next merging try against the theoretical maximum
threshold. If max_thres is larger than UINT_MAX / 2, doubling the
threshold could make it overflow, and bypass the loop break condition. In
the case, if the number of regions cannot be reduced under the upper limit
like explained above, the loop will run infinitely.
Prevent the case by doing the break condition check before doubling the
threshold. Also, prevent the threshold exceeding the maximum threshold,
as it could overflow and apply the wrong merge threshold.
This issue is unlikely to occur in real world, since having the max_thres
higher than UINT_MAX / 2 require unrealistically large aggregation
intervals compared to the sampling interval. Also, it requires an
unrealistically large number of uncontiguous regions setup. Nonetheless,
the consequence is bad and the fix is simple.
The issue was discovered [1] by Sashiko.
Severity
No CVSS data available.
Assigner
References
7 references
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1e865019cef354a5f0314491b4b4fc9f9a613642 , < 407da1dd7f48e5ba22ceb8834f6923390632d025
(git)
Affected: d7eda72e59bbf3ed592db7ff0fd8c246c73149a8 , < 65edd8b3a88278c9f8e5c7d8c15d4f296ce35078 (git) Affected: 11078e2d11465518a9e85096bd28f8cd5fa1ea41 , < 5b0953f86d65855dc901050f40bbe6da0475d198 (git) Affected: 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 , < 769c16699c89811386eb003c8fd9dcb8d405b316 (git) Affected: 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 , < 50a7a5aec1aa43efc297fd4377c1cbdc7d15620d (git) Affected: 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 , < 8a96a06e04d210845be5d9581c0e9e338947e8f8 (git) Affected: 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 , < 123e4619ab6c8ab1c4cb1d7a58311a2af13929cd (git) Affected: f2bd3184b6aeca6a497394b558337246e09fc02d (git) Affected: 5.15.164 , < 5.15.222 (semver) Affected: 6.1.101 , < 6.1.189 (semver) Affected: 6.6.41 , < 6.6.158 (semver) Affected: 6.9.10 , < 6.10 (semver) |
guessed | |
| Linux | Linux |
Affected:
6.10
Unaffected: 0 , < 6.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.5 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"mm/damon/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "407da1dd7f48e5ba22ceb8834f6923390632d025",
"status": "affected",
"version": "1e865019cef354a5f0314491b4b4fc9f9a613642",
"versionType": "git"
},
{
"lessThan": "65edd8b3a88278c9f8e5c7d8c15d4f296ce35078",
"status": "affected",
"version": "d7eda72e59bbf3ed592db7ff0fd8c246c73149a8",
"versionType": "git"
},
{
"lessThan": "5b0953f86d65855dc901050f40bbe6da0475d198",
"status": "affected",
"version": "11078e2d11465518a9e85096bd28f8cd5fa1ea41",
"versionType": "git"
},
{
"lessThan": "769c16699c89811386eb003c8fd9dcb8d405b316",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"lessThan": "50a7a5aec1aa43efc297fd4377c1cbdc7d15620d",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"lessThan": "8a96a06e04d210845be5d9581c0e9e338947e8f8",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"lessThan": "123e4619ab6c8ab1c4cb1d7a58311a2af13929cd",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"status": "affected",
"version": "f2bd3184b6aeca6a497394b558337246e09fc02d",
"versionType": "git"
},
{
"lessThan": "5.15.222",
"status": "affected",
"version": "5.15.164",
"versionType": "semver"
},
{
"lessThan": "6.1.189",
"status": "affected",
"version": "6.1.101",
"versionType": "semver"
},
{
"lessThan": "6.6.158",
"status": "affected",
"version": "6.6.41",
"versionType": "semver"
},
{
"lessThan": "6.10",
"status": "affected",
"version": "6.9.10",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"mm/damon/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.10"
},
{
"lessThan": "6.10",
"status": "unaffected",
"version": "0",
"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": "7.2.*",
"status": "unaffected",
"version": "7.2.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.222",
"versionStartIncluding": "5.15.164",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.189",
"versionStartIncluding": "6.1.101",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.158",
"versionStartIncluding": "6.6.41",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.111",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.53",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.5",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "6.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.9.10",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: avoid infinite kdamond_merge_regions() internal loop\n\nPatch series \"mm/damon: unurgent fixes for infinite loop, NULL de-ref and\nraces\", v1.1.\n\nSashiko found a few issues in DAMON that could cause infinite loop, NULL\ndereference and monitoring results degradation. The first two sounds\nscary but the infinite loop happens only under unreasonable user setup. \nThe NULL dereference is only in a unit test. Monitoring results\ndegradation is trivial since it is only best-effort, and those happens\nfrom only unlikely races. Still those are bugs that better to fix if\npossible. Fix those.\n\n\nThis patch (of 6):\n\nDue to online parameter update like events, the number of DAMON regions\ncould be higher than the user-set upper limit. kdamond_merge_regions()\nrepeats merge regions until the number meets the limit, while doubling the\nmerge threshold up to the theoretical maximum threshold. It is tried only\nup to the theoretical maximum threshold because even the aggressive\nmerging can fail from reducing the number of regions under the\nuser-defined upper limit. For example, there could be many user-defined\nnon-contiguous regions that cannot be merged.\n\nThe threshold based loop break condition is evaluated by comparing the\nthreshold for the next merging try against the theoretical maximum\nthreshold. If max_thres is larger than UINT_MAX / 2, doubling the\nthreshold could make it overflow, and bypass the loop break condition. In\nthe case, if the number of regions cannot be reduced under the upper limit\nlike explained above, the loop will run infinitely.\n\nPrevent the case by doing the break condition check before doubling the\nthreshold. Also, prevent the threshold exceeding the maximum threshold,\nas it could overflow and apply the wrong merge threshold.\n\nThis issue is unlikely to occur in real world, since having the max_thres\nhigher than UINT_MAX / 2 require unrealistically large aggregation\nintervals compared to the sampling interval. Also, it requires an\nunrealistically large number of uncontiguous regions setup. Nonetheless,\nthe consequence is bad and the fix is simple.\n\nThe issue was discovered [1] by Sashiko."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T08:52:51.066Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/407da1dd7f48e5ba22ceb8834f6923390632d025"
},
{
"url": "https://git.kernel.org/stable/c/65edd8b3a88278c9f8e5c7d8c15d4f296ce35078"
},
{
"url": "https://git.kernel.org/stable/c/5b0953f86d65855dc901050f40bbe6da0475d198"
},
{
"url": "https://git.kernel.org/stable/c/769c16699c89811386eb003c8fd9dcb8d405b316"
},
{
"url": "https://git.kernel.org/stable/c/50a7a5aec1aa43efc297fd4377c1cbdc7d15620d"
},
{
"url": "https://git.kernel.org/stable/c/8a96a06e04d210845be5d9581c0e9e338947e8f8"
},
{
"url": "https://git.kernel.org/stable/c/123e4619ab6c8ab1c4cb1d7a58311a2af13929cd"
}
],
"title": "mm/damon/core: avoid infinite kdamond_merge_regions() internal loop",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-89796",
"datePublished": "2026-09-16T10:30:27.478Z",
"dateReserved": "2026-09-11T19:38:34.767Z",
"dateUpdated": "2026-10-19T08:52:51.066Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-89796",
"date": "2026-11-09",
"epss": "0.00231",
"percentile": "0.14076"
},
"microsoft_vex": {
"current_release_date": "2026-10-22T01:11:06.000Z",
"cve": "CVE-2026-89796",
"id": "msrc_CVE-2026-89796",
"initial_release_date": "2026-09-17T01:11:09.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "3",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "mm/damon/core: avoid infinite kdamond_merge_regions() internal loop",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-89796.json",
"version": "7"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"mm/damon/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "407da1dd7f48e5ba22ceb8834f6923390632d025",
"status": "affected",
"version": "1e865019cef354a5f0314491b4b4fc9f9a613642",
"versionType": "git"
},
{
"lessThan": "65edd8b3a88278c9f8e5c7d8c15d4f296ce35078",
"status": "affected",
"version": "d7eda72e59bbf3ed592db7ff0fd8c246c73149a8",
"versionType": "git"
},
{
"lessThan": "5b0953f86d65855dc901050f40bbe6da0475d198",
"status": "affected",
"version": "11078e2d11465518a9e85096bd28f8cd5fa1ea41",
"versionType": "git"
},
{
"lessThan": "769c16699c89811386eb003c8fd9dcb8d405b316",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"lessThan": "50a7a5aec1aa43efc297fd4377c1cbdc7d15620d",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"lessThan": "8a96a06e04d210845be5d9581c0e9e338947e8f8",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"lessThan": "123e4619ab6c8ab1c4cb1d7a58311a2af13929cd",
"status": "affected",
"version": "310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6",
"versionType": "git"
},
{
"status": "affected",
"version": "f2bd3184b6aeca6a497394b558337246e09fc02d",
"versionType": "git"
},
{
"lessThan": "5.15.222",
"status": "affected",
"version": "5.15.164",
"versionType": "semver"
},
{
"lessThan": "6.1.189",
"status": "affected",
"version": "6.1.101",
"versionType": "semver"
},
{
"lessThan": "6.6.158",
"status": "affected",
"version": "6.6.41",
"versionType": "semver"
},
{
"lessThan": "6.10",
"status": "affected",
"version": "6.9.10",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"mm/damon/core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.10"
},
{
"lessThan": "6.10",
"status": "unaffected",
"version": "0",
"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": "7.2.*",
"status": "unaffected",
"version": "7.2.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"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\nmm/damon/core: avoid infinite kdamond_merge_regions() internal loop\n\nPatch series \"mm/damon: unurgent fixes for infinite loop, NULL de-ref and\nraces\", v1.1.\n\nSashiko found a few issues in DAMON that could cause infinite loop, NULL\ndereference and monitoring results degradation. The first two sounds\nscary but the infinite loop happens only under unreasonable user setup. \nThe NULL dereference is only in a unit test. Monitoring results\ndegradation is trivial since it is only best-effort, and those happens\nfrom only unlikely races. Still those are bugs that better to fix if\npossible. Fix those.\n\n\nThis patch (of 6):\n\nDue to online parameter update like events, the number of DAMON regions\ncould be higher than the user-set upper limit. kdamond_merge_regions()\nrepeats merge regions until the number meets the limit, while doubling the\nmerge threshold up to the theoretical maximum threshold. It is tried only\nup to the theoretical maximum threshold because even the aggressive\nmerging can fail from reducing the number of regions under the\nuser-defined upper limit. For example, there could be many user-defined\nnon-contiguous regions that cannot be merged.\n\nThe threshold based loop break condition is evaluated by comparing the\nthreshold for the next merging try against the theoretical maximum\nthreshold. If max_thres is larger than UINT_MAX / 2, doubling the\nthreshold could make it overflow, and bypass the loop break condition. In\nthe case, if the number of regions cannot be reduced under the upper limit\nlike explained above, the loop will run infinitely.\n\nPrevent the case by doing the break condition check before doubling the\nthreshold. Also, prevent the threshold exceeding the maximum threshold,\nas it could overflow and apply the wrong merge threshold.\n\nThis issue is unlikely to occur in real world, since having the max_thres\nhigher than UINT_MAX / 2 require unrealistically large aggregation\nintervals compared to the sampling interval. Also, it requires an\nunrealistically large number of uncontiguous regions setup. Nonetheless,\nthe consequence is bad and the fix is simple.\n\nThe issue was discovered [1] by Sashiko."
}
],
"id": "CVE-2026-89796",
"lastModified": "2026-10-19T09:18:23.370",
"metrics": {},
"published": "2026-09-16T11:16:44.423",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/123e4619ab6c8ab1c4cb1d7a58311a2af13929cd"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/407da1dd7f48e5ba22ceb8834f6923390632d025"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/50a7a5aec1aa43efc297fd4377c1cbdc7d15620d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5b0953f86d65855dc901050f40bbe6da0475d198"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/65edd8b3a88278c9f8e5c7d8c15d4f296ce35078"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/769c16699c89811386eb003c8fd9dcb8d405b316"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8a96a06e04d210845be5d9581c0e9e338947e8f8"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-07T11:26:31+00:00",
"cve": "CVE-2026-89796",
"id": "CVE-2026-89796",
"initial_release_date": "2026-09-16T00:00:00+00:00",
"product_status:known_affected": "110",
"product_status:known_not_affected": "93",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: mm/damon/core: avoid infinite kdamond_merge_regions() internal loop",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89796.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.