CVE-2022-49605: igc: Reinstate IGC_REMOVED logic and implement it properly

Published Feb 26, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

igc: Reinstate IGCREMOVED logic and implement it properly

The initially merged version of the igc driver code (via commit 146740f9abc4, "igc: Add support for PF") contained the following IGCREMOVED checks in the igcrd32/wr32() MMIO accessors:

u32 igcrd32(struct igchw hw, u32 reg) { u8 iomem hwaddr = READONCE(hw->hwaddr); u32 value = 0;

if (IGCREMOVED(hwaddr)) return ~value;

value = readl(&hwaddr[reg]);

/ reads should not return all F's / if (!(~value) && (!reg || !(~readl(hwaddr)))) hw->hwaddr = NULL;

return value; }

And:

#define wr32(reg, val) \ do { \ u8 iomem hwaddr = READONCE((hw)->hwaddr); \ if (!IGCREMOVED(hwaddr)) \ writel((val), &hwaddr[(reg)]); \ } while (0)

E.g. igb has similar checks in its MMIO accessors, and has a similar macro E1000REMOVED, which is implemented as follows:

#define E1000REMOVED(h) unlikely(!(h))

These checks serve to detect and take note of an 0xffffffff MMIO read return from the device, which can be caused by a PCIe link flap or some other kind of PCI bus error, and to avoid performing MMIO reads and writes from that point onwards.

However, the IGCREMOVED macro was not originally implemented:

#ifndef IGCREMOVED #define IGCREMOVED(a) (0) #endif / IGCREMOVED /

This led to the IGCREMOVED logic to be removed entirely in a subsequent commit (commit 3c215fb18e70, "igc: remove IGCREMOVED function"), with the rationale that such checks matter only for virtualization and that igc does not support virtualization -- but a PCIe device can become detached even without virtualization being in use, and without proper checks, a PCIe bus error affecting an igc adapter will lead to various NULL pointer dereferences, as the first access after the error will set hw->hwaddr to NULL, and subsequent accesses will blindly dereference this now-NULL pointer.

This patch reinstates the IGCREMOVED checks in igcrd32/wr32(), and implements IGCREMOVED the way it is done for igb, by checking for the unlikely() case of hwaddr being NULL. This change prevents the oopses seen when a PCIe link flap occurs on an igc adapter.

Affected Software

