CVE-2019-3460: Infoleak

Published Jan 3, 2019
·
Updated

A flaw was found in the Linux kernel's implementation of logical link control and adaptation protocol (L2CAP), part of the Bluetooth stack in the l2capparseconfrsp and l2capparseconfreq functions. An attacker with physical access within the range of standard Bluetooth transmission can create a specially crafted packet. The response to this specially crafted packet can contain part of the kernel stack which can be used in a further attack.

Other sources

A flaw was found in the Linux kernels implementation of Logical link control and adaptation protocol (L2CAP), part of the bluetooth stack in the l2capparseconfrsp, l2capparseconfreq functions.

An attacker with physical access within the range of standard bluetooth transmission can create a specially crafted packet. The response to this specially crafted packet can contain part of the kernel stack which can be used in a further attack.

Upstream patch: https://lore.kernel.org/linux-bluetooth/20190110062833.GA15047@kroah.com/

Oss-security post: https://seclists.org/oss-sec/2019/q1/58

Mitigation:

- Disabling the bluetooth hardware in the bios. - Prevent loading of the bluetooth kernel modules. - Disable the bluetooth connection by putting the system in "airport" mode.

— Red Hat

A heap data infoleak in multiple locations including L2CAPPARSECONFRSP was found in the Linux kernel before 5.1-rc1.

— Ubuntu

Affected Software

