# sfc: fix TX channel offset when using legacy interrupts

CVE record · `CVE-2022-48647`

- **Identifiers:** `CVE-2022-48647`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 28 Apr 2024
- **Updated:** 23 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 28 Apr 2024, 13:00 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: `bf2af9b24313553f3f0b30443220ab0ac8595d2d to before b4afd3878f961d3517f27b3213730fceef77945c` (git)
  - affected: `06cb7e134f8f4a11b66f1dbeb5f237412a0aeedc to before 360910b88d1466a90644a4e0533803b594344a2b` (git)
  - affected: `c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 to before 5f623a77cfc2d501d72bcb4f9ee71721e6c766ff` (git)
  - affected: `c308dfd1b43ef0d4c3e57b741bb3462eb7a7f4a2 to before f232af4295653afa4ade3230462b3be15ad16419` (git)
  - affected: `1a7c0b3ef93d1d1dae7b0a85dab3ac6e3ad0ef61` (git)
  - affected: `b2d60329a0b88c4e35017436ee29c43be59d46a5` (git)
  - affected: `5.10.122 to before 5.10.146` (semver)
  - affected: `5.15.47 to before 5.15.71` (semver)
  - affected: `5.17.15 to before 5.18` (semver)
  - affected: `5.18.4 to before 5.19` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.19`
  - unaffected: `before 5.19` (semver)
  - unaffected: `5.10.146 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.71 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.12 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0 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.0023, the 13th percentile, on 21 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 28 Apr 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/b4afd3878f961d3517f27b3213730fceef77945c>
- <https://git.kernel.org/stable/c/360910b88d1466a90644a4e0533803b594344a2b>
- <https://git.kernel.org/stable/c/5f623a77cfc2d501d72bcb4f9ee71721e6c766ff>
- <https://git.kernel.org/stable/c/f232af4295653afa4ade3230462b3be15ad16419>

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

---

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