# ax25: fix incorrect dev_tracker usage

CVE record · `CVE-2022-50163`

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

Published by the CVE Program (CNA: Linux) at 18 Jun 2025, 11:03 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: `feef318c855a361a1eccd880f33e88c460eb63b4 to before d08e3d71e5942f77fbff7f3529ed7fc82fbb3dfa` (git)
  - affected: `feef318c855a361a1eccd880f33e88c460eb63b4 to before 4294df1374450912b2f64ee3cf575069fc784679` (git)
  - affected: `feef318c855a361a1eccd880f33e88c460eb63b4 to before d7c4c9e075f8cc6d88d277bc24e5d99297f03c06` (git)
  - affected: `b8c07f33aa35dacf5444e7053ed9662d1869f536` (git)
  - affected: `b1e0a6fc7f17500484c402ad1cd018c24dfc14b3` (git)
  - affected: `7528d0f2210c3a1154186175516ed37aa970f2b1` (git)
  - affected: `57cc15f5fd550316e4104eaf84b90fbc640fd7a5` (git)
  - affected: `b982492ec3a115e0a136856a1b2dbe32f2d21a0e` (git)
  - affected: `4.14.277 to before 4.15` (semver)
  - affected: `4.19.240 to before 4.20` (semver)
  - affected: `5.4.190 to before 5.5` (semver)
  - affected: `5.10.112 to before 5.11` (semver)
  - and 1 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `5.18.18 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19.2 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.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 18 Jun 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/d08e3d71e5942f77fbff7f3529ed7fc82fbb3dfa>
- <https://git.kernel.org/stable/c/4294df1374450912b2f64ee3cf575069fc784679>
- <https://git.kernel.org/stable/c/d7c4c9e075f8cc6d88d277bc24e5d99297f03c06>

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

---

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