From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-72260][LOW] ASoC: mediatek: mt8192: Check runtime resume during probe [ Upstream Date: Sun, 16 Aug 2026 01:45:55 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-72260 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 1 X-AL-KERNEL-ActionableScore-Lower: 0 X-AL-KERNEL-Commit: 6e2ee6eacc3ec7b339753abcf33812d27e03efe5 List-Id: CVE: CVE-2026-72260 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: ASoC: mediatek: mt8192: Check runtime resume during probe [ Upstream Commit: 6e2ee6eacc3ec7b339753abcf33812d27e03efe5 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6e2ee6eacc3ec7b339753abcf33812d27e03efe5 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72260 Analysis date: Sun, 16 Aug 2026 01:45:55 -0400 ActionableScore: 1 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: The MT8192 AFE probe path failed to handle runtime PM resume and regmap cache reinitialization errors correctly, which could leave the audio device in an inconsistent PM state and cause limited local device availability impact. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72260 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72260 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: LOW 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-72260 LOW CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';CWE-252;*CWE-772;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '2.5';DESCR 'The MT8192 AFE probe path can continue after a failed runtime PM resume or return from regmap_reinit_cache failure without properly dropping the temporary PM reference and clearing the temporary bypass state. This can leave the audio device or its runtime PM state inconsistent and may cause probe failure, device unavailability, or a persistent PM usage count leak. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate driver bind, unbind, or power management control to a reduced capability local user or service account. The issue is not network reachable and requires local control over device probing or a hardware dependent failure path. Impact is limited denial of service or degraded availability of the affected audio device. There is no evidence of UAF, OOB access, arbitrary write, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) SKIP CVE-2026-72260 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE SIMPLEFIX LEAK ERRORPATH HARDWARE - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like**:: ## 2. Signal breakdown Triggered signals: * Availability impact realistic: +1 The bug can leave the MT8192 AFE audio device or runtime PM state inconsistent, causing probe failure, device unavailability, or a PM usage count leak. Negative or limiting signals: * Requires admin/root/device-management control in typical deployments: -2 Reliable triggering normally requires driver probe, bind/unbind, device power-management manipulation, or a hardware/runtime-resume failure path. * Rare and hardware-specific subsystem: -1 The issue is specific to the MediaTek MT8192 AFE ASoC driver and its probe-time runtime PM handling. * No memory corruption signal: +0 The patch shows unchecked return handling and cleanup ordering only. No UAF, OOB access, double free, stale pointer reuse, arbitrary write, or type confusion is indicated. * No strong DoS signal: +0 The likely impact is limited device-level availability degradation, not a reliable system-wide crash. * No confidentiality or integrity impact: +0 There is no supported primitive for information disclosure, unauthorized modification, or privilege escalation. ## 3. Reachability analysis This is a local device-management and probe-path issue. A normal remote attacker cannot reach it, and it is not triggered by network traffic. In typical deployments, triggering requires privileged control over the platform device lifecycle or a hardware-dependent runtime resume failure during driver probe. Namespaces or containers do not normally make this reachable unless a container or service account is explicitly delegated device bind/unbind or power-management controls. Even then, the impact remains limited to device availability or PM state inconsistency. Call-site confidence: high. The relevant probe path and cleanup ordering are visible in the patch. ## 4. Severity interpretation This behaves like a Low-like or ordinary Moderate reliability bug, not an Important-class kernel vulnerability. The theoretical issue is a PM reference leak and inconsistent temporary probe state. The realistic impact is limited denial of service or degraded availability of the affected audio device. There is no evidence of memory corruption, privilege escalation, security-boundary bypass, or sensitive data exposure. The paranoid score only preserves a small availability concern for delegated local device-management scenarios. ## 5. One-sentence report phrase The MT8192 AFE probe path failed to handle runtime PM resume and regmap cache reinitialization errors correctly, which could leave the audio device in an inconsistent PM state and cause limited local device availability impact. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This can be auto-closed for security triage because the patch fixes local probe error handling and PM reference cleanup without memory corruption, network reachability, privilege escalation, or cross-boundary impact. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ASoC: mediatek: mt8192: Check runtime resume during probe [ Upstream Commit: 6e2ee6eacc3ec7b339753abcf33812d27e03efe5 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6e2ee6eacc3ec7b339753abcf33812d27e03efe5 Changed files: sound/soc/mediatek/mt8192/mt8192-afe-pcm.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=6e2ee6eacc3ec7b339753abcf33812d27e03efe5 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72260 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72260 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:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS score: 2.5 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: 0 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: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW 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).