Bug 2554889 (CVE-2026-98457) - CVE-2026-98457 kernel: Bluetooth: L2CAP: validate frame length before control and FCS access
Summary: CVE-2026-98457 kernel: Bluetooth: L2CAP: validate frame length before control...
Keywords:
Status: NEW
Alias: CVE-2026-98457
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-18 15:25 UTC by OSIDB Bzimport
Modified: 2026-10-19 14:53 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-18 15:25:43 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.