CVE-2020-11494: Medium severity Linux Linux kernel vulnerability

Published Apr 2, 2020
·
Updated

An issue was discovered in slcbump in drivers/net/can/slcan.c in the Linux kernel 3.16 through 5.6.2. It allows attackers to read uninitialized canframe data, potentially containing sensitive information from kernel stack memory, if the configuration lacks CONFIGINITSTACKALL, aka CID-b9258a2cece4.

Affected Software

66 affected componentsFixes available
Linux Linux kernel>=3.16<=5.6.2
openSUSE Leap=15.1
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.10
ubuntu/linux-aws<4.4.0-1067.71
4.4.0-1067.71
ubuntu/linux-azure<4.15.0-1083.93~14.04.1
4.15.0-1083.93~14.04.1
ubuntu/linux-lts-xenial<4.4.0-179.209~14.04.1
4.4.0-179.209~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-179.209
4.4.0-179.209
ubuntu/linux-aws<4.4.0-1107.118
4.4.0-1107.118
ubuntu/linux-aws-hwe<4.15.0-1067.71~16.04.1
4.15.0-1067.71~16.04.1
ubuntu/linux-azure<4.15.0-1083.93~16.04.1
4.15.0-1083.93~16.04.1
ubuntu/linux-gcp<4.15.0-1071.81~16.04.1
4.15.0-1071.81~16.04.1
ubuntu/linux-hwe<4.15.0-101.102~16.04.1
4.15.0-101.102~16.04.1
ubuntu/linux-kvm<4.4.0-1071.78
4.4.0-1071.78
ubuntu/linux-oracle<4.15.0-1039.43~16.04.1
4.15.0-1039.43~16.04.1
ubuntu/linux-raspi2<4.4.0-1133.142
4.4.0-1133.142
ubuntu/linux-snapdragon<4.4.0-1137.145
4.4.0-1137.145
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1034.39
4.4.0-1034.39
ubuntu/linux-fips*
ubuntu/linux<4.15.0-101.102
4.15.0-101.102
ubuntu/linux-aws<4.15.0-1067.71
4.15.0-1067.71
ubuntu/linux-aws-5.3<5.3.0-1019.21~18.04.1
5.3.0-1019.21~18.04.1
ubuntu/linux-azure-4.15<4.15.0-1083.93
4.15.0-1083.93
ubuntu/linux-azure-5.3<5.3.0-1022.23~18.04.1
5.3.0-1022.23~18.04.1
ubuntu/linux-gcp-5.3<5.3.0-1020.22~18.04.1
5.3.0-1020.22~18.04.1
ubuntu/linux-gke-4.15<4.15.0-1059.62
4.15.0-1059.62
ubuntu/linux-gke-5.0<5.0.0-1037.38
5.0.0-1037.38
ubuntu/linux-gke-5.3<5.3.0-1020.22~18.04.1
5.3.0-1020.22~18.04.1
ubuntu/linux-hwe<5.3.0-53.47~18.04.1
5.3.0-53.47~18.04.1
ubuntu/linux-kvm<4.15.0-1060.61
4.15.0-1060.61
ubuntu/linux-oem<4.15.0-1081.91
4.15.0-1081.91
ubuntu/linux-oem-osp1<5.0.0-1052.57
5.0.0-1052.57
ubuntu/linux-oracle<4.15.0-1039.43
4.15.0-1039.43
ubuntu/linux-oracle-5.3<5.3.0-1018.20~18.04.1
5.3.0-1018.20~18.04.1
ubuntu/linux-raspi2<4.15.0-1062.66
4.15.0-1062.66
ubuntu/linux-raspi2-5.3<5.3.0-1026.28~18.04.1
5.3.0-1026.28~18.04.1
ubuntu/linux-snapdragon<4.15.0-1079.86
4.15.0-1079.86
ubuntu/linux-aws-5.0*
ubuntu/linux-azure*
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-edge*
ubuntu/linux-hwe-edge*
ubuntu/linux-oracle-5.0*
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-fips<4.15.0-1029.34
4.15.0-1029.34
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-oem-5.6<5.6.0-1008.8
5.6.0-1008.8
ubuntu/linux-raspi<5.4.0-1011.11
5.4.0-1011.11
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*
debian/linux
6.1.176-16.1.190-16.12.107-16.12.116-17.2.15-17.3.3-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 4.4.0-1067.71
  2. Upgrade

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

    Fixed in 4.15.0-1083.93~14.04.1
  3. Upgrade

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

    Fixed in 4.4.0-179.209~14.04.1
  4. Upgrade

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

    Fixed in 4.4.0-179.209
  5. Upgrade

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

    Fixed in 4.4.0-1107.118
  6. Upgrade

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

    Fixed in 4.15.0-1067.71~16.04.1
  7. Upgrade

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

    Fixed in 4.15.0-1083.93~16.04.1
  8. Upgrade

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

    Fixed in 4.15.0-1071.81~16.04.1
  9. Upgrade

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

    Fixed in 4.15.0-101.102~16.04.1
  10. Upgrade

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

    Fixed in 4.4.0-1071.78
  11. Upgrade

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

    Fixed in 4.15.0-1039.43~16.04.1
  12. Upgrade

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

    Fixed in 4.4.0-1133.142
  13. Upgrade

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

    Fixed in 4.4.0-1137.145
  14. Upgrade

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

    Fixed in 4.4.0-1034.39
  15. Upgrade

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

    Fixed in 4.15.0-101.102
  16. Upgrade

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

    Fixed in 4.15.0-1067.71
  17. Upgrade

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

    Fixed in 5.3.0-1019.21~18.04.1
  18. Upgrade

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

    Fixed in 4.15.0-1083.93
  19. Upgrade

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

    Fixed in 5.3.0-1022.23~18.04.1
  20. Upgrade

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

    Fixed in 5.3.0-1020.22~18.04.1
  21. Upgrade

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

    Fixed in 4.15.0-1059.62
  22. Upgrade

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

    Fixed in 5.0.0-1037.38
  23. Upgrade

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

    Fixed in 5.3.0-1020.22~18.04.1
  24. Upgrade

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

    Fixed in 5.3.0-53.47~18.04.1
  25. Upgrade

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

    Fixed in 4.15.0-1060.61
  26. Upgrade

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

    Fixed in 4.15.0-1081.91
  27. Upgrade

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

    Fixed in 5.0.0-1052.57
  28. Upgrade

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

    Fixed in 4.15.0-1039.43
  29. Upgrade

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

    Fixed in 5.3.0-1018.20~18.04.1
  30. Upgrade

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

    Fixed in 4.15.0-1062.66
  31. Upgrade

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

    Fixed in 5.3.0-1026.28~18.04.1
  32. Upgrade

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

    Fixed in 4.15.0-1079.86
  33. Upgrade

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

    Fixed in 4.15.0-2018.18
  34. Upgrade

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

    Fixed in 4.15.0-2006.7
  35. Upgrade

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

    Fixed in 4.15.0-1029.34
  36. Upgrade

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

    Fixed in 5.6.0-1008.8
  37. Upgrade

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

    Fixed in 5.4.0-1011.11
  38. 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.116-1Fixed in 7.2.15-1Fixed in 7.3.3-1
  39. Configuration

    Enable CONFIG_INIT_STACK_ALL to prevent uninitialized can_frame data from being exposed through slc_bump.

    Linux kernel CONFIG_INIT_STACK_ALL = enabled

Event History

Apr 2, 2020
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·08:14 PM
Data Sourced
via MITRE·08:14 PM
Description
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:15 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-2020-11494?

CVE-2020-11494 is considered a security vulnerability that could potentially expose sensitive information.

2

How do I fix CVE-2020-11494?

To fix CVE-2020-11494, update the Linux kernel to a version newer than 5.6.2 or apply the recommended patches.

3

Which Linux distributions are affected by CVE-2020-11494?

CVE-2020-11494 affects Linux kernel versions from 3.16 to 5.6.2, impacting distributions such as openSUSE, Debian, and Ubuntu.

4

Can CVE-2020-11494 lead to data leakage?

Yes, CVE-2020-11494 allows attackers to read uninitialized can_frame data, which may contain sensitive information.

5

What specific kernel configuration is related to CVE-2020-11494?

CVE-2020-11494 is related to the lack of CONFIG_INIT_STACK_ALL in the kernel configuration.

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