CVE-2026-43062High· 7.1▾ TwilightIn 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…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 39.1 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
Last analysed / modified upstream
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.
Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < 21d3ba696918d6373233aac0b9d51fcabdedddc0Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < 3b94e62caa1dc1198d0d55d97bd710da1dee15d7Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < 111f74547eee8cfedfb854284e80f35c8a491186Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < dd3b221e21079ade8263fbb7176f3d55ad75d3b6Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < d90150c72d2e6a8a3079e88755dafcfbe91c746dLinux >= 15f02b91056253e8cdc592888f431da0731337b8 < 5a1ea296f8589ce8f1e3141b2b123b34ad010e19Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < f110b8f58b254bf997cec1bd60701b7798e9bb82Linux >= 15f02b91056253e8cdc592888f431da0731337b8 < 15145675690cab2de1056e7ed68e59cbd0452529Linux 5.7Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets