CVE-2026-99013: Bluetooth: ISO: Reject concurrent BIS listener setup

Q: What conditions are required to trigger the issue?

Two concurrent listen() calls must be made on the same Bluetooth ISO broadcast socket while it is in the BT_BOUND state. The race exists because the socket lock is dropped before BIS listener setup and the state was not rechecked after both relevant locks were acquired.

Q: What can happen if the race is triggered?

The second listener setup can overwrite the socket's connection pointer, leaking the first connection reference while that first connection still points to the socket. After the socket is torn down through the second connection, later events on the first connection can access a stale socket and cause a use-after-free.

Q: How does the resolved code prevent concurrent setup?

It rechecks that the socket remains BT_BOUND and verifies that its connection pointer is NULL after acquiring both the HCI device and socket locks. A competing setup is rejected with -EBADFD before another connection is allocated.

Published Oct 23, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: Reject concurrent BIS listener setup

isosocklisten() drops the socket lock before calling isolistenbis() to preserve the hdev->lock ordering. Two concurrent listen() calls on the same broadcast socket can therefore both observe BTBOUND. Caller A can attach connA and release the locks, then caller B can acquire them and attach connB before A publishes BTLISTEN.

isochanadd() checks whether connB already has a socket, but not whether the socket already has a connection. The second attachment overwrites isopi(sk)->conn, leaking the connA reference and leaving connA->sk intact. Socket teardown follows connB, so later events on connA can cause a stale socket access.

Recheck BTBOUND and require isopi(sk)->conn to be NULL after taking both the HCI device and socket locks in isolistenbis(). The connection check also covers the interval between attachment and publication of BTLISTEN. Reject a competing setup with -EBADFD through the existing unlock path before allocating another connection.

A recorded KASAN report from an instrumented kernel shows:

BUG: KASAN: slab-use-after-free in isosockhold+0x119/0x1f0 Call Trace: isosockhold+0x119/0x1f0 isoconndel+0xe4/0x270 hcidisconncompleteevt+0x351/0x8c0 hcieventpacket+0x71b/0xb20 hcirxwork+0x293/0x730

Allocated by task 93: skprotalloc+0x113/0x220 skalloc+0x2b/0x6d0 btsockalloc+0x29/0x370 isosockalloc.constprop.0+0x19/0x300 isosockcreate+0x94/0x100

Freed by task 93: kfree+0x121/0x3c0 skdestruct+0x42b/0x540 isosockrelease+0x29d/0x340 sockrelease+0xa1/0x260 sockclose+0x10/0x20

Affected Software

175 affected componentsFixes available

Linux Linux kernel

linux/kernel<6.12.113

6.12.113

linux/kernel>=6.13.0<6.18.57

6.18.57

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1069.74~22.04.1

6.8.0-1069.74~22.04.1

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1073.82~22.04.1

6.8.0-1073.82~22.04.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-azure-fde-6.8<6.8.0-1071.78~22.04.1

6.8.0-1071.78~22.04.1

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1073.81~22.04.1

6.8.0-1073.81~22.04.1

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-ibm-6.8<6.8.0-1069.70~22.04.1

6.8.0-1069.70~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-149.149.1~22.04.1

6.8.0-149.149.1~22.04.1

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1067.71~22.04.1

6.8.0-1067.71~22.04.1

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-149.149~22.04.2

6.8.0-149.149~22.04.2

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime-6.8<6.8.1-1064.65~22.04.1

6.8.1-1064.65~22.04.1

ubuntu/linux<6.8.0-149.149

6.8.0-149.149

ubuntu/linux-aws<6.8.0-1069.74

6.8.0-1069.74

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17*

ubuntu/linux-aws-7.0<7.0.0-1017.18~24.04.1

7.0.0-1017.18~24.04.1

ubuntu/linux-azure<6.8.0-1073.82

6.8.0-1073.82

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-6.17*

ubuntu/linux-azure-7.0*

ubuntu/linux-azure-fde<6.8.0-1071.78

6.8.0-1071.78

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-fde-6.17*

ubuntu/linux-azure-fde-7.0<7.0.0-1019.19~24.04.1

7.0.0-1019.19~24.04.1

ubuntu/linux-azure-nvidia*

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp<6.8.0-1073.81

6.8.0-1073.81

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gcp-7.0<7.0.0-1017.19~24.04.1

7.0.0-1017.19~24.04.1

ubuntu/linux-gke<6.8.0-1068.77

6.8.0-1068.77

ubuntu/linux-gkeop<6.8.0-1053.57

6.8.0-1053.57

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-hwe-6.17*

ubuntu/linux-hwe-7.0*

ubuntu/linux-ibm<6.8.0-1069.70

6.8.0-1069.70

ubuntu/linux-lowlatency<6.8.0-149.149.1

6.8.0-149.149.1

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia<6.8.0-1067.70

6.8.0-1067.70

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17*

ubuntu/linux-nvidia-7.0*

ubuntu/linux-nvidia-lowlatency<6.8.0-1067.70.1

6.8.0-1067.70.1

ubuntu/linux-nvidia-tegra*

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17*

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1067.71

6.8.0-1067.71

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17*

ubuntu/linux-oracle-7.0<7.0.0-1016.18~24.04.1

7.0.0-1016.18~24.04.1

ubuntu/linux-raspi<6.8.0-1068.72

6.8.0-1068.72

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-riscv-6.17*

ubuntu/linux-riscv-7.0<7.0.0-43.43.1~24.04.2

7.0.0-43.43.1~24.04.2

