From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-74332][MODERATE REGULAR] ASoC: amd: acp-sdw-sof: Bound DAI link iteration [ Upstream Date: Sun, 16 Aug 2026 05:27:54 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-74332 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: 0a5ff4000dd7a390139dd7823fef1de4963e490a List-Id: CVE: CVE-2026-74332 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: ASoC: amd: acp-sdw-sof: Bound DAI link iteration [ Upstream Commit: 0a5ff4000dd7a390139dd7823fef1de4963e490a Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0a5ff4000dd7a390139dd7823fef1de4963e490a Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74332 Analysis date: Sun, 16 Aug 2026 05:27:54 -0400 ActionableScore: 3 ActionableScore lower bound: 2 Actionable bucket: Borderline. Manual review recommended, but not an Important candidate by default Manual review required: YES Summary: An out-of-bounds read in the AMD ACP SoundWire SOF machine driver can occur during DAI link creation when all allocated sof_dais entries are initialized, potentially causing invalid descriptor interpretation and driver initialization failure on affected hardware. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-74332 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74332 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-74332 MODERATE CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';CWE-125;*CWE-787;CWE-129;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.2';DESCR 'An out of bounds read in the ASoC AMD SoundWire machine driver can occur because create_sdw_dailinks() walks the sof_dais array until it finds an entry with initialised cleared, while the array is allocated with exactly num_ends entries and no guaranteed sentinel. If every allocated entry is initialized, the loop can read beyond the end of the array and may interpret adjacent memory as another DAI descriptor. For the CVSS the PR:H is used because reliable triggering normally requires privileged control of driver probing or a specific platform firmware and hardware configuration rather than ordinary local user actions. The issue is not network reachable and is limited to the local device initialization path. Base impact is likely low availability impact through failed probe or audio subsystem failure. For the paranoid score, impact is treated as possible C:L/I:L/A:H because the out of bounds descriptor may drive follow on DAI link creation using invalid data, so manual review is preferred over autoclosed false negatives.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline. Manual review recommended, but not an Important candidate by default (with actual score 3) YES INIT SIMPLEFIX HARDWARE YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ActionableScoreLower=2 ## 1. ActionableScore * Conservative score: 2 * Paranoid score: 3 * Final recommended bucket: **Borderline. Manual review recommended, but not an Important candidate by default**:: ## 2. Signal breakdown Triggered signals: * Weak/indirect corruption candidate: +1 The loop can read past the allocated `sof_dais` array and interpret adjacent memory as another `asoc_sdw_dailink` descriptor. This is an OOB read with possible invalid object interpretation, but no demonstrated attacker-controlled overwrite, UAF reclaim, callback control, or arbitrary write. * Firmware-mediated external influence: +1 The affected path depends on AMD SoundWire / SOF machine-driver topology and platform data. Triggering is more plausibly mediated by hardware, firmware, ACPI, topology, or driver probe state than by a normal local user interface. * Availability impact realistic: +1 A bad DAI descriptor can plausibly break driver probe or audio device initialization. This is likely limited to audio subsystem failure rather than a reliable system-wide panic. * Privileged kernel/device-management path: +1 in paranoid score only The invalid descriptor is consumed during trusted kernel driver initialization and DAI link construction. This deserves manual review, but the patch does not show corruption of credentials, page ownership, refcounts, function pointers, or other high-value security objects. Negative or limiting signals: * Requires admin/root or platform control for reliable triggering: -2 conservative Reliable triggering normally requires driver reprobe/bind/unbind, module reload, modified firmware/topology/platform data, or a matching affected AMD SoundWire platform. Ordinary local users are not shown to control this path. * Rare or hardware-specific configuration: -1 The bug is limited to the AMD ACP SoundWire SOF machine driver path and does not affect a broad default kernel interface. * No attacker-controlled payload or overwrite target: -1 paranoid limiter The patch demonstrates an out-of-bounds read and possible invalid descriptor consumption, not a controlled write primitive. ## 3. Reachability analysis The issue is local and hardware or platform dependent. It is not network reachable. A normal unprivileged local user is not shown to be able to trigger the vulnerable path directly. In typical deployments, reliable triggering would require administrative control over driver probing or a platform/firmware/topology condition that causes all allocated `sof_dais` entries to be initialized without a sentinel. Namespaces and containers do not materially lower the privilege requirement unless the environment delegates real device-management capabilities to the container, which is uncommon. Call-site confidence: high. The patch includes the changed caller, showing that `num_ends` is the allocated count passed from `sof_card_dai_links_create()` into `create_sdw_dailinks()`. ## 4. Severity interpretation This behaves more like a low-to-borderline Moderate driver initialization bug than an Important-class kernel vulnerability. The theoretical concern is that the OOB read may cause adjacent memory to be treated as a DAI descriptor and feed follow-on DAI link creation. The realistic evidence supports failed probe, audio initialization failure, or limited DoS. There is no demonstrated arbitrary write, UAF, controlled reclaim, privilege escalation path, information leak, or network trigger. ## 5. One-sentence report phrase An out-of-bounds read in the AMD ACP SoundWire SOF machine driver can occur during DAI link creation when all allocated sof_dais entries are initialized, potentially causing invalid descriptor interpretation and driver initialization failure on affected hardware. ## 6. Manual review recommendation MANUAL CHECK RECOMMENDED Reason: the bug is an OOB array access in a trusted driver initialization path, and the paranoid interpretation allows invalid descriptor consumption. However, triggering appears hardware or admin dependent, and the patch does not support Important-class treatment by default. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ASoC: amd: acp-sdw-sof: Bound DAI link iteration [ Upstream Commit: 0a5ff4000dd7a390139dd7823fef1de4963e490a Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0a5ff4000dd7a390139dd7823fef1de4963e490a Changed files: sound/soc/amd/acp/acp-sdw-sof-mach.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=0a5ff4000dd7a390139dd7823fef1de4963e490a ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-74332 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74332 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:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H The Best / paranoid CVSS score: 5.2 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).