From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98066][MODERATE 7.0] ALSA: caiaq: Fix potential double-free at error path [ Upstream Date: Fri, 25 Sep 2026 10:41:37 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98066 X-AL-KERNEL-Priority: MODERATE 7.0 X-AL-KERNEL-Severity: MODERATE 7.0 X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: YES X-AL-KERNEL-ActionableScore: 4 X-AL-KERNEL-ActionableScore-Lower: 3 X-AL-KERNEL-Commit: 2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8 List-Id: CVE: CVE-2026-98066 Priority: MODERATE 7.0 AL-KERNEL base severity: MODERATE KPANIC flag: YES Patch: ALSA: caiaq: Fix potential double-free at error path [ Upstream Commit: 2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98066 Analysis date: Fri, 25 Sep 2026 10:41:37 -0400 ActionableScore: 4 ActionableScore lower bound: 3 Actionable bucket: Borderline / 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-98066 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98066 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 7.0 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-98066 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98066 CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H';CWE-415;CWE-675;Other CVSS 'AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '6.4';DESCR 'A double-free can occur in the ALSA caiaq audio initialization error path because previously released URB or callback resources may remain referenced by non-NULL pointers and can be released again during later cleanup. Triggering requires a caiaq USB device or a suitable emulated USB device together with an initialization failure that reaches the affected cleanup sequence. For the CVSS the PR:N value is used because an attacker who can physically attach a crafted USB device does not need an authenticated local account or existing privileges on the target. The issue is not network reachable and the realistic attack vector is physical access to the USB interface. Impact is at least denial of service through kernel memory corruption and a kernel crash. In the paranoid case the double-free may permit broader confidentiality and integrity impact or kernel code execution if the freed allocation can be reclaimed and controlled, although a reliable privilege escalation path is not demonstrated.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / Strong Important candidate requiring manual review (with actual score 4) SKIP CVE-2026-98066 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE DANGER USB INIT ERRORPATH UAF HARDWARE LINUS KPANIC - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=4 ActionableScoreLower=3 PrimitiveClass=CLASS_B RealUAF=YES HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=NO ImportantCandidate=YES ManualReview=REQUIRED AutoDowngradeAllowed=NO 1. ActionableScore * Raw conservative score: 3 * Conservative score: 3 * Raw paranoid score: 4 * Paranoid score: 4 * No floor or cap changed either score. The physical and specialized USB-device prerequisite is a concrete reducing condition that prevents application of the normal repeated-release floor of 5. * Final recommended bucket: **Borderline / Strong Important candidate requiring manual review**:: 2. Signal breakdown Conservative signals: * +2 Real lifetime violation. Resources can be freed on the initialization error path while their addresses remain stored in `cdev`. * +1 Concrete repeated release. The same uncleared pointers can subsequently reach `snd_usb_caiaq_audio_free()` and be passed to `free_urbs()` or `kfree()` again. * +1 Reliable kernel-crash concern. A second URB release or `kfree()` can corrupt allocator or USB lifetime state and plausibly cause an Oops or panic. * +1 Device-mediated external influence. A matching physical or emulated USB peripheral initiates the driver probe and influences whether the affected initialization path is reached. * -2 Physical or specialized-device prerequisite. Reaching the path requires a caiaq-compatible USB device or suitable USB emulation and an initialization failure. Paranoid-only signal: * +1 Repeated-release post-lifetime mutation. The second `free_urbs()` or `kfree()` may modify allocator or lifetime state after the original allocation has already left its valid lifetime. Repeated-release findings: * The first `free_urbs()` and `kfree()` operations can end the relevant allocation lifetimes. * The exact pointers remain stored in `cdev` because the old error paths do not clear them. * A later destructor invocation can perform real second lifetime-mutating operations on those pointers. * Concrete repeated release/refcount +1 was awarded. * Paranoid repeated-release leverage +1 was awarded because the second free can operate on already-freed storage rather than merely reading it. * FLOOR 5 was not applied because physical or specialized USB access is a supported strong reducing condition. Not awarded: * Controlled reclaim or attacker-shaped replacement contents are not demonstrated. * Arbitrary or directed kernel read/write is not demonstrated. * Structured stale-object leverage was not separately awarded because the established stale operation is the same repeated free already scored. * Weak LPE was not separately awarded for the repeated-release fact. * Confidentiality and integrity points were not awarded merely because allocator corruption could theoretically become exploitable. * No additional Availability point was awarded because it would duplicate the same potential kernel crash. * Remote network reachability is not established. * No timing penalty was applied because this is an ordered error and cleanup sequence, not a demonstrated hard race. 3. Reachability analysis A caiaq-compatible physical USB device or suitable USB-device emulation must cause the driver to probe and then encounter an audio-resource initialization failure. USB hotplug can normally invoke a matching driver without an authenticated local account, but the supplied code does not establish that an attacker can reliably force the required allocation failure on every target. Therefore the complete privilege boundary is unresolved and `HostAdminRequired=UNKNOWN`. The operation is part of USB device probing rather than a user-namespace capability path. No attacker-created namespace provides the complete trigger, so `NamespaceScopedPrivilege=NO`. The driver must be built or loaded and the target must accept the device. No race is required. The special USB-device and failure-path requirements materially limit practical reachability. 4. Primitive and severity interpretation The exact primitive is a potential double-free of URB resources or `data_cb_info`. This is a real lifetime violation because an initial free can end the allocation lifetime while the same non-NULL pointer remains reachable for later cleanup. This is category B repeated lifetime corruption, not an ordinary stale cleanup dereference. The second operation calls a real free operation through a potentially dangling pointer and can modify allocator or object-lifetime state. It is therefore `CLASS_B`, not `CLASS_C`. The demonstrated practical consequence is kernel memory corruption with plausible crash or denial of service. Controlled reclaim, useful type confusion, callback control, arbitrary read/write, and privilege escalation remain unproven. The bug is not `CLASS_A`. `ImportantCandidate=YES` because the concrete second free leaves meaningful post-lifetime corruption leverage unresolved. `AutoDowngradeAllowed=NO` because treating it as an ordinary cleanup crash would discard the established repeated lifetime mutation. The physical and specialized-device requirements nevertheless keep the numeric score below the normal actionable range. 5. One-sentence report phrase A caiaq audio initialization failure can leave freed URB or callback pointers reachable for a later destructor call, causing a concrete double-free with kernel-crash potential and unresolved allocator-corruption leverage. 6. Manual review recommendation MANUAL CHECK REQUIRED The second free is concrete enough to establish a Class B lifetime-corruption primitive, but allocator reuse potential and attacker control over the required initialization failure need call-path and reproducer review. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ALSA: caiaq: Fix potential double-free at error path [ Upstream Commit: 2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8 Changed files: sound/usb/caiaq/audio.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=2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98066 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98066 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:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H The Best / paranoid CVSS vector: AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H The Best / paranoid CVSS score: 6.4 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: 3 Paranoid ActionableScore: 4 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: YES Published priority for this report (same as in Subject): MODERATE 7.0 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).