ubuntu/linux-vmware<6.8.0-1010.10

6.8.0-1010.10

ubuntu/linux-xilinx*

ubuntu/linux-bluefield<6.8.0-1036.41

6.8.0-1036.41

ubuntu/linux-raspi-realtime<6.8.0-2056.58

6.8.0-2056.58

ubuntu/linux-realtime<6.8.1-1064.65

6.8.1-1064.65

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17*

ubuntu/linux-aws-fips<6.8.0-1069.74+fips1

6.8.0-1069.74+fips1

ubuntu/linux-azure-fips<6.8.0-1073.82+fips1

6.8.0-1073.82+fips1

ubuntu/linux-fips*

ubuntu/linux-gcp-fips<6.8.0-1073.81+fips1

6.8.0-1073.81+fips1

ubuntu/linux<7.3.0-10.10

7.3.0-10.10

ubuntu/linux-aws<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-azure<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-azure-fde<7.3.0-1004.5

7.3.0-1004.5

ubuntu/linux-gcp<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-oracle<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-raspi<7.3.0-1004.4

7.3.0-1004.4

ubuntu/linux-realtime<7.3.0-10.10.1

7.3.0-10.10.1

ubuntu/linux-riscv<7.3.0-10.10.1

7.3.0-10.10.1

ubuntu/linux<7.0.0-43.43

7.0.0-43.43

ubuntu/linux-aws<7.0.0-1017.18

7.0.0-1017.18

ubuntu/linux-azure<7.0.0-1020.21

7.0.0-1020.21

ubuntu/linux-azure-fde<7.0.0-1019.19

7.0.0-1019.19

ubuntu/linux-gcp<7.0.0-1017.19

7.0.0-1017.19

ubuntu/linux-gke<7.0.0-1010.11

7.0.0-1010.11

ubuntu/linux-ibm<7.0.0-1018.18

7.0.0-1018.18

ubuntu/linux-nvidia*

ubuntu/linux-nvidia-bos*

ubuntu/linux-oem-7.0<7.0.0-1018.18

7.0.0-1018.18

ubuntu/linux-oracle<7.0.0-1016.18

7.0.0-1016.18

ubuntu/linux-raspi<7.0.0-1023.23

7.0.0-1023.23

ubuntu/linux-realtime<7.0.0-43.43.1

7.0.0-43.43.1

ubuntu/linux-riscv*

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 6.12.113
Upgrade
Upgrade linux/Kernel to a version that resolves this vulnerability.
Fixed in 6.18.57
Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1069.74~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1073.82~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1071.78~22.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1073.81~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1069.70~22.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-149.149.1~22.04.1
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1067.71~22.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-149.149~22.04.2
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1064.65~22.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-149.149
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1069.74
Upgrade
Upgrade ubuntu/linux-aws-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.18~24.04.1
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1073.82
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 6.8.0-1071.78
Upgrade
Upgrade ubuntu/linux-azure-fde-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1019.19~24.04.1
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1073.81
Upgrade
Upgrade ubuntu/linux-gcp-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.19~24.04.1
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1068.77
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1053.57
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1069.70
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-149.149.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1067.70
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1067.70.1
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1067.71
Upgrade
Upgrade ubuntu/linux-oracle-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1016.18~24.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1068.72
Upgrade
Upgrade ubuntu/linux-riscv-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-43.43.1~24.04.2
Upgrade
Upgrade ubuntu/linux-vmware to a version that resolves this vulnerability.
Fixed in 6.8.0-1010.10
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 6.8.0-1036.41
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2056.58
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1064.65
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1069.74+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1073.82+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1073.81+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 7.3.0-10.10
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.5
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 7.3.0-1004.4
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 7.3.0-10.10.1
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 7.3.0-10.10.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 7.0.0-43.43
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.18
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 7.0.0-1020.21
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 7.0.0-1019.19
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 7.0.0-1017.19
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 7.0.0-1010.11
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 7.0.0-1018.18
Upgrade
Upgrade ubuntu/linux-oem-7.0 to a version that resolves this vulnerability.
Fixed in 7.0.0-1018.18
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 7.0.0-1016.18
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 7.0.0-1023.23
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 7.0.0-43.43.1

Event History

Oct 23, 2026

CVE Published

via MITRE·12:20 PM

Data Sourced

via MITRE·12:20 PM

DescriptionSeverity

Data Sourced

via OSV·12:20 PM

DescriptionSeverityAffected Software

Data Sourced

via NVD·01:17 PM

DescriptionSeverity

Frequently Asked Questions

What conditions are required to trigger the issue?

Two concurrent listen() calls must be made on the same Bluetooth ISO broadcast socket while it is in the BT_BOUND state. The race exists because the socket lock is dropped before BIS listener setup and the state was not rechecked after both relevant locks were acquired.

What can happen if the race is triggered?

The second listener setup can overwrite the socket's connection pointer, leaking the first connection reference while that first connection still points to the socket. After the socket is torn down through the second connection, later events on the first connection can access a stale socket and cause a use-after-free.

How does the resolved code prevent concurrent setup?

It rechecks that the socket remains BT_BOUND and verifies that its connection pointer is NULL after acquiring both the HCI device and socket locks. A competing setup is rejected with -EBADFD before another connection is allocated.

CVE-2026-99013: Bluetooth: ISO: Reject concurrent BIS listener setup

Affected Software

Remediation

Event History

Frequently Asked Questions

What conditions are required to trigger the issue?

What can happen if the race is triggered?

How does the resolved code prevent concurrent setup?

Company

Resources

Contact