# igc: Reinstate IGC_REMOVED logic and implement it properly

CVE record · `CVE-2022-49605`

- **Identifiers:** `CVE-2022-49605`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `146740f9abc4976e4f0af1aa302efee1c699d2e4 to before 16cb6717f4f42487ef10583eb8bc98e7d1e33d65` (git)
  - affected: `146740f9abc4976e4f0af1aa302efee1c699d2e4 to before 77836dbe35382aaf8108489060c5c89530c77494` (git)
  - affected: `146740f9abc4976e4f0af1aa302efee1c699d2e4 to before e75b73081f1ec169518773626c2ff3950476660b` (git)
  - affected: `146740f9abc4976e4f0af1aa302efee1c699d2e4 to before 70965b6e5c03aa70cc754af1226b9f9cde0c4bf3` (git)
  - affected: `146740f9abc4976e4f0af1aa302efee1c699d2e4 to before 7c1ddcee5311f3315096217881d2dbe47cc683f9` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.20`
  - unaffected: `before 4.20` (semver)
  - unaffected: `5.4.208 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.134 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.58 to 5.15.*, inclusive` (semver)
  - unaffected: `5.18.15 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0026, the 18th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 26 Feb 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-49605](https://www.cve.org/CVERecord?id=CVE-2022-49605)
- [NVD: CVE-2022-49605](https://nvd.nist.gov/vuln/detail/CVE-2022-49605)

### References from the CNA

- <https://git.kernel.org/stable/c/16cb6717f4f42487ef10583eb8bc98e7d1e33d65>
- <https://git.kernel.org/stable/c/77836dbe35382aaf8108489060c5c89530c77494>
- <https://git.kernel.org/stable/c/e75b73081f1ec169518773626c2ff3950476660b>
- <https://git.kernel.org/stable/c/70965b6e5c03aa70cc754af1226b9f9cde0c4bf3>
- <https://git.kernel.org/stable/c/7c1ddcee5311f3315096217881d2dbe47cc683f9>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49605>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49605/>. Everything for agents: <https://agentprime.io/llms.txt>.
