CVE-2024-36968: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()

Published Jun 8, 2024
·
Updated

Bluetooth: L2CAP: Fix div-by-zero in l2capleflowctlinit()

Affected Software

10 affected componentsFixes available
Linux Linux kernel>=2.6.39<6.6.32
Linux Linux kernel>=6.7<6.8.11
Linux Linux kernel>=6.9<6.9.2
debian/linux<=5.10.223-1, <=5.10.234-1, <=6.1.129-1, <=6.1.135-1
6.12.27-1
redhat/kernel<6.6.32
6.6.32
redhat/kernel<6.8.11
6.8.11
redhat/kernel<6.9.2
6.9.2
redhat/kernel<6.10
6.10
Microsoft azl3 kernel 6.6.22.1-2
Microsoft azl3 kernel 6.6.35.1-5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.27-1
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.6.32
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.8.11
  4. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.9.2
  5. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.10
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch CVE-2024-36968
  7. Configuration

    Implement the missing validation in read_buffer_size() used by l2cap_le_flowctl_init() and make read_buffer_size() return an error value if the validation fails, to prevent div-by-zero and integer overflow when MTU values are out of range.

    Linux kernel Bluetooth L2CAP (net/bluetooth/l2cap_core.c: l2cap_le_flowctl_init/read_buffer_size) Add missing validation in read_buffer_size() and return an error value when validation fails = error value on validation failure
  8. Configuration

    Update the Bluetooth stack so MTU is moved from hci_dev to hci_conn, validate MTU during hci_conn_add(), and stop the connection process earlier if MTU is invalid (hci_conn_add() returns ERR_PTR()).

    Linux kernel Bluetooth HCI connection management (hci_conn_add()/MTU handling) Move MTU from hci_dev to hci_conn to validate MTU and stop the connection earlier if MTU is invalid = MTU validated in hci_conn instead of hci_dev; stop connection earlier on invalid MTU

Event History

Jun 8, 2024
CVE Published
via MITRE·12:53 PM
Data Sourced
via MITRE·12:53 PM
DescriptionSeverity
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 14, 2024
Data Sourced
via Red Hat·03:49 AM
DescriptionSeverityAffected Software
Aug 8, 2024
Data Sourced
via Launchpad·11:27 PM
Description
Sep 11, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Apr 27, 2025
Data Sourced
via Ubuntu·12:27 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-36968?

CVE-2024-36968 is classified as a critical vulnerability due to the potential for a div-by-zero and integer overflow affecting system stability.

2

How do I fix CVE-2024-36968?

To mitigate CVE-2024-36968, update your Linux kernel to version 6.12.12-1 or later.

3

Which Linux kernel versions are affected by CVE-2024-36968?

CVE-2024-36968 affects Linux kernel versions from 2.6.39 up to 6.6.32 and from 6.7 to 6.8.11.

4

What type of systems are impacted by CVE-2024-36968?

CVE-2024-36968 impacts systems running vulnerable versions of the Linux kernel, particularly those using Bluetooth functionalities.

5

Is CVE-2024-36968 related to Bluetooth functionality?

Yes, CVE-2024-36968 specifically relates to vulnerabilities in the Bluetooth L2CAP layer of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203