CVE-2020-10720: Use After Free

Published Dec 9, 2019
·
Updated

A flaw was found in the Linux kernel's implementation of GRO in versions before 5.2. This flaw allows an attacker with local access to crash the system.

Other sources

A flaw was found in the Linux kernel’s implementation of GRO. This flaw allows an attacker with local access to crash the system.

If a network driver provides to napigrofrags() an skb with a page fragment of exactly 14 bytes, the call to gropullfromfrag0() will 'consume' the fragment by calling skbfragunref(skb, 0), and the page might be freed and reused. Reading eth->hproto at the end of napifragsskb() might read mangled data, or crash under specific debugging features.

It is possible that an attacker who is able to trigger this situation may be able to crash the system. The upstream description describes this flaw as a use-after-free, it appears that this is only able to be triggered as a denial of service but other effects look unlikely although this has not been fully investigated.

External References:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a4270d6795b0580287453ea55974d948393e66ef

— Red Hat

Affected Software

52 affected componentsFixes available
redhat/kernel-alt<0:4.14.0-115.26.1.el7a
0:4.14.0-115.26.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
redhat/kernel<5.2
5.2
Linux Linux kernel<5.2
ubuntu/linux-aws<4.4.0-1054.58
4.4.0-1054.58
ubuntu/linux-azure<4.15.0-1059.64~14.04.1
4.15.0-1059.64~14.04.1
ubuntu/linux-lts-xenial<4.4.0-164.192~14.04.1
4.4.0-164.192~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-157.185
4.4.0-157.185
ubuntu/linux-aws<4.4.0-1090.101
4.4.0-1090.101
ubuntu/linux-aws-hwe<4.15.0-1047.49~16.04.1
4.15.0-1047.49~16.04.1
ubuntu/linux-azure<4.15.0-1056.61
4.15.0-1056.61
ubuntu/linux-gcp<4.15.0-1041.43
4.15.0-1041.43
ubuntu/linux-hwe<4.15.0-60.67~16.04.1
4.15.0-60.67~16.04.1
ubuntu/linux-kvm<4.4.0-1052.59
4.4.0-1052.59
ubuntu/linux-oracle<4.15.0-1022.25~16.04.1
4.15.0-1022.25~16.04.1
ubuntu/linux-raspi2<4.4.0-1117.126
4.4.0-1117.126
ubuntu/linux-snapdragon<4.4.0-1121.127
4.4.0-1121.127
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1015.20
4.4.0-1015.20
ubuntu/linux<4.15.0-60.67
4.15.0-60.67
ubuntu/linux-aws<4.15.0-1047.49
4.15.0-1047.49
ubuntu/linux-gke-4.15<4.15.0-1041.43
4.15.0-1041.43
ubuntu/linux-gke-5.0<5.0.0-1015.15~18.04.1
5.0.0-1015.15~18.04.1
ubuntu/linux-hwe<5.0.0-27.28~18.04.1
5.0.0-27.28~18.04.1
ubuntu/linux-hwe-edge<5.3.0-19.20~18.04.2
5.3.0-19.20~18.04.2
ubuntu/linux-kvm<4.15.0-1043.43
4.15.0-1043.43
ubuntu/linux-oem<4.15.0-1056.65
4.15.0-1056.65
ubuntu/linux-oem-osp1<5.0.0-1020.22
5.0.0-1020.22
ubuntu/linux-oracle<4.15.0-1022.25
4.15.0-1022.25
ubuntu/linux-raspi2<4.15.0-1044.47
4.15.0-1044.47
ubuntu/linux-snapdragon<4.15.0-1062.69
4.15.0-1062.69
ubuntu/linux-aws-5.0*
ubuntu/linux-azure*
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-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-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-alt to a version that resolves this vulnerability.

    Fixed in 0:4.14.0-115.26.1.el7a
  2. Upgrade

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

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

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

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

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

    Fixed in 5.2
  5. Upgrade

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

    Fixed in 4.4.0-1054.58
  6. Upgrade

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

    Fixed in 4.15.0-1059.64~14.04.1
  7. Upgrade

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

    Fixed in 4.4.0-164.192~14.04.1
  8. Upgrade

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

    Fixed in 4.4.0-157.185
  9. Upgrade

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

    Fixed in 4.4.0-1090.101
  10. Upgrade

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

    Fixed in 4.15.0-1047.49~16.04.1
  11. Upgrade

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

    Fixed in 4.15.0-1056.61
  12. Upgrade

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

    Fixed in 4.15.0-1041.43
  13. Upgrade

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

    Fixed in 4.15.0-60.67~16.04.1
  14. Upgrade

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

    Fixed in 4.4.0-1052.59
  15. Upgrade

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

    Fixed in 4.15.0-1022.25~16.04.1
  16. Upgrade

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

    Fixed in 4.4.0-1117.126
  17. Upgrade

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

    Fixed in 4.4.0-1121.127
  18. Upgrade

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

    Fixed in 4.4.0-1015.20
  19. Upgrade

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

    Fixed in 4.15.0-60.67
  20. Upgrade

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

    Fixed in 4.15.0-1047.49
  21. Upgrade

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

    Fixed in 4.15.0-1041.43
  22. Upgrade

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

    Fixed in 5.0.0-1015.15~18.04.1
  23. Upgrade

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

    Fixed in 5.0.0-27.28~18.04.1
  24. Upgrade

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

    Fixed in 5.3.0-19.20~18.04.2
  25. Upgrade

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

    Fixed in 4.15.0-1043.43
  26. Upgrade

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

    Fixed in 4.15.0-1056.65
  27. Upgrade

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

    Fixed in 5.0.0-1020.22
  28. Upgrade

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

    Fixed in 4.15.0-1022.25
  29. Upgrade

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

    Fixed in 4.15.0-1044.47
  30. Upgrade

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

    Fixed in 4.15.0-1062.69
  31. Upgrade

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

    Fixed in 4.15.0-2018.18
  32. Upgrade

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

    Fixed in 4.15.0-2006.7
  33. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 5.2
  34. Configuration

    Disable GSO on the network cards using ethtool to prevent the vulnerable code path from being taken

    Network interface cards GSO = disabled

Event History

Dec 9, 2019
CVE Published
02:23 PM
Sep 3, 2020
CVE Published
via MITRE·05:49 PM
Data Sourced
via MITRE·05:49 PM
DescriptionWeakness
Data Sourced
via OSV·06:15 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which systems should be prioritized for review?

Review systems running Linux kernel versions before 5.2, particularly deployments using the listed Ubuntu kernel packages (linux, linux-aws, linux-azure, linux-gcp, linux-hwe, linux-kvm, or linux-raspi2) or the Red Hat kernel package.

2

What access or conditions are needed to trigger the issue?

The issue is described as requiring local access and the ability to cause a network driver to pass napi_gro_frags() an skb containing a page fragment exactly 14 bytes long. Exploitation is characterized as difficult and may require user interaction according to the supplied severity vector.

3

What is the expected impact if exploitation succeeds?

The documented impact is a system crash, resulting in denial of service. Although the upstream description identifies a use-after-free, the available information says other impacts appear unlikely and have not been fully investigated.

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