CVE-2026-89902
CVE CVE-2026-89902EUVD EUVD-2026-80502Published 2026-09-16T10:32:01.000ZLast changed 2026-09-16T14:39:50.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.110; patch: 7.2.5; 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 <76395109a051b53860faaec96522ef08ae9e8e27; patch: 0; 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 <c4357ebeee63cb8da1446fc936573a34e68b0f71; 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 <ff40e597d5d98c0c45a4d09df8177202fac9520e; 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 <a1cb727fa27c2d9c7859729cd90db7bc0f46957f; patch: 7.3-rc2; 6d4cc40fb5f58147defc6c0e9d86e6232fe31616 <72ce4b24676e8b3b75376c4c559dd81c1ac52d5a; patch: 6.6.157; patch: 6.18.51; 6.3
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.