CyberIntel ⬡ News
★ Saved ◆ Cyber Reads
← Back ⬡ Vulnerabilities & CVEs Apr 24, 2026

CVE-2026-31572 | Linux Kernel up to 6.18.20/6.19.10 Genpd API pm_runtime_get_sync race condition

VulDB Archived Apr 24, 2026 ✓ Full text saved

A vulnerability was found in Linux Kernel up to 6.18.20/6.19.10 . It has been declared as critical . Impacted is the function pm_runtime_get_sync of the component Genpd API . Executing a manipulation can lead to race condition. This vulnerability is handled as CVE-2026-31572 . The attack can only be done within the local network. There is not any exploit available. It is recommended to upgrade the affected component.

Full text archived locally
✦ AI Summary · Claude Sonnet


    VDB-359387 · CVE-2026-31572 · GCVE-0-2026-31572 LINUX KERNEL UP TO 6.18.20/6.19.10 GENPD API PM_RUNTIME_GET_SYNC RACE CONDITION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.4 $0-$5k 1.43+ Summaryinfo A vulnerability was found in Linux Kernel up to 6.18.20/6.19.10. It has been rated as critical. The affected element is the function pm_runtime_get_sync of the component Genpd API. The manipulation leads to race condition. This vulnerability is uniquely identified as CVE-2026-31572. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability was found in Linux Kernel up to 6.18.20/6.19.10. It has been rated as critical. This issue affects the function pm_runtime_get_sync of the component Genpd API. The manipulation with an unknown input leads to a race condition vulnerability. Using CWE to declare the problem leads to CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown. The summary by CVE is: In the Linux kernel, the following vulnerability has been resolved: i2c: designware: amdisp: Fix resume-probe race condition issue Identified resume-probe race condition in kernel v7.0 with the commit 38fa29b01a6a ("i2c: designware: Combine the init functions"),but this issue existed from the beginning though not detected. The amdisp i2c device requires ISP to be in power-on state for probe to succeed. To meet this requirement, this device is added to genpd to control ISP power using runtime PM. The pm_runtime_get_sync() called before i2c_dw_probe() triggers PM resume, which powers on ISP and also invokes the amdisp i2c runtime resume before the probe completes resulting in this race condition and a NULL dereferencing issue in v7.0 Fix this race condition by using the genpd APIs directly during probe: - Call dev_pm_genpd_resume() to Power ON ISP before probe - Call dev_pm_genpd_suspend() to Power OFF ISP after probe - Set the device to suspended state with pm_runtime_set_suspended() - Enable runtime PM only after the device is fully initialized It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-31572 since 03/09/2026. The exploitation is known to be difficult. Technical details of the vulnerability are known, but there is no available exploit. Upgrading to version 6.18.21 or 6.19.11 eliminates this vulnerability. Applying the patch 83bcea9da91965484df64a6492b89e65d41ab31c/e81f0341754c309e33babea2821eda8f98f0b44c/e2f1ada8e089dd5a331bcd8b88125ae2af8d188f 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 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.18.20 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 6.19.10 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: 4.6 VulDB Meta Temp Score: 4.4 VulDB Base Score: 4.6 VulDB Temp Score: 4.4 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: Race condition CWE: CWE-362 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 6.18.21/6.19.11 Patch: 83bcea9da91965484df64a6492b89e65d41ab31c/e81f0341754c309e33babea2821eda8f98f0b44c/e2f1ada8e089dd5a331bcd8b88125ae2af8d188f 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-31572 (🔒) GCVE (CVE): GCVE-0-2026-31572 GCVE (VulDB): GCVE-100-359387 Entryinfo Created: 04/24/2026 17:48 Changes: 04/24/2026 17:48 (59) Complete: 🔍 Cache ID: 99:31E:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸
    💬 Team Notes
    Article Info
    Source
    VulDB
    Category
    ⬡ Vulnerabilities & CVEs
    Published
    Apr 24, 2026
    Archived
    Apr 24, 2026
    Full Text
    ✓ Saved locally
    Open Original ↗