Skip to main content

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: validate frame length before control and FCS access… (CVE-2026-98457)

0
Medium
Published: 10/18/2026 (10/18/2026, 18:31:49 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's Bluetooth L2CAP implementation allows out-of-bounds reads due to insufficient validation of frame length before accessing control and FCS fields. This occurs in the l2cap_data_rcv() function when unpacking control fields without ensuring their presence, and in l2cap_check_fcs() when CRC16 is enabled and frame length checks are inadequate.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/18/2026, 20:03:20 UTC

Technical Analysis

The Linux kernel Bluetooth L2CAP component had a vulnerability where the function l2cap_data_rcv() would unpack a two-byte or four-byte control field without verifying that the frame length was sufficient, leading to potential out-of-bounds reads. Additionally, when CRC16 is enabled, l2cap_check_fcs() subtracts two bytes from the frame length without checking if enough bytes remain, causing a wraparound and subsequent out-of-bounds read during FCS access. The fix involves validating that the frame contains both the control field and, if enabled, the FCS before accessing these fields.

Potential Impact

This vulnerability can cause out-of-bounds reads in the Bluetooth L2CAP processing in the Linux kernel, which may lead to kernel memory disclosure or instability. However, no known exploits in the wild have been reported. The impact is limited to the kernel Bluetooth stack and requires crafted Bluetooth frames to trigger.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to validate frame lengths before accessing control and FCS fields in the Bluetooth L2CAP code. Users should apply the official Linux kernel updates that include this patch. Since this is not a cloud service, remediation requires updating the affected Linux kernel versions once patches are released. Patch status is not explicitly confirmed in the provided data; users should consult the vendor advisory for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-8cwv-pj99-4m5f
Osv Schema Version
1.4.0
Aliases
["CVE-2026-98457"]

Threat ID: 6ad520b12cdf04f656993b17

Added to database: 10/18/2026, 19:40:33 UTC

Last enriched: 10/18/2026, 20:03:20 UTC

Last updated: 10/18/2026, 22:02:57 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses