CVE-2026-98993 (GCVE-0-2026-98993)
Vulnerability from cvelistv5 – Published: 2026-10-23 12:20 – Updated: 2026-10-24 14:09
VLAI
EPSS
VEX
Title
namespace: don't inherit MNT_UMOUNT in clone_mnt()
Summary
In the Linux kernel, the following vulnerability has been resolved:
namespace: don't inherit MNT_UMOUNT in clone_mnt()
MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has
taken out of its namespace. It's never cleared. __detach_mounts()
unhooks a mount that carries it instead of unmounting it.
disconnect_mount() lets an unmounted child stay attached only if its
parent carries it. propagate_umount() takes it as the sign that a mount
is going to be unmounted when it decides what else can be unmounted,
where a chain of locked mounts ends and where a for reparenting an
overmount.
clone_mnt() copies the flags of the source and only masks
MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was
lazily unmounted but is kept alive by a file descriptor can still be
copied when its root is an nsfs or pidfs file because may_copy_tree()
accepts those before checking whether the source is mounted at all:
mount --bind /proc/self/ns/net /tmp/x
exec 3< /tmp/x
umount -l /tmp/x
mount --bind /proc/self/fd/3 /tmp/y
The mount on /tmp/y is attached to the caller's namespace with
MNT_UMOUNT already set and every copy of it inherits the flag again.
That causes a number of bugs:
- Unlink its mountpoint from a mount namespace where it isn't one.
__detach_mounts() takes it for a mount that was unmounted earlier,
unhooks it from its parent and drops the reference the namespace
holds on it. It stays in the namespace with one reference too few
and as its own parent, so it can't be unmounted through the file
descriptor anymore and the namespace never finds it again. When the
namespace goes away it's leaked and points to a freed struct
mnt_namespace that may_change_propagation() and anon_ns_root() read
on the next propagation change or mount_setattr() through the file
descriptor.
- Make it shared and unmount a peer. trace_transfers() follows the
flag from the peer into it and strips it from its peer group.
- Let a propagated umount reach it. gather_candidates() marks it with
T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the
mark is never cleared and every later propagated umount skips it. If
it's the parent of a locked mount handle_locked() takes it as the
cutoff and commits the locked child that should have stayed and
disconnect_mount() leaves that child attached to it, unmounted under
a mounted parent, which is what disconnect_mount() exists to
prevent. When the namespace goes away umount_tree() visits the child
a second time. And once __detach_mounts() has made it its own parent
reparent() never finds the end of the chain of unmounted parents.
A clone is a new mount that has never been unmounted. Add MNT_UMOUNT
to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when
umount_tree() reaches a mount that already has it set.
Severity
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
590ce4bcbfb4e0462a720a4ad901e84416080bba , < 99698cfa34e493fc091219056aae446fe9442a96
(git)
Affected: 590ce4bcbfb4e0462a720a4ad901e84416080bba , < c26c1a91ad2881a194f7af543e0b57f0870006b2 (git) Affected: 590ce4bcbfb4e0462a720a4ad901e84416080bba , < eecc9cd0fc07dba3f7fb0b2f844b4029435a2f7b (git) Affected: 590ce4bcbfb4e0462a720a4ad901e84416080bba , < 5077b52e9e4d72da53c50251296b99cd416765a1 (git) Affected: 590ce4bcbfb4e0462a720a4ad901e84416080bba , < e2c6d326216642011da318b9edfd5d57ebd5a56f (git) Affected: 7052e71b2d085f76800115d4a212dcaf82b86262 (git) Affected: 4.0.2 , < 4.1 (semver) |
guessed | |
| Linux | Linux |
Affected:
4.1
Unaffected: 0 , < 4.1 (semver) Unaffected: 6.6.160 , ≤ 6.6.* (semver) Unaffected: 6.12.114 , ≤ 6.12.* (semver) Unaffected: 6.18.57 , ≤ 6.18.* (semver) Unaffected: 7.2.11 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/namespace.c",
"include/linux/mount.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "99698cfa34e493fc091219056aae446fe9442a96",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "c26c1a91ad2881a194f7af543e0b57f0870006b2",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "eecc9cd0fc07dba3f7fb0b2f844b4029435a2f7b",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "5077b52e9e4d72da53c50251296b99cd416765a1",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "e2c6d326216642011da318b9edfd5d57ebd5a56f",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"status": "affected",
"version": "7052e71b2d085f76800115d4a212dcaf82b86262",
"versionType": "git"
},
{
"lessThan": "4.1",
"status": "affected",
"version": "4.0.2",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/namespace.c",
"include/linux/mount.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.1"
},
{
"lessThan": "4.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.114",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.57",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.11",
"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": "6.6.160",
"versionStartIncluding": "4.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.114",
"versionStartIncluding": "4.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.57",
"versionStartIncluding": "4.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.11",
"versionStartIncluding": "4.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "4.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "4.0.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnamespace: don\u0027t inherit MNT_UMOUNT in clone_mnt()\n\nMNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has\ntaken out of its namespace. It\u0027s never cleared. __detach_mounts()\nunhooks a mount that carries it instead of unmounting it.\n\ndisconnect_mount() lets an unmounted child stay attached only if its\nparent carries it. propagate_umount() takes it as the sign that a mount\nis going to be unmounted when it decides what else can be unmounted,\nwhere a chain of locked mounts ends and where a for reparenting an\novermount.\n\nclone_mnt() copies the flags of the source and only masks\nMNT_INTERNAL_FLAGS which doesn\u0027t include MNT_UMOUNT. A mount that was\nlazily unmounted but is kept alive by a file descriptor can still be\ncopied when its root is an nsfs or pidfs file because may_copy_tree()\naccepts those before checking whether the source is mounted at all:\n\n mount --bind /proc/self/ns/net /tmp/x\n exec 3\u003c /tmp/x\n umount -l /tmp/x\n mount --bind /proc/self/fd/3 /tmp/y\n\nThe mount on /tmp/y is attached to the caller\u0027s namespace with\nMNT_UMOUNT already set and every copy of it inherits the flag again.\n\nThat causes a number of bugs:\n\n- Unlink its mountpoint from a mount namespace where it isn\u0027t one.\n __detach_mounts() takes it for a mount that was unmounted earlier,\n unhooks it from its parent and drops the reference the namespace\n holds on it. It stays in the namespace with one reference too few\n and as its own parent, so it can\u0027t be unmounted through the file\n descriptor anymore and the namespace never finds it again. When the\n namespace goes away it\u0027s leaked and points to a freed struct\n mnt_namespace that may_change_propagation() and anon_ns_root() read\n on the next propagation change or mount_setattr() through the file\n descriptor.\n\n- Make it shared and unmount a peer. trace_transfers() follows the\n flag from the peer into it and strips it from its peer group.\n\n- Let a propagated umount reach it. gather_candidates() marks it with\n T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the\n mark is never cleared and every later propagated umount skips it. If\n it\u0027s the parent of a locked mount handle_locked() takes it as the\n cutoff and commits the locked child that should have stayed and\n disconnect_mount() leaves that child attached to it, unmounted under\n a mounted parent, which is what disconnect_mount() exists to\n prevent. When the namespace goes away umount_tree() visits the child\n a second time. And once __detach_mounts() has made it its own parent\n reparent() never finds the end of the chain of unmounted parents.\n\nA clone is a new mount that has never been unmounted. Add MNT_UMOUNT\nto MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when\numount_tree() reaches a mount that already has it set."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - mount(2) reaches path_mount()-\u003edo_loopback()-\u003e__do_loopback()-\u003eclone_mnt(), which copies MNT_UMOUNT from an fd-pinned, lazily unmounted nsfs/pidfs mount; the causal operations are local syscalls.\nAC:L - The attacker can deterministically bind an nsfs/pidfs file, retain an fd, call umount2(MNT_DETACH), rebind /proc/self/fd/N, and unlink the mountpoint from an attacker-controlled sibling mount namespace; no uncontrollable race is required.\nPR:L - path_mount() and can_umount() use may_mount(), which checks CAP_SYS_ADMIN in the mount namespace\u0027s owning user namespace; an unprivileged user can obtain that capability with unshare(CLONE_NEWUSER|CLONE_NEWNS).\nUI:N - The attacker performs the namespace creation, bind mounts, lazy unmount, fd retention, and unlink operations without any victim action.\nS:U - clone_mnt() corrupts mount and mnt_namespace lifetime state within the same host kernel security authority; a resulting local kernel privilege escalation remains scope unchanged.\nC:H - __detach_mounts() leaves the fd-pinned mount\u0027s mnt_ns pointing to a freed struct mnt_namespace; may_change_propagation() dereferences its freed user_ns and anon_ns_root() reads freed namespace fields, creating an attacker-triggered kernel UAF.\nI:H - After the dangling mnt_ns passes may_change_propagation(), do_change_type() calls touch_mnt_namespace(), which writes ns-\u003eevent and operates on ns-\u003epoll through freed, reclaimable storage, supporting heap corruption and control-flow exploitation.\nA:H - reparent() can loop forever on the self-parented unmounted chain, umount_tree() can visit a child twice, and the dangling namespace accesses can fault, permitting a kernel hang or crash."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-24T14:09:54.039Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/99698cfa34e493fc091219056aae446fe9442a96"
},
{
"url": "https://git.kernel.org/stable/c/c26c1a91ad2881a194f7af543e0b57f0870006b2"
},
{
"url": "https://git.kernel.org/stable/c/eecc9cd0fc07dba3f7fb0b2f844b4029435a2f7b"
},
{
"url": "https://git.kernel.org/stable/c/5077b52e9e4d72da53c50251296b99cd416765a1"
},
{
"url": "https://git.kernel.org/stable/c/e2c6d326216642011da318b9edfd5d57ebd5a56f"
}
],
"title": "namespace: don\u0027t inherit MNT_UMOUNT in clone_mnt()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98993",
"datePublished": "2026-10-23T12:20:12.266Z",
"dateReserved": "2026-09-25T10:25:14.384Z",
"dateUpdated": "2026-10-24T14:09:54.039Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-98993",
"date": "2026-10-24",
"epss": "0.00209",
"percentile": "0.10484"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/namespace.c",
"include/linux/mount.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "99698cfa34e493fc091219056aae446fe9442a96",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "c26c1a91ad2881a194f7af543e0b57f0870006b2",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "eecc9cd0fc07dba3f7fb0b2f844b4029435a2f7b",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "5077b52e9e4d72da53c50251296b99cd416765a1",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"lessThan": "e2c6d326216642011da318b9edfd5d57ebd5a56f",
"status": "affected",
"version": "590ce4bcbfb4e0462a720a4ad901e84416080bba",
"versionType": "git"
},
{
"status": "affected",
"version": "7052e71b2d085f76800115d4a212dcaf82b86262",
"versionType": "git"
},
{
"lessThan": "4.1",
"status": "affected",
"version": "4.0.2",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/namespace.c",
"include/linux/mount.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.1"
},
{
"lessThan": "4.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.114",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.57",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.11",
"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\nnamespace: don\u0027t inherit MNT_UMOUNT in clone_mnt()\n\nMNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has\ntaken out of its namespace. It\u0027s never cleared. __detach_mounts()\nunhooks a mount that carries it instead of unmounting it.\n\ndisconnect_mount() lets an unmounted child stay attached only if its\nparent carries it. propagate_umount() takes it as the sign that a mount\nis going to be unmounted when it decides what else can be unmounted,\nwhere a chain of locked mounts ends and where a for reparenting an\novermount.\n\nclone_mnt() copies the flags of the source and only masks\nMNT_INTERNAL_FLAGS which doesn\u0027t include MNT_UMOUNT. A mount that was\nlazily unmounted but is kept alive by a file descriptor can still be\ncopied when its root is an nsfs or pidfs file because may_copy_tree()\naccepts those before checking whether the source is mounted at all:\n\n mount --bind /proc/self/ns/net /tmp/x\n exec 3\u003c /tmp/x\n umount -l /tmp/x\n mount --bind /proc/self/fd/3 /tmp/y\n\nThe mount on /tmp/y is attached to the caller\u0027s namespace with\nMNT_UMOUNT already set and every copy of it inherits the flag again.\n\nThat causes a number of bugs:\n\n- Unlink its mountpoint from a mount namespace where it isn\u0027t one.\n __detach_mounts() takes it for a mount that was unmounted earlier,\n unhooks it from its parent and drops the reference the namespace\n holds on it. It stays in the namespace with one reference too few\n and as its own parent, so it can\u0027t be unmounted through the file\n descriptor anymore and the namespace never finds it again. When the\n namespace goes away it\u0027s leaked and points to a freed struct\n mnt_namespace that may_change_propagation() and anon_ns_root() read\n on the next propagation change or mount_setattr() through the file\n descriptor.\n\n- Make it shared and unmount a peer. trace_transfers() follows the\n flag from the peer into it and strips it from its peer group.\n\n- Let a propagated umount reach it. gather_candidates() marks it with\n T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the\n mark is never cleared and every later propagated umount skips it. If\n it\u0027s the parent of a locked mount handle_locked() takes it as the\n cutoff and commits the locked child that should have stayed and\n disconnect_mount() leaves that child attached to it, unmounted under\n a mounted parent, which is what disconnect_mount() exists to\n prevent. When the namespace goes away umount_tree() visits the child\n a second time. And once __detach_mounts() has made it its own parent\n reparent() never finds the end of the chain of unmounted parents.\n\nA clone is a new mount that has never been unmounted. Add MNT_UMOUNT\nto MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when\numount_tree() reaches a mount that already has it set."
}
],
"id": "CVE-2026-98993",
"lastModified": "2026-10-24T14:16:51.270",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-10-23T13:17:21.410",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5077b52e9e4d72da53c50251296b99cd416765a1"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/99698cfa34e493fc091219056aae446fe9442a96"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c26c1a91ad2881a194f7af543e0b57f0870006b2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e2c6d326216642011da318b9edfd5d57ebd5a56f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/eecc9cd0fc07dba3f7fb0b2f844b4029435a2f7b"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
}
}
}
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
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.