Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 2 weeks, 6 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
Bluetooth: RFCOMM: validate skb length in MCC handlers

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: validate skb length in MCC handlers The RFCOMM MCC handlers cast skb->data to protocol-specific structs without validating skb->len first. A malicious remote device can send truncated MCC frames and trigger out-of-bounds reads in these handlers. Fix this by using skb_pull_data() to validate and access the required data before dereferencing it. rfcomm_recv_rpn() requires special handling since ETSI TS 07.10 allows 1-byte RPN requests. Handle this by validating only the DLCI byte first, and validating the full struct only when len > 1.

Affected products

Linux
  • <23882b828c3c8c51d0c946446a396b10abb3b16b
  • ==2.6.12
  • =<6.18.*
  • <3eabc6d47a0ad22b053329997aaf0ec1e581e392
  • =<6.1.*
  • =<6.6.*
  • <1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c
  • =<5.15.*
  • =<6.12.*
  • <0d637136ce89f9a2309b2c3502402ce400dab0ef
  • <08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997
  • =<7.0.*
  • <98377e6b1a1a56561ec66a181573ea2b61b2079e
  • <7c15c7c2878957cbfed93bcc29c13fdace464254
  • <2.6.12
  • =<*