Linux Kernel up to 7.3-rc4 Bluetooth l2cap_data_rcv/l2cap_check_fcs len out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.46

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 7.3-rc4. Impacted is the function l2cap_data_rcv/l2cap_check_fcs of the component Bluetooth. This manipulation of the argument len causes out-of-bounds. The identification of this vulnerability is CVE-2026-98457. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.3-rc4 and classified as critical. Affected by this vulnerability is the function l2cap_data_rcv/l2cap_check_fcs of the component Bluetooth. The manipulation of the argument len with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-98457 since 09/25/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/18/2026).

Upgrading to version 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9 or 7.3-rc5 eliminates this vulnerability. Applying the patch 4373ba79a267947e771c438507f7b103e30bdb21/965bd88ed4b4763cb765dd65885adcfa588c6b14/3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70/8c7556c7cd17e073bbefdc4a9a4694a207544c37/1fdbb2a712a9a162ee817c959740face80b3d929/c6a288e6001bcce16553c3853e0f5a45eaaf85c7/f557274af7b94b6134692e6f26b880f1e34c15bf/6c78a213d9070b610c7f418af2c25b66180b7e37 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.271/5.15.222/6.1.189/6.6.158/6.12.112/6.18.55/7.2.9/7.3-rc5
Patch: 4373ba79a267947e771c438507f7b103e30bdb21/965bd88ed4b4763cb765dd65885adcfa588c6b14/3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70/8c7556c7cd17e073bbefdc4a9a4694a207544c37/1fdbb2a712a9a162ee817c959740face80b3d929/c6a288e6001bcce16553c3853e0f5a45eaaf85c7/f557274af7b94b6134692e6f26b880f1e34c15bf/6c78a213d9070b610c7f418af2c25b66180b7e37

Timelineinfo

09/25/2026 CVE reserved
10/18/2026 +23 days Advisory disclosed
10/18/2026 +0 days VulDB entry created
10/18/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-98457 (🔒)
GCVE (CVE): GCVE-0-2026-98457
GCVE (VulDB): GCVE-100-421789

Entryinfo

Created: 10/18/2026 17:43
Changes: 10/18/2026 17:43 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!