Bugzilla – Bug 1180460
VUL-1: CVE-2020-35499: kernel-source: bluetooth crash when using BT_SNDMTU/BT_RCVMTU option
Last modified: 2021-02-02 12:44:43 UTC
Upstream fix: commit f6b8c6b55439 ("Bluetooth: sco: Fix crash when using BT_SNDMTU/BT_RCVMTU option")
It is unknown whether this can be actually triggered via Bluetooth. The PoC only crashes itself, with no apparent impact on kernel functionality. If it turns out this is indeed the case, we can file a dispute for the CVE.
(In reply to Wolfgang Frisch from comment #2) > It is unknown whether this can be actually triggered via Bluetooth. The PoC > only crashes itself, with no apparent impact on kernel functionality. If it > turns out this is indeed the case, we can file a dispute for the CVE. > Upstream fix: commit f6b8c6b55439 ("Bluetooth: sco: Fix crash when using BT_SNDMTU/BT_RCVMTU option") This patch apply on v5.11-rc1 and fixing is based on 0fc1a726f897 Bluetooth: sco: new getsockopt options BT_SNDMTU/BT_RCVMTU (v5.10-rc1) master: has it stable: affected 15sp2: not affected cve/linux-4.12: not affected cve/linux-4.4: not affected cve/linux-3.0: not affected cve/linux-2.6.32: not affected
is public
(In reply to Al Cho from comment #3) > (In reply to Wolfgang Frisch from comment #2) > > It is unknown whether this can be actually triggered via Bluetooth. The PoC > > only crashes itself, with no apparent impact on kernel functionality. If it > > turns out this is indeed the case, we can file a dispute for the CVE. > > > Upstream fix: commit f6b8c6b55439 ("Bluetooth: sco: Fix crash when using > BT_SNDMTU/BT_RCVMTU option") > > This patch apply on v5.11-rc1 > > and fixing is based on 0fc1a726f897 Bluetooth: sco: new getsockopt options > BT_SNDMTU/BT_RCVMTU (v5.10-rc1) > > master: has it > stable: affected already fixed/patched by 84f94bc8377d8ec8a7cc2b8b48c5b5a301b52364 at Wed Dec 30 13:26:17 2020 patches.kernel.org/5.10.4-337-Bluetooth-sco-Fix-crash-when-using-BT_SNDMTU-B.patch - Bluetooth: sco: Fix crash when using BT_SNDMTU/BT_RCVMTU option (bsc#1012628). > 15sp2: not affected > cve/linux-4.12: not affected > cve/linux-4.4: not affected > cve/linux-3.0: not affected > cve/linux-2.6.32: not affected
-> fixed upstream