CVE-2026-31552 Vulnerability Analysis & Exploit Details

CVE-2026-31552
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-31552 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-31552 Details

Status: Analyzed

Last updated: 🕗 27 Apr 2026, 20:15 UTC
Originally published on: 🕒 24 Apr 2026, 15:16 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

416baaa9-dc9f-4396-8d5f-8c081fb06d67

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2026-31552 Vulnerability Summary

CVE-2026-31552: In the Linux kernel, the following vulnerability has been resolved: wifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom Since upstream commit e75665dd0968 ("wifi: wlcore: ensure skb headroom before skb_push"), wl1271_tx_allocate() and with it wl1271_prepare_tx_frame() returns -EAGAIN if pskb_expand_head() fails. However, in wlcore_tx_work_locked(), a return value of -EAGAIN from wl1271_prepare_tx_frame() is interpreted as the aggregation buffer being full. This causes the code to flush the buffer, put the skb back at the head of the queue, and immediately retry the same skb in a tight while loop. Because wlcore_tx_work_locked() holds wl->mutex, and the retry happens immediately with GFP_ATOMIC, this will result in an infinite loop and a CPU soft lockup. Return -ENOMEM instead so the packet is dropped and the loop terminates. The problem was found by an experimental code review agent based on gemini-3.1-pro while reviewing backports into v6.18.y.

Assessing the Risk of CVE-2026-31552

Access Complexity Graph

The exploitability of CVE-2026-31552 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-31552

With low attack complexity and no required privileges, CVE-2026-31552 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-31552, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-31552, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-31552 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-31552 poses no threat to data integrity.
  • Availability: High
    CVE-2026-31552 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-31552 References

External References

CWE Common Weakness Enumeration

CWE-835

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.10.250:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.250:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.10.251:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.251:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.10.252:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.252:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.200:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.200:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.201:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.201:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.202:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.202:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.163:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.163:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.164:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.164:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1.165:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1.165:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.124:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.124:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.125:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.125:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.127:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.127:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.128:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.128:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.129:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.129:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.70:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.70:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.72:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.72:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.74:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.74:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.75:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.75:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.77:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.77:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-31552: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-7690 – A weakness has been identified in Wavlink WL-WN570HA1 R70HA1 V1410_221110. This issue affects the function set_sys_adm of the file /cgi-bin/adm.cgi...
  • CVE-2026-7689 – A security flaw has been discovered in Dolibarr ERP CRM up to 23.0.2. This vulnerability affects the function dol_verifyHash in the library htdocs/...
  • CVE-2026-7688 – A vulnerability was identified in Dolibarr ERP CRM up to 23.0.2. This affects the function _checkValForAPI of the file htdocs/expedition/class/expe...
  • CVE-2026-7687 – A vulnerability was determined in langflow-ai langflow up to 1.8.4. Affected by this issue is the function CodeParser.parse_callable_details of the...
  • CVE-2026-7686 – A vulnerability was found in eyeo Adblock Plus up to 4.36.2 on Chrome. Affected by this vulnerability is the function postMessage of the file premi...