CVE-2026-31513 Vulnerability Analysis & Exploit Details

CVE-2026-31513
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-31513 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • 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-31513 Details

Status: Analyzed

Last updated: 🕓 28 Apr 2026, 16:15 UTC
Originally published on: 🕑 22 Apr 2026, 14:16 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

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

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-31513 Vulnerability Summary

CVE-2026-31513: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req Syzbot reported a KASAN stack-out-of-bounds read in l2cap_build_cmd() that is triggered by a malformed Enhanced Credit Based Connection Request. The vulnerability stems from l2cap_ecred_conn_req(). The function allocates a local stack buffer (`pdu`) designed to hold a maximum of 5 Source Channel IDs (SCIDs), totaling 18 bytes. When an attacker sends a request with more than 5 SCIDs, the function calculates `rsp_len` based on this unvalidated `cmd_len` before checking if the number of SCIDs exceeds L2CAP_ECRED_MAX_CID. If the SCID count is too high, the function correctly jumps to the `response` label to reject the packet, but `rsp_len` retains the attacker's oversized value. Consequently, l2cap_send_cmd() is instructed to read past the end of the 18-byte `pdu` buffer, triggering a KASAN panic. Fix this by moving the assignment of `rsp_len` to after the `num_scid` boundary check. If the packet is rejected, `rsp_len` will safely remain 0, and the error response will only read the 8-byte base header from the stack.

Assessing the Risk of CVE-2026-31513

Access Complexity Graph

The exploitability of CVE-2026-31513 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-31513

With low attack complexity and no required privileges, CVE-2026-31513 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-31513, 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-31513, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-31513 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-31513 poses no threat to data integrity.
  • Availability: High
    CVE-2026-31513 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-31513 References

External References

CWE Common Weakness Enumeration

CWE-125

CAPEC Common Attack Pattern Enumeration and Classification

  • Overread Buffers CAPEC-540 An adversary attacks a target by providing input that causes an application to read beyond the boundary of a defined buffer. This typically occurs when a value influencing where to start or stop reading is set to reflect positions outside of the valid memory location of the buffer. This type of attack may result in exposure of sensitive information, a system crash, or arbitrary code execution.

Vulnerable Configurations

  • 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.12.78:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.78:*:*:*:*:*:*:*
  • 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.18.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.20:*:*:*:*:*:*:*
  • 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.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-31513: 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-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...
  • CVE-2026-7685 – A vulnerability was detected in Edimax BR-6208AC up to 1.02. Affected is an unknown function of the file /goform/setWAN. Performing a manipulation ...
  • CVE-2026-7684 – A security vulnerability has been detected in Edimax BR-6428nC up to 1.16. This impacts an unknown function of the file /goform/setWAN. Such manipu...
  • CVE-2026-7683 – A weakness has been identified in Edimax BR-6428nC up to 1.16. This affects an unknown function of the file /goform/setWAN of the component Web Int...
  • CVE-2026-7682 – A security flaw has been discovered in Edimax BR-6208AC 1.02. The impacted element is the function setWAN of the file /goform/setWAN of the compone...