Review reviewHigh

CVE-2026-23462

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: Fix possible UAF This fixes the following trace caused by not dropping l2cap_conn reference when user->remove callback is called: [ 97.809249] l2cap_conn_free: freeing conn ffff88810a171c00 [ 97.809907] CPU: 1 UID: 0 PID: 1419 Comm: repro_standalon Not tainted 7.0.0-rc1-dirty #14 PREEMPT(lazy) [ 97.809935] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 97.809947] Call Trace: [ 97.809954] <TASK> [ 97.809961] dump_stack_lvl (lib/dump_stack.c:122) [ 97.809990] l...

CVSS
8.8
EPSS
0.26%
18.0% percentile
CISA KEV
Not listed
Published
2026.04.04
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.26%
Technical severityCVSS 8.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: Fix possible UAF This fixes the following trace caused by not dropping l2cap_conn reference when user->remove callback is called: [ 97.809249] l2cap_conn_free: freeing conn ffff88810a171c00 [ 97.809907] CPU: 1 UID: 0 PID: 1419 Comm: repro_standalon Not tainted 7.0.0-rc1-dirty #14 PREEMPT(lazy) [ 97.809935] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 [ 97.809947] Call Trace: [ 97.809954] <TASK> [ 97.809961] dump_stack_lvl (lib/dump_stack.c:122) [ 97.809990] l...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < d955ccbf91ab74d76fe9e4eab2846a7d8a173075, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < 18b1263ece6431bd78fa6b61faaef5281203741c, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < 21a47a119f33df9bb157326846390d7e8e1b45ba, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < 45ebe5b900200ac3e01f3470506a44a447825721, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < 7c805b7d1e580eececcc92470292e3dbc42bc3f5, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < f8b6ed2f06d3baa44f347a0fa2af52433f386463, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < 4d37fa7582aa960ba23e10a7a2596a29f37ad281, >= b4f34d8d9d26b2428fa7cf7c8f97690a297978e6 < dbf666e4fc9bdd975a61bf682b3f75cb0145eedd, >= 3.10, >= 3.10 < 5.10.253, >= 5.11 < 5.15.203, >= 5.16 < 6.1.167, >= 6.2 < 6.6.130, >= 6.7 < 6.12.78, >= 6.13 < 6.18.20, >= 6.19 < 6.19.10, 7.0
Fixed versions
5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416