# sfc: fix considering that all channels have TX queues

CVE record · `CVE-2022-49378`

- **Identifiers:** `CVE-2022-49378`
- **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:11 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: `8700aff089843399f95bc7701ae87b642b35a716 to before 8f81a4113e1e574d2cbde4f2cd599380a9189c0f` (git)
  - affected: `8700aff089843399f95bc7701ae87b642b35a716 to before 5567d69b95b9c07e1c56f15cf0301251d12e5f97` (git)
  - affected: `8700aff089843399f95bc7701ae87b642b35a716 to before e7e8d5e25dc762b70f9c88ec6b7d451d0816eead` (git)
  - affected: `8700aff089843399f95bc7701ae87b642b35a716 to before 913d45f02d346ce41c4aad057eaf53a8ed449dc3` (git)
  - affected: `8700aff089843399f95bc7701ae87b642b35a716 to before 2e102b53f8a778f872dc137f4c7ac548705817aa` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.5`
  - unaffected: `before 5.5` (semver)
  - unaffected: `5.10.122 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.47 to 5.15.*, inclusive` (semver)
  - unaffected: `5.17.15 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18.4 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.0027, the 19th 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-49378](https://www.cve.org/CVERecord?id=CVE-2022-49378)
- [NVD: CVE-2022-49378](https://nvd.nist.gov/vuln/detail/CVE-2022-49378)

### References from the CNA

- <https://git.kernel.org/stable/c/8f81a4113e1e574d2cbde4f2cd599380a9189c0f>
- <https://git.kernel.org/stable/c/5567d69b95b9c07e1c56f15cf0301251d12e5f97>
- <https://git.kernel.org/stable/c/e7e8d5e25dc762b70f9c88ec6b7d451d0816eead>
- <https://git.kernel.org/stable/c/913d45f02d346ce41c4aad057eaf53a8ed449dc3>
- <https://git.kernel.org/stable/c/2e102b53f8a778f872dc137f4c7ac548705817aa>

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-49378>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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