CVE-2019-19533: Infoleak

Published Aug 21, 2019
·
Updated

An information leak flaw was found in the Linux kernel's USB digital video device driver. An attacker with a malicious USB device presenting itself as a 'Technotrend/Hauppauge USB DEC' device is able to issue commands to this specific device and leak kernel internal memory information. The highest threat from this vulnerability is a breach of data confidentiality.

Other sources

An information leak ina driver in the Linux kernel was found which can be exploited by malicious USB device being attached presenting itself as "Technotrend/Hauppauge USB DEC" device.

A local attacker who is able to issue commands to this specific device is able to leak kernel internal memory information.

Upstream Patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1

References:

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.4 http://seclists.org/oss-sec/2019/q4/115 http://www.openwall.com/lists/oss-security/2019/12/03/4

— Red Hat

In the Linux kernel before 5.3.4, there is an info-leak bug that can be caused by a malicious USB device in the drivers/media/usb/ttusb-dec/ttusbdec.c driver, aka CID-a10feaf8c464.

Affected Software

49 affected componentsFixes available
redhat/kernel-rt<0:4.18.0-240.rt7.54.el8
0:4.18.0-240.rt7.54.el8
redhat/kernel<0:4.18.0-240.el8
0:4.18.0-240.el8
Linux Linux kernel<5.3.4
ubuntu/linux-aws<4.4.0-1058.62
4.4.0-1058.62
ubuntu/linux-azure<4.15.0-1063.68~14.04.1
4.15.0-1063.68~14.04.1
ubuntu/linux-lts-xenial<4.4.0-168.197~14.04.1
4.4.0-168.197~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-168.197
4.4.0-168.197
ubuntu/linux-aws<4.4.0-1098.109
4.4.0-1098.109
ubuntu/linux-aws-hwe<4.15.0-1054.56~16.04.1
4.15.0-1054.56~16.04.1
ubuntu/linux-azure<4.15.0-1063.68
4.15.0-1063.68
ubuntu/linux-gcp<4.15.0-1049.52
4.15.0-1049.52
ubuntu/linux-hwe<4.15.0-69.78~16.04.1
4.15.0-69.78~16.04.1
ubuntu/linux-kvm<4.4.0-1062.69
4.4.0-1062.69
ubuntu/linux-oracle<4.15.0-1029.32~16.04.1
4.15.0-1029.32~16.04.1
ubuntu/linux-raspi2<4.4.0-1125.134
4.4.0-1125.134
ubuntu/linux-snapdragon<4.4.0-1129.137
4.4.0-1129.137
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1025.30
4.4.0-1025.30
ubuntu/linux-fips*
ubuntu/linux<4.15.0-69.78
4.15.0-69.78
ubuntu/linux-aws<4.15.0-1054.56
4.15.0-1054.56
ubuntu/linux-azure<5.0.0-1025.27~18.04.1
5.0.0-1025.27~18.04.1
ubuntu/linux-gcp<5.0.0-1025.26~18.04.1
5.0.0-1025.26~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1048.51
4.15.0-1048.51
ubuntu/linux-gke-5.0<5.0.0-1025.26~18.04.1
5.0.0-1025.26~18.04.1
ubuntu/linux-hwe<5.0.0-35.38~18.04.1
5.0.0-35.38~18.04.1
ubuntu/linux-kvm<4.15.0-1050.50
4.15.0-1050.50
ubuntu/linux-oem<4.15.0-1063.72
4.15.0-1063.72
ubuntu/linux-oem-osp1<5.0.0-1027.31
5.0.0-1027.31
ubuntu/linux-oracle<4.15.0-1029.32
4.15.0-1029.32
ubuntu/linux-raspi2<4.15.0-1050.54
4.15.0-1050.54
ubuntu/linux-snapdragon<4.15.0-1067.74
4.15.0-1067.74
ubuntu/linux-azure-edge*
ubuntu/linux-gcp-edge*
ubuntu/linux-hwe-edge*
ubuntu/linux-aws-fips<4.15.0-2018.18
4.15.0-2018.18
ubuntu/linux-azure-fips<4.15.0-2006.7
4.15.0-2006.7
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-azure-fde*
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-raspi-realtime*
ubuntu/linux-vmware*

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:4.18.0-240.rt7.54.el8
  2. Upgrade

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

    Fixed in 0:4.18.0-240.el8
  3. Upgrade

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

    Fixed in 4.4.0-1058.62
  4. Upgrade

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

    Fixed in 4.15.0-1063.68~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-168.197~14.04.1
  6. Upgrade

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

    Fixed in 4.4.0-168.197
  7. Upgrade

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

    Fixed in 4.4.0-1098.109
  8. Upgrade

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

    Fixed in 4.15.0-1054.56~16.04.1
  9. Upgrade

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

    Fixed in 4.15.0-1063.68
  10. Upgrade

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

    Fixed in 4.15.0-1049.52
  11. Upgrade

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

    Fixed in 4.15.0-69.78~16.04.1
  12. Upgrade

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

    Fixed in 4.4.0-1062.69
  13. Upgrade

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

    Fixed in 4.15.0-1029.32~16.04.1
  14. Upgrade

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

    Fixed in 4.4.0-1125.134
  15. Upgrade

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

    Fixed in 4.4.0-1129.137
  16. Upgrade

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

    Fixed in 4.4.0-1025.30
  17. Upgrade

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

    Fixed in 4.15.0-69.78
  18. Upgrade

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

    Fixed in 4.15.0-1054.56
  19. Upgrade

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

    Fixed in 5.0.0-1025.27~18.04.1
  20. Upgrade

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

    Fixed in 5.0.0-1025.26~18.04.1
  21. Upgrade

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

    Fixed in 4.15.0-1048.51
  22. Upgrade

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

    Fixed in 5.0.0-1025.26~18.04.1
  23. Upgrade

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

    Fixed in 5.0.0-35.38~18.04.1
  24. Upgrade

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

    Fixed in 4.15.0-1050.50
  25. Upgrade

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

    Fixed in 4.15.0-1063.72
  26. Upgrade

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

    Fixed in 5.0.0-1027.31
  27. Upgrade

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

    Fixed in 4.15.0-1029.32
  28. Upgrade

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

    Fixed in 4.15.0-1050.54
  29. Upgrade

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

    Fixed in 4.15.0-1067.74
  30. Upgrade

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

    Fixed in 4.15.0-2018.18
  31. Upgrade

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

    Fixed in 4.15.0-2006.7
  32. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 5.3.4
  33. Configuration

    Add `install ttusb_dec /bin/true` to `/etc/modprobe.d/disable-cifs.conf` to prevent the module from loading.

    ttusb_dec kernel module module loading = /bin/true
  34. Operational

    Restart the system if the `ttusb_dec` module is already loaded.

Event History

Aug 21, 2019
CVE Published
12:00 AM
Dec 3, 2019
CVE Published
via MITRE·03:39 PM
Data Sourced
via MITRE·03:39 PM
Description
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Dec 13, 2019
Data Sourced
via Red Hat·09:26 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2019-19533?

CVE-2019-19533 has been assigned a medium severity rating indicating potential data exposure risks.

2

How do I fix CVE-2019-19533?

To address CVE-2019-19533, update to kernel version 0:4.18.0-240.rt7.54.el8 or 0:4.18.0-240.el8 or later.

3

What systems are affected by CVE-2019-19533?

CVE-2019-19533 affects Red Hat's kernel-rt and kernel packages on versions up to 0:4.18.0-240.el8.

4

What does CVE-2019-19533 exploit?

CVE-2019-19533 exploits an information leak in the Linux kernel's USB digital video device driver.

5

How can an attacker use CVE-2019-19533?

An attacker can use CVE-2019-19533 by presenting a malicious USB device to leak internal memory information from the kernel.

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