Skip to main content

Linux CVE-2026-98457

| EUVDEUVD-2026-103697
2026-10-18 Linux GHSA-8cwv-pj99-4m5f
View
Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: validate frame length before control and FCS access

l2cap_data_rcv() unpacks either a two-byte or four-byte control field without first ensuring that it is present. A short ERTM or streaming-mode frame can therefore cause an out-of-bounds read.

There is a second short-frame case when CRC16 is enabled. After the control field is pulled, l2cap_check_fcs() subtracts two from skb->len without checking it. If fewer than two bytes remain, the subtraction wraps; skb_trim() leaves the buffer unchanged and the subsequent FCS load reads past the logical end of the frame.

Validate that the frame contains both its control field and, when enabled, its FCS before either field is accessed.

Affected VersionsENISA

Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <4373ba79a267947e771c438507f7b103e30bdb21
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70
Linux patch: 6.12.112
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <c6a288e6001bcce16553c3853e0f5a45eaaf85c7
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <1fdbb2a712a9a162ee817c959740face80b3d929
Linux patch: 5.10.271
Linux patch: 6.1.189
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <f557274af7b94b6134692e6f26b880f1e34c15bf
Linux 2.6.32
Linux patch: 7.3-rc5
Linux patch: 7.2.9
Linux patch: 0
Linux patch: 6.6.158
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <965bd88ed4b4763cb765dd65885adcfa588c6b14
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <8c7556c7cd17e073bbefdc4a9a4694a207544c37
Linux patch: 6.18.55
Linux 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a <6c78a213d9070b610c7f418af2c25b66180b7e37
Linux patch: 5.15.222

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 18, 2026 - 16:02 EUVD
CVE Published
Oct 18, 2026 - 15:15 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

Data Quality
1 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.
Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy