Bug 2292324 (CVE-2024-36968)

Summary: CVE-2024-36968 kernel: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()
Product: [Other] Security Response Reporter: Pedro Sampaio <psampaio>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel 6.6.32, kernel 6.8.11, kernel 6.9.2, kernel 6.10-rc1 Doc Type: If docs needed, set a value
Doc Text:
in linux kernel bluetooth L2CAP, l2cap_le_flowctl_init() can cause both div-by-zero and an integer overflow since hdev->le_mtu may not fall in the valid range.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2293932    
Bug Blocks: 2292332    

Description Pedro Sampaio 2024-06-14 03:49:18 UTC
In the Linux kernel, the following vulnerability has been resolved:

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

The Linux kernel CVE team has assigned CVE-2024-36968 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024060804-CVE-2024-36968-6d78@gregkh/T

Comment 14 Keith Grant 2024-06-24 13:05:12 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2293932]

Comment 15 errata-xmlrpc 2025-05-13 08:24:38 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:6966 https://access.redhat.com/errata/RHSA-2025:6966