Skip to main content
VulnerabilityPublished Updated

CVE-2026-43062: Linux kernel · Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()

Source GCVE Database

0
Authoritative record:CVE-2026-43062· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in f110b8f58b254bf997cec1bd60701b7798e9bb82 : patch Linux kernel soon.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in f110b8f58b254bf997cec1bd60701b7798e9bb82, dd3b221e21079ade8263fbb7176f3d55ad75d3b6, d90150c72d2e6a8a3079e88755dafcfbe91c746d +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 15f02b91056253e8cdc592888f431da0731337b8, < f110b8f58b254bf997cec1bd60701b7798e9bb82
Fixed in
  • f110b8f58b254bf997cec1bd60701b7798e9bb82
LinuxLinuxAffected
  • ≥ 15f02b91056253e8cdc592888f431da0731337b8, < dd3b221e21079ade8263fbb7176f3d55ad75d3b6
Fixed in
  • dd3b221e21079ade8263fbb7176f3d55ad75d3b6
LinuxLinuxAffected
  • ≥ 15f02b91056253e8cdc592888f431da0731337b8, < d90150c72d2e6a8a3079e88755dafcfbe91c746d
Fixed in
  • d90150c72d2e6a8a3079e88755dafcfbe91c746d
LinuxLinuxAffected
  • ≥ 15f02b91056253e8cdc592888f431da0731337b8, < 15145675690cab2de1056e7ed68e59cbd0452529
Fixed in
  • 15145675690cab2de1056e7ed68e59cbd0452529
LinuxLinuxAffected
  • ≥ 15f02b91056253e8cdc592888f431da0731337b8, < 111f74547eee8cfedfb854284e80f35c8a491186
Fixed in
  • 111f74547eee8cfedfb854284e80f35c8a491186
LinuxLinuxAffected
  • ≥ 15f02b91056253e8cdc592888f431da0731337b8, < 21d3ba696918d6373233aac0b9d51fcabdedddc0
Fixed in
  • 21d3ba696918d6373233aac0b9d51fcabdedddc0

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() l2cap_ecred_reconf_rsp() casts the incoming data to struct l2cap_ecred_conn_rsp (the ECRED *connection* response, 8 bytes with result at offset 6) instead of struct l2cap_ecred_reconf_rsp (2 bytes with result at offset 0). This causes two problems: - The sizeof(*rsp) length check requires 8 bytes instead of the correct 2, so valid L2CAP_ECRED_RECONF_RSP packets are rejected with -EPROTO. - rsp->result reads from offset 6 instead of offset 0, returning wrong data when the packet is large enough to pass the check. Fix by using the correct type. Also pass the already byte-swapped result variable to BT_DBG instead of the raw __le16 field.

References

Community reviews

Loading reviews…