From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80878][IMPORTANT] afs: Fix leak of ungot volume [ Upstream Date: Fri, 04 Sep 2026 14:11:44 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-80878 X-AL-KERNEL-Priority: IMPORTANT X-AL-KERNEL-Severity: IMPORTANT X-AL-KERNEL-Base-Severity: IMPORTANT X-AL-KERNEL-KPANIC: YES X-AL-KERNEL-ActionableScore: 6 X-AL-KERNEL-ActionableScore-Lower: 5 X-AL-KERNEL-Commit: 9cabf1c86948793fbad09023bd2ec58c71b9c1d4 List-Id: CVE: CVE-2026-80878 Priority: IMPORTANT AL-KERNEL base severity: IMPORTANT KPANIC flag: YES Patch: afs: Fix leak of ungot volume [ Upstream Commit: 9cabf1c86948793fbad09023bd2ec58c71b9c1d4 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9cabf1c86948793fbad09023bd2ec58c71b9c1d4 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80878 Analysis date: Fri, 04 Sep 2026 14:11:44 -0400 ActionableScore: 6 ActionableScore lower bound: 5 Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80878 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80878 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: IMPORTANT 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-80878 IMPORTANT https://www.kernelcve.org/list/?q=CVE-2026-80878 CHECK WITH IMPACT FROM ORIG NN NONE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;*CWE-664;Other CVSS 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '8.1';DESCR 'afs_lookup_volume_rcu could return a volume pointer even when afs_try_get_volume failed, meaning the caller may receive a dying object without a valid reference. This is an RCU and refcount lifetime bug and can become a stale pointer or use after free candidate if later callback handling uses the returned volume as valid. For the CVSS the PR:N is used for the paranoid score because a malicious or compromised AFS server side endpoint may be able to influence callback processing without local privileges on the victim. The issue is network reachable only on systems using AFS and reachable AFS server callback paths, so exploitation is environment dependent and likely high complexity. Impact is at least denial of service via crash. In the worst still defensible case it may allow confidentiality or integrity impact due to UAF style memory lifetime corruption and should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 6) SKIP CVE-2026-80878 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 32222f09782f YES NO NO unknown MAYBE READ DISK SIMPLEFIX LEAK SKIP LINUS KPANIC INCREASED_TO_MODERATE7_FROM_LOW_BASED_ON_GUESSCVSS_AND_ACTIONABLESCOREHIGHER4 KPANIC INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHERTHAN5 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=6 ActionableScoreLower=5 PrimitiveClass=CLASS_B RealUAF=YES HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=NO ImportantCandidate=YES ManualReview=REQUIRED AutoDowngradeAllowed=NO 1. ActionableScore * Raw conservative score: 5 * Conservative score: 5 * Raw paranoid score: 6 * Paranoid score: 6 * Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**:: No floor or cap changed the score. The lower score keeps only the directly established lifetime bug, network callback reachability in an AFS deployment, and crash risk. The paranoid score adds one technically defensible point for an escaped active structured stale object used in callback processing. 2. Signal breakdown Conservative positive signals: * +2 Real UAF / lifetime violation: `afs_try_get_volume()` failed, meaning the volume is dying or cannot be safely referenced, but without `volume = NULL` the function could still return that pointer to the caller. * +2 Remote reachable / network callback path: the bug is in AFS callback handling and can plausibly be influenced by an AFS server side endpoint on systems using AFS. * +1 Reliable kernel crash / strong DoS: returning a dying volume without a valid reference can lead to stale object use and kernel fault. Paranoid additional signal: * +1 Structured stale-object exploitation leverage: the stale pointer is an active `afs_volume` object returned to caller-side callback logic, not merely a fixed stale buffer or immediate cleanup-only dereference. This leaves meaningful unresolved lifetime leverage, although controlled reclaim is not shown. Non-awarded signals: * +0 Controlled reclaim: not demonstrated. * +0 Arbitrary or directed kernel write: not demonstrated. * +0 Confidentiality or integrity: not awarded as separate ActionableScore signals because no concrete leak, write primitive, or protected-object modification is shown. * +0 Concrete repeated release/refcount: not awarded. The patch shows a failed get and stale return, but not a visible first put followed by a second put on the exact same dangling reference. * +0 Weak LPE: not separately awarded because the unresolved exploitation concern is already captured by structured stale-object leverage in the paranoid score. * +0 Extra availability: not awarded because crash/DoS is already counted once. * +0 Race penalty: not applied. The lifetime state is RCU/refcount related, but the supplied evidence does not prove a materially hard, one-shot, externally uncontrollable race. * +0 Host-admin penalty: not applied because host-admin-equivalent triggering is not positively established. Repeated release/refcount checklist: * First release can end lifetime: not established in supplied patch. * Exact same reference survives after first release: not established. * Second operation mutates lifetime/refcount: not established. * Concrete repeated release/refcount +1 awarded: no. * Paranoid repeated-refcount leverage +1 awarded: no. * FLOOR 5 applied: no. Score naturally reaches 5 conservatively. 3. Reachability analysis The likely attacker model is a malicious or compromised AFS server side endpoint interacting with an AFS client that has already mounted or otherwise uses the affected AFS volume. The vulnerable code is in `fs/afs/callback.c`, and the fixed function returns an `afs_volume` found under RCU callback-side lookup. This is not a generic Internet-wide network bug. It depends on AFS being configured and the callback path being reachable in that deployment. However, once such a deployment exists, the supplied context does not positively establish that host administrator privileges on the victim are required for the remote side to influence callback processing. HostAdminRequired is therefore UNKNOWN rather than YES or NO. NamespaceScopedPrivilege is NO because the issue is not presented as a namespace-scoped capability path. No special hardware is required. No sysctl or boot-only prerequisite is shown beyond using the AFS filesystem. Race repeatability is unresolved, but no concrete hard timing penalty is justified from the supplied evidence alone. 4. Primitive and severity interpretation The exact primitive is a returned stale lifetime object. `afs_lookup_volume_rcu()` may find a volume, fail to acquire a reference with `afs_try_get_volume()`, and still return the non-NULL pointer unless it is explicitly cleared. A failed try-get strongly implies the object is dying or otherwise unsafe to hand to callers as a valid referenced object. This is an active structured object lifetime bug, not fixed stale storage. It is not merely a memory leak. The stale object can escape the lookup helper and be consumed by callback handling code as if a valid reference had been acquired. The class is CLASS_B. The demonstrated consequence is at least kernel crash / DoS from stale object use. The speculative consequence is stronger exploitation via UAF-style lifetime corruption, but controlled reclaim, arbitrary read/write, callback hijack, or proven privilege escalation are not established by the patch. ImportantCandidate is YES because this is a real RCU/refcount lifetime bug in a network filesystem callback path, and the stale active object escapes to caller logic. AutoDowngradeAllowed is NO because automatically closing it as ordinary Moderate would discard unresolved exploitation leverage from a real active-object lifetime primitive. Likely operational severity is actionable Moderate with strong manual-review value. It is not proven Important from the supplied patch alone, but it should not be automatically downgraded. 5. One-sentence report phrase AFS callback volume lookup could return a dying afs_volume without a valid reference after afs_try_get_volume() failed, creating a network filesystem lifetime bug that can cause kernel crash and requires manual review for possible UAF exploitation leverage. 6. Manual review recommendation MANUAL CHECK REQUIRED Reason: real RCU/refcount lifetime violation in an AFS callback path, active structured object returned without a valid reference, and unresolved exploitation leverage beyond crash. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: afs: Fix leak of ungot volume [ Upstream Commit: 9cabf1c86948793fbad09023bd2ec58c71b9c1d4 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9cabf1c86948793fbad09023bd2ec58c71b9c1d4 Changed files: fs/afs/callback.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=9cabf1c86948793fbad09023bd2ec58c71b9c1d4 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80878 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80878 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:H The Best / paranoid CVSS vector: AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H The Best / paranoid CVSS score: 8.1 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: 5 Paranoid ActionableScore: 6 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: IMPORTANT KPANIC detected for this report: YES Published priority for this report (same as in Subject): IMPORTANT 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).