From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-46010][MODERATE REGULAR] rxrpc: Fix error handling in rxgk_extract_token() Date: Wed, 27 May 2026 17:01:15 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-46010 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: 3 X-AL-KERNEL-ActionableScore-Lower: 2 X-AL-KERNEL-Commit: 293095ef618818852bac5488c1bc223935e2ca17 List-Id: CVE: CVE-2026-46010 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: rxrpc: Fix error handling in rxgk_extract_token() Commit: 293095ef618818852bac5488c1bc223935e2ca17 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=293095ef618818852bac5488c1bc223935e2ca17 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46010 Analysis date: Wed, 27 May 2026 17:01:15 -0400 ActionableScore: 3 ActionableScore lower bound: 2 Actionable bucket: Borderline, manual review recommended Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46010 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46010 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: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-46010 MODERATE CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-703;CWE-755;CWE-252;*CWE-20;Other CVSS 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.9';DESCR 'rxgk_extract_token() can continue token processing after rxgk_decrypt_skb() returns ENOMEM instead of returning the allocation failure immediately. This may send a failed decrypt state into default_decode_ticket() and cause incorrect RXGK connection handling or denial of service under memory pressure. For the CVSS the PR:N is used because no local privileges are required on the victim when the RXRPC RXGK endpoint is reachable. The issue is network reachable in deployments using RXRPC RXGK, but reliable triggering depends on allocation failure or memory pressure and is therefore high complexity. Impact is availability only, with no supported memory corruption, information disclosure, or privilege escalation primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3) SKIP CVE-2026-46010 SKIP The Fixes patch not applied yet, so unlikely that actual: 64863f4ca4945bdb62ce2b30823f39ea9fe95415 YES NO NO unknown MAYBE SIMPLEFIX ERRORPATH LINUS INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ActionableScoreLower=2 1. ActionableScore * Conservative score: 2 * Paranoid score: 3 * Final recommended bucket: **Borderline, manual review recommended**:: 2. Signal breakdown * Remote reachable / network-triggerable: +2. The affected code is in RXRPC/RXGK token extraction and can be reached by network traffic when RXRPC/RXGK is exposed. * Availability impact plausible: +1. Continuing after `rxgk_decrypt_skb()` returns `ENOMEM` can cause incorrect token handling or connection failure under memory pressure. * Hard or unreliable condition: -1. Reliable triggering depends on making the decrypt path return `ENOMEM`, which generally requires memory pressure or allocation failure timing. * Rare/configuration-dependent exposure: -1. RXRPC/RXGK is not a broadly exposed default Internet service and requires a deployment using this authentication path. * No memory corruption signal. The patch fixes error handling after allocation failure and does not show UAF, OOB access, arbitrary write, information disclosure, or LPE. 3. Reachability analysis A remote peer can reach `rxgk_extract_token()` only if the victim uses RXRPC/RXGK. No local privileges are required on the victim once that endpoint is reachable. Practical exploitation is difficult because the interesting path requires `rxgk_decrypt_skb()` to fail with `ENOMEM`. Namespaces and containers do not materially change the remote trigger model. 4. Severity interpretation This behaves like a network-reachable but high-complexity DoS/error-handling issue. It is not an Important-class memory corruption bug. The realistic impact is availability disruption or incorrect connection handling under memory pressure. There is no demonstrated confidentiality or integrity impact. 5. One-sentence report phrase `rxgk_extract_token()` could continue token decoding after `rxgk_decrypt_skb()` returned `ENOMEM`, allowing malformed RXGK connection handling or DoS under memory pressure on exposed RXRPC/RXGK endpoints. 6. Manual review recommendation MANUAL CHECK RECOMMENDED. The issue is network reachable in RXRPC/RXGK deployments, but exploitation depends on `ENOMEM` and no memory corruption or privilege escalation primitive is shown. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: rxrpc: Fix error handling in rxgk_extract_token() Commit: 293095ef618818852bac5488c1bc223935e2ca17 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=293095ef618818852bac5488c1bc223935e2ca17 Commit description: Fix a missing bit of error handling in rxgk_extract_token(): in the event that rxgk_decrypt_skb() returns -ENOMEM, it should just return that rather than continuing on (for anything else, it generates an abort). Fixes: 64863f4 ("rxrpc: Fix unhandled errors in rxgk_verify_packet_integrity()") Closes: https://sashiko.dev/#/patchset/20260422161438.2593376-4-dhowells@redhat.com Signed-off-by: David Howells cc: Marc Dionne cc: Jeffrey Altman cc: Simon Horman cc: linux-afs@lists.infradead.org cc: stable@kernel.org Link: https://patch.msgid.link/20260423200909.3049438-4-dhowells@redhat.com Signed-off-by: Jakub Kicinski Signed-off-by: Greg Kroah-Hartman Changed files: net/rxrpc/rxgk_app.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=293095ef618818852bac5488c1bc223935e2ca17 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46010 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46010 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:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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: 2 Paranoid ActionableScore: 3 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).