142 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.20<5.4.208
Linux Linux kernel>=5.5<5.10.134
Linux Linux kernel>=5.11<5.15.58
Linux Linux kernel>=5.16<5.18.15
Linux Linux kernel=5.19-rc1
Linux Linux kernel=5.19-rc2
Linux Linux kernel=5.19-rc3
Linux Linux kernel=5.19-rc4
Linux Linux kernel=5.19-rc5
Linux Linux kernel=5.19-rc6
Linux Linux kernel=5.19-rc7
ubuntu/linux-hwe-edge*
ubuntu/linux-aws-5.4<5.4.0-1086.93~18.04.1
5.4.0-1086.93~18.04.1
ubuntu/linux-azure-5.4<5.4.0-1094.100~18.04.1
5.4.0-1094.100~18.04.1
ubuntu/linux-gcp-5.4<5.4.0-1092.101~18.04.1
5.4.0-1092.101~18.04.1
ubuntu/linux-hwe-5.4<5.4.0-128.144~18.04.1
5.4.0-128.144~18.04.1
ubuntu/linux-ibm-5.4<5.4.0-1034.38~18.04.1
5.4.0-1034.38~18.04.1
ubuntu/linux-oracle-5.4<5.4.0-1084.92~18.04.1
5.4.0-1084.92~18.04.1
ubuntu/linux-raspi-5.4<5.4.0-1071.81~18.04.1
5.4.0-1071.81~18.04.1
ubuntu/linux-aws-5.0*
ubuntu/linux-aws-5.3*
ubuntu/linux-azure*
ubuntu/linux-azure-5.3*
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-5.3*
ubuntu/linux-gke-4.15*
ubuntu/linux-gke-5.4*
ubuntu/linux-gkeop-5.4*
ubuntu/linux-hwe*
ubuntu/linux-hwe-edge*
ubuntu/linux-oem*
ubuntu/linux-oracle-5.0*
ubuntu/linux-oracle-5.3*
ubuntu/linux<5.4.0-128.144
5.4.0-128.144
ubuntu/linux-aws<5.4.0-1086.93
5.4.0-1086.93
ubuntu/linux-aws-5.15<5.15.0-1021.25~20.04.1
5.15.0-1021.25~20.04.1
ubuntu/linux-azure<5.4.0-1094.100
5.4.0-1094.100
ubuntu/linux-azure-5.15<5.15.0-1021.26~20.04.1
5.15.0-1021.26~20.04.1
ubuntu/linux-bluefield<5.4.0-1047.52
5.4.0-1047.52
ubuntu/linux-gcp<5.4.0-1090.98
5.4.0-1090.98
ubuntu/linux-gcp-5.15<5.15.0-1021.28~20.04.1
5.15.0-1021.28~20.04.1
ubuntu/linux-hwe-5.15<5.15.0-50.56~20.04.1
5.15.0-50.56~20.04.1
ubuntu/linux-ibm<5.4.0-1034.38
5.4.0-1034.38
ubuntu/linux-intel-iotg-5.15<5.15.0-1017.22~20.04.1
5.15.0-1017.22~20.04.1
ubuntu/linux-iot<5.4.0-1005.7
5.4.0-1005.7
ubuntu/linux-kvm<5.4.0-1076.81
5.4.0-1076.81
ubuntu/linux-lowlatency-hwe-5.15<5.15.0-50.56~20.04.1
5.15.0-50.56~20.04.1
ubuntu/linux-oracle<5.4.0-1084.92
5.4.0-1084.92
ubuntu/linux-oracle-5.15<5.15.0-1019.24~20.04.1
5.15.0-1019.24~20.04.1
ubuntu/linux-raspi<5.4.0-1071.81
5.4.0-1071.81
ubuntu/linux-riscv-5.15<5.15.0-1022.26~20.04.1
5.15.0-1022.26~20.04.1
ubuntu/linux-aws-5.11*
ubuntu/linux-aws-5.13*
ubuntu/linux-aws-5.8*
ubuntu/linux-azure-5.11*
ubuntu/linux-azure-5.13*
ubuntu/linux-azure-5.8*
ubuntu/linux-azure-fde*
ubuntu/linux-gcp-5.11*
ubuntu/linux-gcp-5.13*
ubuntu/linux-gcp-5.8*
ubuntu/linux-gke*
ubuntu/linux-gke-5.15*
ubuntu/linux-gkeop*
ubuntu/linux-gkeop-5.15*
ubuntu/linux-hwe-5.11*
ubuntu/linux-hwe-5.13*
ubuntu/linux-hwe-5.8*
ubuntu/linux-intel-5.13*
ubuntu/linux-oem-5.10*
ubuntu/linux-oem-5.13*
ubuntu/linux-oem-5.6*
ubuntu/linux-oracle-5.11*
ubuntu/linux-oracle-5.13*
ubuntu/linux-oracle-5.8*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.11*
ubuntu/linux-riscv-5.8*
ubuntu/linux-aws-fips<5.4.0-1086.93+fips1
5.4.0-1086.93+fips1
ubuntu/linux-azure-fips<5.4.0-1094.100+fips1
5.4.0-1094.100+fips1
ubuntu/linux-fips<5.4.0-1062.70
5.4.0-1062.70
ubuntu/linux-gcp-fips<5.4.0-1092.101+fips1
5.4.0-1092.101+fips1
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux<5.15.0-50.56
5.15.0-50.56
ubuntu/linux-allwinner-5.19*
ubuntu/linux-aws<5.15.0-1021.25
5.15.0-1021.25
ubuntu/linux-aws-5.19*
ubuntu/linux-aws-6.2*
ubuntu/linux-aws-6.5*
ubuntu/linux-azure<5.15.0-1021.26
5.15.0-1021.26
ubuntu/linux-azure-5.19*
ubuntu/linux-azure-6.2*
ubuntu/linux-azure-6.5*
ubuntu/linux-azure-fde<5.15.0-1024.30.1
5.15.0-1024.30.1
ubuntu/linux-azure-fde-5.19*
ubuntu/linux-azure-fde-6.2*
ubuntu/linux-gcp<5.15.0-1019.25
5.15.0-1019.25
ubuntu/linux-gcp-5.19*
ubuntu/linux-gcp-6.2*
ubuntu/linux-gcp-6.5*
ubuntu/linux-gke<5.15.0-1017.20
5.15.0-1017.20
ubuntu/linux-gkeop<5.15.0-1004.6
5.15.0-1004.6
ubuntu/linux-hwe-5.19*
ubuntu/linux-hwe-6.2*
ubuntu/linux-hwe-6.5*
ubuntu/linux-ibm<5.15.0-1015.17
5.15.0-1015.17
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-intel-iotg<5.15.0-1017.22
5.15.0-1017.22
ubuntu/linux-kvm<5.15.0-1019.23
5.15.0-1019.23
ubuntu/linux-lowlatency<5.15.0-50.56
5.15.0-50.56
ubuntu/linux-lowlatency-hwe-5.19*
ubuntu/linux-lowlatency-hwe-6.2*
ubuntu/linux-lowlatency-hwe-6.5*
ubuntu/linux-nvidia<5.15.0-1015.15
5.15.0-1015.15
ubuntu/linux-nvidia-6.2*
ubuntu/linux-nvidia-6.5*
ubuntu/linux-oem-5.17*
ubuntu/linux-oem-6.0*
ubuntu/linux-oem-6.1*
ubuntu/linux-oem-6.5*
ubuntu/linux-oracle<5.15.0-1019.24
5.15.0-1019.24
ubuntu/linux-oracle-6.5*
ubuntu/linux-raspi<5.15.0-1016.18
5.15.0-1016.18
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.19*
ubuntu/linux-riscv-6.5*
ubuntu/linux-starfive-5.19*
ubuntu/linux-starfive-6.2*
ubuntu/linux-starfive-6.5*
ubuntu/linux-realtime<5.15.0-1022.22
5.15.0-1022.22
ubuntu/linux-raspi-realtime*
debian/linux<5.18.16-1
5.18.16-1
debian/linux<5.18.16-1
5.18.16-1
debian/linux<5.18.16-1
5.18.16-1
debian/linux
6.1.176-16.1.192-26.12.107-16.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.4.0-1086.93~18.04.1
  2. Upgrade

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

    Fixed in 5.4.0-1094.100~18.04.1
  3. Upgrade

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

    Fixed in 5.4.0-1092.101~18.04.1
  4. Upgrade

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

    Fixed in 5.4.0-128.144~18.04.1
  5. Upgrade

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

    Fixed in 5.4.0-1034.38~18.04.1
  6. Upgrade

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

    Fixed in 5.4.0-1084.92~18.04.1
  7. Upgrade

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

    Fixed in 5.4.0-1071.81~18.04.1
  8. Upgrade

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

    Fixed in 5.4.0-128.144
  9. Upgrade

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

    Fixed in 5.4.0-1086.93
  10. Upgrade

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

    Fixed in 5.15.0-1021.25~20.04.1
  11. Upgrade

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

    Fixed in 5.4.0-1094.100
  12. Upgrade

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

    Fixed in 5.15.0-1021.26~20.04.1
  13. Upgrade

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

    Fixed in 5.4.0-1047.52
  14. Upgrade

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

    Fixed in 5.4.0-1090.98
  15. Upgrade

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

    Fixed in 5.15.0-1021.28~20.04.1
  16. Upgrade

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

    Fixed in 5.15.0-50.56~20.04.1
  17. Upgrade

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

    Fixed in 5.4.0-1034.38
  18. Upgrade

    Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1017.22~20.04.1
  19. Upgrade

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

    Fixed in 5.4.0-1005.7
  20. Upgrade

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

    Fixed in 5.4.0-1076.81
  21. Upgrade

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

    Fixed in 5.15.0-50.56~20.04.1
  22. Upgrade

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

    Fixed in 5.4.0-1084.92
  23. Upgrade

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

    Fixed in 5.15.0-1019.24~20.04.1
  24. Upgrade

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

    Fixed in 5.4.0-1071.81
  25. Upgrade

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

    Fixed in 5.15.0-1022.26~20.04.1
  26. Upgrade

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

    Fixed in 5.4.0-1086.93+fips1
  27. Upgrade

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

    Fixed in 5.4.0-1094.100+fips1
  28. Upgrade

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

    Fixed in 5.4.0-1062.70
  29. Upgrade

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

    Fixed in 5.4.0-1092.101+fips1
  30. Upgrade

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

    Fixed in 5.15.0-50.56
  31. Upgrade

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

    Fixed in 5.15.0-1021.25
  32. Upgrade

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

    Fixed in 5.15.0-1021.26
  33. Upgrade

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

    Fixed in 5.15.0-1024.30.1
  34. Upgrade

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

    Fixed in 5.15.0-1019.25
  35. Upgrade

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

    Fixed in 5.15.0-1017.20
  36. Upgrade

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

    Fixed in 5.15.0-1004.6
  37. Upgrade

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

    Fixed in 5.15.0-1015.17
  38. Upgrade

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

    Fixed in 5.15.0-1017.22
  39. Upgrade

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

    Fixed in 5.15.0-1019.23
  40. Upgrade

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

    Fixed in 5.15.0-50.56
  41. Upgrade

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

    Fixed in 5.15.0-1015.15
  42. Upgrade

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

    Fixed in 5.15.0-1019.24
  43. Upgrade

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

    Fixed in 5.15.0-1016.18
  44. Upgrade

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

    Fixed in 5.15.0-1022.22
  45. Upgrade

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

    Fixed in 5.18.16-1
  46. Upgrade

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

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Event History

Feb 26, 2025
CVE Published
via MITRE·02:23 AM
Data Sourced
via MITRE·02:23 AM
Description
Data Sourced
via Red Hat·03:21 AM
DescriptionSeverityAffected Software
Data Sourced
via OSV·07:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:01 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2022-49605?

CVE-2022-49605 is classified as a medium severity vulnerability in the Linux kernel's igc driver.

2

How do I fix CVE-2022-49605?

To resolve CVE-2022-49605, update the Linux kernel to the latest version that contains the fix for this vulnerability.

3

What systems are affected by CVE-2022-49605?

CVE-2022-49605 affects systems running the Linux kernel, specifically with the Intel igc driver.

4

What is the impact of CVE-2022-49605?

The impact of CVE-2022-49605 may include improper handling of driver logic, potentially leading to system crashes or instability.

5

Is CVE-2022-49605 publicly known?

Yes, CVE-2022-49605 has been publicly disclosed as part of the Linux kernel vulnerabilities.

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