CVE-2026-89902 (GCVE-0-2026-89902)
Vulnerability from cvelistv5 – Published: 2026-09-16 10:32 – Updated: 2026-10-19 08:54| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
6d4cc40fb5f58147defc6c0e9d86e6232fe31616 , < ff40e597d5d98c0c45a4d09df8177202fac9520e
(git)
Affected: 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 , < a1cb727fa27c2d9c7859729cd90db7bc0f46957f (git) Affected: 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 , < 76395109a051b53860faaec96522ef08ae9e8e27 (git) Affected: 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 , < c4357ebeee63cb8da1446fc936573a34e68b0f71 (git) Affected: 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 , < 72ce4b24676e8b3b75376c4c559dd81c1ac52d5a (git) |
guessed | |
| Linux | Linux |
Affected:
6.3
Unaffected: 0 , < 6.3 (semver) Unaffected: 6.6.157 , ≤ 6.6.* (semver) Unaffected: 6.12.110 , ≤ 6.12.* (semver) Unaffected: 6.18.51 , ≤ 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": [
"arch/loongarch/kernel/kprobes.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ff40e597d5d98c0c45a4d09df8177202fac9520e",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "a1cb727fa27c2d9c7859729cd90db7bc0f46957f",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "76395109a051b53860faaec96522ef08ae9e8e27",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "c4357ebeee63cb8da1446fc936573a34e68b0f71",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "72ce4b24676e8b3b75376c4c559dd81c1ac52d5a",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/loongarch/kernel/kprobes.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.3"
},
{
"lessThan": "6.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.51",
"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": "6.6.157",
"versionStartIncluding": "6.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.110",
"versionStartIncluding": "6.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.51",
"versionStartIncluding": "6.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.5",
"versionStartIncluding": "6.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "6.3",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Avoid preempt count underflow without probe\n\nLoongArch uses break 11 for the breakpoint placed after an instruction\nthat Kprobes executes out of line. Since userspace can issue the same\nbreak instruction, do_bp() can reach kprobe_singlestep_handler() when\nthere is no current probe.\n\nThe handler actually returns false in this case, but it first calls\npreempt_enable_no_resched(). The corresponding preempt_disable() is done\nby kprobe_breakpoint_handler() on a real Kprobe hit, so it has not run\nhere. As a result, an ordinary userspace breakpoint (code 11) underflows\nthe current task\u0027s preempt count.\n\nThis also makes in_interrupt() return true until the task schedules. One\nvisible consequence is the socket cgroup attribution: cgroup_sk_alloc()\ntreats the allocation as interrupt context and assigns the socket to the\nroot cgroup. A socket opened from the SIGTRAP handler can then avoid a\nBPF_CGROUP_INET_SOCK_CREATE policy attached to the task\u0027s own cgroup.\n\nReturn as soon as kprobe_running() reports no active probe.\n\nThe same check has appeared in [PATCH v10 2/4] of the original LoongArch\nKprobes series, but was dropped before the feature reached mainline."
}
],
"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 - An unprivileged LoongArch process reaches do_bp() then kprobe_singlestep_handler() by executing break 11 (BRK_KPROBE_SSTEPBP). That is a local CPU exception path, not a network protocol, adjacent wireless/Bluetooth frame, or physical device interface.\nAC:L - With no kprobe running on the CPU (the normal case), break 11 always takes the unmatched preempt_enable_no_resched() path and underflows preempt_count. The attacker then calls socket() from their own SIGTRAP handler; no race or victim-controlled state is required.\nPR:L - do_bp() applies no capability or credential check before dispatching BRK_KPROBE_SSTEPBP. Any unprivileged local user who can run code can issue the instruction; init-namespace root and user-namespace capabilities are not required.\nUI:N - The attacker executes break 11 in their own process and, for the cgroup bypass, installs their own SIGTRAP handler that creates sockets. No other user must mount a filesystem, open a device, or otherwise cooperate.\nS:U - Preempt-count corruption and the resulting socket cgroup/BPF misattribution stay inside the host kernel\u0027s security authority. This is not a KVM/Xen guest-to-host escape or an IOMMU/DMA boundary bypass.\nC:H - cgroup_sk_alloc() treats the underflow as interrupt context and pins the new socket to the root cgroup, so BPF_CGROUP_INET_SOCK_CREATE and later cgroup bind/connect/egress programs on the task\u0027s cgroup do not run. In a container or Cilium-style deployment this bypasses network isolation and can expose protected services.\nI:H - Root-cgroup attribution skips the container\u0027s cgroup BPF socket and traffic hooks for that socket, fully bypassing that access-control policy, while the unmatched preempt_enable corrupts kernel preempt_count used for interrupt and atomic accounting.\nA:H - The underflow makes in_atomic() true, so the next schedule (default SIGTRAP teardown or any blocking syscall) hits BUG: scheduling while atomic and can panic the host, especially with panic_on_warn. mem_cgroup_sk_alloc() also skips container socket charging, allowing host memory exhaustion."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T08:54:35.100Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/ff40e597d5d98c0c45a4d09df8177202fac9520e"
},
{
"url": "https://git.kernel.org/stable/c/a1cb727fa27c2d9c7859729cd90db7bc0f46957f"
},
{
"url": "https://git.kernel.org/stable/c/76395109a051b53860faaec96522ef08ae9e8e27"
},
{
"url": "https://git.kernel.org/stable/c/c4357ebeee63cb8da1446fc936573a34e68b0f71"
},
{
"url": "https://git.kernel.org/stable/c/72ce4b24676e8b3b75376c4c559dd81c1ac52d5a"
}
],
"title": "LoongArch: Avoid preempt count underflow without probe",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-89902",
"datePublished": "2026-09-16T10:32:01.655Z",
"dateReserved": "2026-09-11T19:38:34.774Z",
"dateUpdated": "2026-10-19T08:54:35.100Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-89902",
"date": "2026-11-09",
"epss": "0.00175",
"percentile": "0.0704"
},
"microsoft_vex": {
"current_release_date": "2026-10-21T18:42:36.000Z",
"cve": "CVE-2026-89902",
"id": "msrc_CVE-2026-89902",
"initial_release_date": "2026-09-17T01:12:18.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "2",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "LoongArch: Avoid preempt count underflow without probe",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-89902.json",
"version": "6"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/loongarch/kernel/kprobes.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ff40e597d5d98c0c45a4d09df8177202fac9520e",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "a1cb727fa27c2d9c7859729cd90db7bc0f46957f",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "76395109a051b53860faaec96522ef08ae9e8e27",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "c4357ebeee63cb8da1446fc936573a34e68b0f71",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
},
{
"lessThan": "72ce4b24676e8b3b75376c4c559dd81c1ac52d5a",
"status": "affected",
"version": "6d4cc40fb5f58147defc6c0e9d86e6232fe31616",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/loongarch/kernel/kprobes.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.3"
},
{
"lessThan": "6.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.51",
"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\nLoongArch: Avoid preempt count underflow without probe\n\nLoongArch uses break 11 for the breakpoint placed after an instruction\nthat Kprobes executes out of line. Since userspace can issue the same\nbreak instruction, do_bp() can reach kprobe_singlestep_handler() when\nthere is no current probe.\n\nThe handler actually returns false in this case, but it first calls\npreempt_enable_no_resched(). The corresponding preempt_disable() is done\nby kprobe_breakpoint_handler() on a real Kprobe hit, so it has not run\nhere. As a result, an ordinary userspace breakpoint (code 11) underflows\nthe current task\u0027s preempt count.\n\nThis also makes in_interrupt() return true until the task schedules. One\nvisible consequence is the socket cgroup attribution: cgroup_sk_alloc()\ntreats the allocation as interrupt context and assigns the socket to the\nroot cgroup. A socket opened from the SIGTRAP handler can then avoid a\nBPF_CGROUP_INET_SOCK_CREATE policy attached to the task\u0027s own cgroup.\n\nReturn as soon as kprobe_running() reports no active probe.\n\nThe same check has appeared in [PATCH v10 2/4] of the original LoongArch\nKprobes series, but was dropped before the feature reached mainline."
}
],
"id": "CVE-2026-89902",
"lastModified": "2026-10-19T09:18:35.527",
"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-09-16T11:16:59.143",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/72ce4b24676e8b3b75376c4c559dd81c1ac52d5a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/76395109a051b53860faaec96522ef08ae9e8e27"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a1cb727fa27c2d9c7859729cd90db7bc0f46957f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c4357ebeee63cb8da1446fc936573a34e68b0f71"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ff40e597d5d98c0c45a4d09df8177202fac9520e"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-07T11:26:50+00:00",
"cve": "CVE-2026-89902",
"id": "CVE-2026-89902",
"initial_release_date": "2026-09-16T00:00:00+00:00",
"product_status:known_not_affected": "203",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: LoongArch: Avoid preempt count underflow without probe",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89902.json",
"version": "3"
}
}
}
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.
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…
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.
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.