CVE-2026-31513

개요

A flaw was found in the Linux kernel's Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) component. A remote attacker can send a specially crafted Enhanced Credit Based Connection Request with an excessive number of Source Channel IDs (SCIDs). This can cause a stack-out-of-bounds read when processing the malformed request, leading to a kernel panic and a Denial of Service (DoS) on the affected system.

내용

The fix assigns rsp_len only after validating num_scid so error responses cannot read past the small on-stack pdu buffer. Red Hat concurs with upstream that this is primarily a remote-triggerable crash against the Bluetooth stack. Patch kernels promptly.

완화 방법

To mitigate this issue, prevent the bluetooth module from being loaded. See https://access.redhat.com/solutions/41278 for instructions.

CVSS (Common Vulnerability Scoring System) 점수 세부 사항

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

다음의 CVSS 지표 및 점수는 예비 정보로 검토 대상입니다.

CVSS v3 점수 분석

Red HatNVDcve.org
기본 점수6.1N/A8.1
공격 벡터LocalN/AAdjacent Network
공격 복잡성LowN/ALow
필요한 권한LowN/ANone
사용자 상호 작용NoneN/ANone
범위UnchangedN/AUnchanged
기밀성LowN/AHigh
무결성에 미치는 영향NoneN/ANone
가용성에 미치는 영향HighN/AHigh

벡터

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

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

취약점 이해 (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

자주하는 질문

에라타 알림을 받으시겠습니까? 여기에서 등록하세요.