From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98071][MODERATE REGULAR] net/rds: clear cp_flags bits individually in rds_conn_path_reset() [ Upstream Date: Fri, 25 Sep 2026 14:00:45 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98071 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: ed3ee0ac4aafda50c2f4381eb973beefeb7879ac List-Id: CVE: CVE-2026-98071 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: net/rds: clear cp_flags bits individually in rds_conn_path_reset() [ Upstream Commit: ed3ee0ac4aafda50c2f4381eb973beefeb7879ac Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ed3ee0ac4aafda50c2f4381eb973beefeb7879ac Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98071 Analysis date: Fri, 25 Sep 2026 14:00:45 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98071 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98071 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: MODERATE REGULAR Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-98071 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98071 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H';CWE-362;CWE-667;CWE-662;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.9';DESCR 'A race in the RDS connection reset path occurs because rds_conn_path_reset uses a plain cp_flags store while send and transport completion paths update the same word with atomic bit operations. A reset racing with an atomic read modify write can silently discard a connection state update and can break teardown, flow control, or reconnect processing. The realistic impact is denial of service through a stalled or unusable RDS connection, with no concrete UAF, OOB access, information leak, or arbitrary write primitive shown by the affected code. For the CVSS the PR:N value is used in the paranoid score because a reachable RDS peer may influence disconnect, completion, and reconnect timing without an account on the target, although reliable triggering depends on an active RDS workload and a difficult race window. RDS is normally deployed on trusted cluster or storage networks rather than the public Internet, so practical remote exposure is generally network adjacent and configuration dependent.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) SKIP CVE-2026-98071 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE INIT RACE LINUS PACKET INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * No floor or cap applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Availability impact. A lost update can leave RDS flow-control, shutdown, or reconnect state inconsistent and make a connection stall or remain unusable. * No corruption bonus. The patch establishes a data race and discarded flag update, not UAF, OOB access, arbitrary write, refcount corruption, or object replacement. * No remote-reachability bonus. An RDS peer may influence transport timing, but the supplied evidence does not establish that remote traffic alone controls the complete reset-versus-update sequence. * No local-unprivileged bonus. AF_RDS may be usable below host admin in some configurations, but complete below-admin reachability of the shutdown race is not established. * No race penalty. The evidence does not establish that the timing window is narrow, one-shot, or difficult to repeat. * No extra crash point. A kernel panic or host-wide fatal fault is not demonstrated. * No C/I, LPE, structured-object, lifetime, or security-boundary points. Discarding an ordinary connection-state update does not independently establish those consequences. 3. Reachability analysis The race requires `rds_conn_path_reset()` to overlap an atomic update from the send or transport-completion path. An active RDS connection and a shutdown or reset event are prerequisites. A remote RDS peer may affect completion, disconnect, backpressure, and reconnect timing, but the supplied context does not prove a remote-only trigger. The complete privilege boundary is unresolved. The evidence does not establish host-admin-equivalent privilege, but it also does not prove that an ordinary user can drive every required stage. No evidence establishes that the complete operation is available through attacker-created user or network namespaces. No special hardware is required, although an enabled and active RDS deployment is necessary. Race repeatability is unresolved, so no timing penalty is applied. 4. Primitive and severity interpretation The exact primitive is a non-atomic whole-word store racing with atomic read-modify-write bit operations. The resulting primitive is a lost flag update and inconsistent RDS connection state. This is neither fixed stale storage nor an active structured-object UAF. No object is shown to outlive its lifetime, and no repeated release or refcount mutation exists. The demonstrated consequence is connection-level availability failure involving flow control, teardown, or reconnect processing. Host-wide crash, memory corruption, disclosure, privilege escalation, and a useful post-race exploitation primitive remain unsupported. `PrimitiveClass=CLASS_C` is appropriate because the defect primarily creates invalid state and potential DoS. `ImportantCandidate=NO` and `AutoDowngradeAllowed=YES` follow because no unresolved kernel-corruption, lifetime, ownership, or security-boundary primitive is established. Operational severity is ordinary Moderate or Low-like, depending on whether the affected RDS connection is service-critical. 5. One-sentence report phrase A race between the RDS connection reset and atomic flag updates can silently discard connection state and disrupt flow control, teardown, or reconnection, but no memory-corruption or privilege-escalation primitive is established. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Review the surrounding shutdown and transport call paths to determine whether an untrusted RDS peer can reliably trigger the complete race and whether losing these flags can cause effects broader than connection-level DoS. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: net/rds: clear cp_flags bits individually in rds_conn_path_reset() [ Upstream Commit: ed3ee0ac4aafda50c2f4381eb973beefeb7879ac Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ed3ee0ac4aafda50c2f4381eb973beefeb7879ac Changed files: net/rds/connection.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ed3ee0ac4aafda50c2f4381eb973beefeb7879ac ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98071 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98071 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H The Best / paranoid CVSS score: 5.9 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 1 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).