- 7.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Avoid preempt count underflow without probe LoongArch uses break 11 for the breakpoint placed after an instruction that Kprobes executes out of line. Since userspace can issue the same break instruction, do_bp() can reach kprobe_singlestep_handler() when there is no current probe. The handler actually returns false in this case, but it first calls preempt_enable_no_resched(). The corresponding preempt_disable() is done by kprobe_breakpoint_handler() on a real Kprobe hit, so it has not run here. As a result, an ordinary userspace breakpoint (code 11) underflows the current task's preempt count. This also makes in_interrupt() return true until the task schedules. One visible consequence is the socket cgroup attribution: cgroup_sk_alloc() treats the allocation as interrupt context and assigns the socket to the root cgroup. A socket opened from the SIGTRAP handler can then avoid a BPF_CGROUP_INET_SOCK_CREATE policy attached to the task's own cgroup. Return as soon as kprobe_running() reports no active probe. The same check has appeared in [PATCH v10 2/4] of the original LoongArch Kprobes series, but was dropped before the feature reached mainline.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 33 days later
· 33 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 – < ff40e597d5d98c0c45a4d09df8177202fac9520e
- affected 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 – < a1cb727fa27c2d9c7859729cd90db7bc0f46957f
- affected 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 – < 76395109a051b53860faaec96522ef08ae9e8e27
- affected 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 – < c4357ebeee63cb8da1446fc936573a34e68b0f71
- affected 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 – < 72ce4b24676e8b3b75376c4c559dd81c1ac52d5a
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
5
- https://git.kernel.org/stable/c/ff40e597d5d98c0c45a4d09df8177202fac9520e (opens in a new tab)
- https://git.kernel.org/stable/c/a1cb727fa27c2d9c7859729cd90db7bc0f46957f (opens in a new tab)
- https://git.kernel.org/stable/c/76395109a051b53860faaec96522ef08ae9e8e27 (opens in a new tab)
- https://git.kernel.org/stable/c/c4357ebeee63cb8da1446fc936573a34e68b0f71 (opens in a new tab)
- https://git.kernel.org/stable/c/72ce4b24676e8b3b75376c4c559dd81c1ac52d5a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80502 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89902)Record last updated .