CVE-2026-31550 | Linux Kernel up to 6.19.9 pmdomain bcm2835_asb_control infinite loop

VDB-359370 · CVE-2026-31550 · GCVE-0-2026-31550 LINUX KERNEL UP TO 6.19.9 PMDOMAIN BCM2835_ASB_CONTROL INFINITE LOOP HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.5 $0-$5k 0.86+ Summaryinfo A vulnerability was found in Linux Kernel up to 6.19.9 and classified as critical. Affected by this vulnerability is the function bcm2835_asb_control of the component pmdomain. The manipulation results in infinite loop. This vulnerability is known as CVE-2026-31550. No exploit is available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability classified as critical has been found in Linux Kernel up to 6.19.9. Affected is the function bcm2835_asb_control of the component pmdomain. The manipulation with an unknown input leads to a infinite loop vulnerability. CWE is classifying the issue as CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. This is going to have an impact on availability. CVE summarizes: In the Linux kernel, the following vulnerability has been resolved: pmdomain: bcm: bcm2835-power: Increase ASB control timeout The bcm2835_asb_control() function uses a tight polling loop to wait for the ASB bridge to acknowledge a request. During intensive workloads, this handshake intermittently fails for V3D's master ASB on BCM2711, resulting in "Failed to disable ASB master for v3d" errors during runtime PM suspend. As a consequence, the failed power-off leaves V3D in a broken state, leading to bus faults or system hangs on later accesses. As the timeout is insufficient in some scenarios, increase the polling timeout from 1us to 5us, which is still negligible in the context of a power domain transition. Also, replace the open-coded ktime_get_ns()/ cpu_relax() polling loop with readl_poll_timeout_atomic(). The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-31550 since 03/09/2026. Technical details are known, but there is no available exploit. Upgrading to version 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.20 or 6.19.10 eliminates this vulnerability. Applying the patch 0e84e74849d2d7e9b23a09c2d5e0d9357db1ca59/c5e734f6a0740dce92e7c919e632cb43fa5d4e53/622ab02e955c35c125ff2b65d8327b2c52db8758/9443202d91388026dbf7312972a74fbfd27ee82f/ea4fa54b83bb2e4a21e9026824bfe271b1a6ee1e/18605b1b936b66b1f34dcf8e9ad4f1fbcf7a7c13/572f17180f26619809b8e0593d926762aa8660ff/b826d2c0b0ecb844c84431ba6b502e744f5d919a is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Type Operating System Vendor Linux Name Kernel Version 5.10.252 5.15.202 6.1.166 6.6.129 6.12.0 6.12.1 6.12.2 6.12.3 6.12.4 6.12.5 6.12.6 6.12.7 6.12.8 6.12.9 6.12.10 6.12.11 6.12.12 6.12.13 6.12.14 6.12.15 6.12.16 6.12.17 6.12.18 6.12.19 6.12.20 6.12.21 6.12.22 6.12.23 6.12.24 6.12.25 6.12.26 6.12.27 6.12.28 6.12.29 6.12.30 6.12.31 6.12.32 6.12.33 6.12.34 6.12.35 6.12.36 6.12.37 6.12.38 6.12.39 6.12.40 6.12.41 6.12.42 6.12.43 6.12.44 6.12.45 6.12.46 6.12.47 6.12.48 6.12.49 6.12.50 6.12.51 6.12.52 6.12.53 6.12.54 6.12.55 6.12.56 6.12.57 6.12.58 6.12.59 6.12.60 6.12.61 6.12.62 6.12.63 6.12.64 6.12.65 6.12.66 6.12.67 6.12.68 6.12.69 6.12.70 6.12.71 6.12.72 6.12.73 6.12.74 6.12.75 6.12.76 6.12.77 6.18.0 6.18.1 6.18.2 6.18.3 6.18.4 6.18.5 6.18.6 6.18.7 6.18.8 6.18.9 6.18.10 6.18.11 6.18.12 6.18.13 6.18.14 6.18.15 6.18.16 6.18.17 6.18.18 6.18.19 6.19.0 6.19.1 6.19.2 6.19.3 6.19.4 6.19.5 6.19.6 6.19.7 6.19.8 6.19.9 License open-source Website Vendor: https://www.kernel.org/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.7 VulDB Meta Temp Score: 5.5 VulDB Base Score: 5.7 VulDB Temp Score: 5.5 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Infinite loop CWE: CWE-835 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Kernel 5.10.253/5.15.203/6.1.167/6.6.130/6.12.78/6.18.20/6.19.10 Patch: 0e84e74849d2d7e9b23a09c2d5e0d9357db1ca59/c5e734f6a0740dce92e7c919e632cb43fa5d4e53/622ab02e955c35c125ff2b65d8327b2c52db8758/9443202d91388026dbf7312972a74fbfd27ee82f/ea4fa54b83bb2e4a21e9026824bfe271b1a6ee1e/18605b1b936b66b1f34dcf8e9ad4f1fbcf7a7c13/572f17180f26619809b8e0593d926762aa8660ff/b826d2c0b0ecb844c84431ba6b502e744f5d919a Timelineinfo 03/09/2026 CVE reserved 04/24/2026 +45 days Advisory disclosed 04/24/2026 +0 days VulDB entry created 04/24/2026 +0 days VulDB entry last update Sourcesinfo Vendor: kernel.org Advisory: git.kernel.org Status: Confirmed CVE: CVE-2026-31550 (🔒) GCVE (CVE): GCVE-0-2026-31550 GCVE (VulDB): GCVE-100-359370 Entryinfo Created: 04/24/2026 17:43 Changes: 04/24/2026 17:43 (59) Complete: 🔍 Cache ID: 99:914:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