Description
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
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <7c15c7c2878957cbfed93bcc29c13fdace464254; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <0d637136ce89f9a2309b2c3502402ce400dab0ef; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <98377e6b1a1a56561ec66a181573ea2b61b2079e; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <3eabc6d47a0ad22b053329997aaf0ec1e581e392; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <23882b828c3c8c51d0c946446a396b10abb3b16b |
| Linux | Linux | 2.6.12; 0 to <2.6.12; 5.15.210 to <=5.15.*; 6.1.176 to <=6.1.*; 6.6.143 to <=6.6.*; 6.12.94 to <=6.12.*; 6.18.36 to <=6.18.*; 7.0.13 to <=7.0.*; 7.1 to <=* |
References
- https://git.kernel.org/stable/c/7c15c7c2878957cbfed93bcc29c13fdace464254
- https://git.kernel.org/stable/c/0d637136ce89f9a2309b2c3502402ce400dab0ef
- https://git.kernel.org/stable/c/98377e6b1a1a56561ec66a181573ea2b61b2079e
- https://git.kernel.org/stable/c/1b070ac9e99c2c2c3a8112943ca98ab6fca7f10c
- https://git.kernel.org/stable/c/3eabc6d47a0ad22b053329997aaf0ec1e581e392
- https://git.kernel.org/stable/c/08b9c1fbe78f4ad3f6250c6541cfaabdbeb81997
- https://git.kernel.org/stable/c/23882b828c3c8c51d0c946446a396b10abb3b16b
Generated from the official CVE List on 25 Jun 2026 10:14 UTC.