72 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1062.rt56.1022.el7
0:3.10.0-1062.rt56.1022.el7
redhat/kernel<0:3.10.0-1062.el7
0:3.10.0-1062.el7
redhat/kernel-alt<0:4.14.0-115.18.1.el7a
0:4.14.0-115.18.1.el7a
redhat/kernel-rt<0:4.18.0-147.rt24.93.el8
0:4.18.0-147.rt24.93.el8
redhat/kernel<0:4.18.0-147.el8
0:4.18.0-147.el8
Linux Linux kernel<=5.1
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
Debian Debian Linux=8.0
redhat Codeready Linux Builder=8.0
redhat Virtualization Host=4.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Eus=8.1
redhat Enterprise Linux Eus=8.2
redhat Enterprise Linux Eus=8.4
redhat Enterprise Linux For Real Time=7
redhat Enterprise Linux For Real Time=8
redhat Enterprise Linux For Real Time For Nfv=7
redhat Enterprise Linux For Real Time For Nfv=8
redhat Enterprise Linux For Real Time For Nfv Tus=8.2
redhat Enterprise Linux For Real Time For Nfv Tus=8.4
redhat Enterprise Linux For Real Time Tus=8.2
redhat Enterprise Linux For Real Time Tus=8.4
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=8.2
redhat Enterprise Linux Server Aus=8.4
redhat Enterprise Linux Server Tus=8.2
redhat Enterprise Linux Server Tus=8.4
redhat Enterprise Linux Workstation=7.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1
ubuntu/linux<3.13.0-168.218
3.13.0-168.218
ubuntu/linux-aws<4.4.0-1040.43
4.4.0-1040.43
ubuntu/linux-azure<4.15.0-1041.45~14.04.1
4.15.0-1041.45~14.04.1
ubuntu/linux-lts-xenial<4.4.0-144.170~14.04.1
4.4.0-144.170~14.04.1
ubuntu/linux<4.4.0-145.171
4.4.0-145.171
ubuntu/linux-aws<4.4.0-1079.89
4.4.0-1079.89
ubuntu/linux-aws-hwe<4.15.0-1035.37~16.04.1
4.15.0-1035.37~16.04.1
ubuntu/linux-azure<4.15.0-1041.45
4.15.0-1041.45
ubuntu/linux-gcp<4.15.0-1029.31~16.04.1
4.15.0-1029.31~16.04.1
ubuntu/linux-hwe<4.15.0-47.50~16.04.1
4.15.0-47.50~16.04.1
ubuntu/linux-kvm<4.4.0-1043.49
4.4.0-1043.49
ubuntu/linux-oracle<4.15.0-1010.12~16.04.1
4.15.0-1010.12~16.04.1
ubuntu/linux-raspi2<4.4.0-1106.114
4.4.0-1106.114
ubuntu/linux-snapdragon<4.4.0-1110.115
4.4.0-1110.115
ubuntu/linux-fips<4.4.0-1008.10
4.4.0-1008.10
ubuntu/linux<4.15.0-47.50
4.15.0-47.50
ubuntu/linux-aws<4.15.0-1035.37
4.15.0-1035.37
ubuntu/linux-azure<4.18.0-1014.14~18.04.1
4.18.0-1014.14~18.04.1
ubuntu/linux-gcp<4.15.0-1029.31
4.15.0-1029.31
ubuntu/linux-gcp-edge<4.18.0-1008.9~18.04.1
4.18.0-1008.9~18.04.1
ubuntu/linux-hwe<4.18.0-17.18~18.04.1
4.18.0-17.18~18.04.1
ubuntu/linux-kvm<4.15.0-1031.31
4.15.0-1031.31
ubuntu/linux-oem<4.15.0-1035.40
4.15.0-1035.40
ubuntu/linux-oracle<4.15.0-1010.12
4.15.0-1010.12
ubuntu/linux-raspi2<4.15.0-1033.35
4.15.0-1033.35
ubuntu/linux-snapdragon<4.15.0-1053.57
4.15.0-1053.57
ubuntu/linux-azure-fde*
ubuntu/linux-azure-fde-5.15*
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-raspi-realtime*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 0:3.10.0-1062.rt56.1022.el7
  2. Upgrade

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

    Fixed in 0:3.10.0-1062.el7
  3. Upgrade

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

    Fixed in 0:4.14.0-115.18.1.el7a
  4. Upgrade

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

    Fixed in 0:4.18.0-147.rt24.93.el8
  5. Upgrade

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

    Fixed in 0:4.18.0-147.el8
  6. Upgrade

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

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  7. Upgrade

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

    Fixed in 3.13.0-168.218
  8. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.4.0-1040.43
  9. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1041.45~14.04.1
  10. Upgrade

    Upgrade ubuntu/linux-lts-xenial to a version that resolves this vulnerability.

    Fixed in 4.4.0-144.170~14.04.1
  11. Upgrade

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

    Fixed in 4.4.0-145.171
  12. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.4.0-1079.89
  13. Upgrade

    Upgrade ubuntu/linux-aws-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-1035.37~16.04.1
  14. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1041.45
  15. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 4.15.0-1029.31~16.04.1
  16. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-47.50~16.04.1
  17. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 4.4.0-1043.49
  18. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 4.15.0-1010.12~16.04.1
  19. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.4.0-1106.114
  20. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.4.0-1110.115
  21. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 4.4.0-1008.10
  22. Upgrade

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

    Fixed in 4.15.0-47.50
  23. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.15.0-1035.37
  24. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.18.0-1014.14~18.04.1
  25. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 4.15.0-1029.31
  26. Upgrade

    Upgrade ubuntu/linux-gcp-edge to a version that resolves this vulnerability.

    Fixed in 4.18.0-1008.9~18.04.1
  27. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 4.18.0-17.18~18.04.1
  28. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 4.15.0-1031.31
  29. Upgrade

    Upgrade ubuntu/linux-oem to a version that resolves this vulnerability.

    Fixed in 4.15.0-1035.40
  30. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 4.15.0-1010.12
  31. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1033.35
  32. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.15.0-1053.57
  33. Configuration

    Disable Bluetooth by putting the system in "airport" mode, disabling the Bluetooth hardware in the BIOS, or preventing the Bluetooth kernel modules from loading.

    Linux Bluetooth stack Bluetooth availability = disabled

Event History

Jan 3, 2019
Data Sourced
via Red Hat·11:28 AM
DescriptionSeverityAffected Software
Jan 11, 2019
CVE Published
12:00 AM
Jan 14, 2019
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
Apr 11, 2019
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionWeakness
Data Sourced
via NVD·04:29 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2019-3460?

The severity of CVE-2019-3460 is classified as high due to the potential for an attacker to exploit Bluetooth functionalities.

2

How do I fix CVE-2019-3460?

To fix CVE-2019-3460, update your Linux kernel to versions 0:3.10.0-1062.rt56.1022.el7, 0:3.10.0-1062.el7, or other specified remedial versions.

3

Which systems are affected by CVE-2019-3460?

CVE-2019-3460 affects various Linux distributions including Red Hat, Ubuntu, and Debian, specifically certain kernel versions.

4

Can I be attacked through CVE-2019-3460 if my Bluetooth is turned off?

If Bluetooth is turned off, the vulnerability exploited by CVE-2019-3460 cannot be triggered, but keeping software updated is still recommended.

5

What types of attacks are possible with CVE-2019-3460?

CVE-2019-3460 can allow an attacker within Bluetooth range to conduct man-in-the-middle attacks or potentially execute arbitrary code.

Company

Resources

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