CVE Professor
›
Back
CVE-2026-98163

CVE-2026-98163 — Linux Linux Kernel (tüm Sürümler) — CWE-362 · CWE-416

HIGH CVSS 7.8 NVD

CVE-2026-98163 is a HIGH severity security vulnerability (CWE-362, CWE-416) (CVSS 7.8/10) affecting Linux Linux Kernel (tüm Sürümler). Technical vector analysis shows that an attacker can exploit this flaw via local access (AV:L) with low-privileged access (PR:L) with zero user interaction (UI:N), resulting in complete compromise of system confidentiality and integrity (C:H/I:H).

📄 Official NVD / MITRE Original Record Text

In the Linux kernel, the following vulnerability has been resolved: cgroup: Avoid iteration of dying tasks with zero refcount The commit 260fbcb92bbea ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()") extended the lifetime of tasks on the dying_tasks list. The iterators have provision to go through dying_tasks because of dying threadgroup leaders or explicit CSS_TASK_ITER_WITH_DEAD, however, it was expected that such tasks can obtain a new reference (that is possible before cgroup_task_release()/put_task_struct_rcu_user()). The tasks after cgroup_task_release() and before cgroup_task_free() are subject to race when they may or may not have ->usage count > 0. The race window is between css_task_iter_next() invocations when css_set_lock is released and we may arrive at a new ->task_pos. The iterator should not attempt to resurrect tasks whose ->usage count dropped to zero. (When that happens, __put_task_struct_rcu_cb() is already imminent and the returned task_struct would could be used after free.) As for the fix, we cannot simply check the signal->live count of a task on the dying list because that won't distinguish regular zombies waiting to be reaped from RCU remnant tasks that are going to be free'd. Therefore add an extra check to rule out ->usage==0 tasks from any iteration. The repeat: loop in css_task_iter_advance() doesn't consider ->usage count, so add a new loop to css_task_iter_next() to skip de-used tasks on the dying_list. Rough illustration of the possible race R (reader of cgroup.procs) T (thread) L (group leader) --------------------------------- -------------------------------- -------------------------------- L exits, signal->live > 0 cgroup_task_dead(L) css_set_skip_task_iters() // skips only cset->tasks list_add_tail(&L->cg_list, &cset->dying_tasks) css_task_iter_next() take css_set_lock css_task_iter_advance() leader && signal->live != 0 => it->task_pos = &L->cg_list release css_set_lock T exits --signal->live == 0 cgroup_task_dead(T) // css_set_lock release_task(T) cgroup_task_release(T) release_task(L) // zap_leader cgroup_task_release(L) put_task_struct_rcu_user(L) ...RCU... put_task_struct(L) L->usage = 0 /* L still on dying_tasks */ ...RCU... __put_task_struct(L) css_task_iter_next() // another iteration take css_set_lock it->task_pos = &L->cg_list get_task_struct(L) => addition on 0 drop css_set_lock cgroup_task_free(L) css_set_skip_task_iters() // dying skip comes too late free_task(L) cgroup_procs_show() task_pid_vnr(L)

Published 26.09.2026
ISO Date 2026-09-26
CVSS Version v3.1
Source NVD
CVSS v3.1 Vector Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector Local AV:L
Attack Complexity Low AC:L
Privileges Req. Low PR:L
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality High C:H
Integrity High I:H
Availability High A:H
AI Security Analysis & Remediation
🤖 Generating Deep AI Security Analysis…
Analyzing CVSS vector & CWE weakness structure…

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-98163
CVSS 7.8/10 · HIGH · 26.09.2026
CWE: CWE-362, CWE-416
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 WHAT IS THIS VULNERABILITY?
Summary: In the Linux kernel, the following vulnerability has been resolved:

cgroup: Avoid iteration of dying tasks with zero refcount

The commit 260fbcb92bbea ("cgroup: Move dying_tasks cleanup from
cgroup_task_release() to cgroup_task_free()") extended the lifetime of
tasks on the dying_tasks list. The iterators have provision to go through dying_tasks because of
dying threadgroup leaders or explici…
Affected: linux:linux_kernel, linux:linux_kernel

⚡ ATTACK CHAIN
Local/physical access | low-privilege account | no user interaction | low complexity.

🌍 REAL WORLD IMPACT
All confidential data readable/stealable; data can be modified or deleted; service can be completely taken down.

🛡️ REMEDIATION
→ Apply vendor security update for linux:linux_kernel.
→ Add WAF rule, create IDS alert for anomalous traffic.

⚠️ URGENCY
⚠️ Planned maintenance (2 weeks).

────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]

Target Reconnaissance Queries (FOFA & Shodan)

FOFA Query

app="linux linux_kernel"
CVSS Score
7.8 / 10 · CVSS HIGH
Weakness Types (CWE)
CWE-362 CWE-416
Affected Products (2)
linux:linux_kernel (tüm sürümler) linux:linux_kernel (7.3)
References & Advisories (2)
Related CVEs
8.8
CVE-2026-126962
open62541 Subscription Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote at
8.1
CVE-2026-113425
When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-
8.1
CVE-2026-121810
Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3. A remote, una
8.1
CVE-2026-123633
When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client reque
8.1
CVE-2026-123634
This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name inclu
7.5
CVE-2026-95823
tcp_pkt_linearize() in subsys/net/ip/tcp.c is used by th_get() whenever a received TCP header is not contiguou