# net: annotate races around sk->sk_bound_dev_if

CVE record · `CVE-2022-49420`

- **Identifiers:** `CVE-2022-49420`
- **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:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:12 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: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 20b2f61797873a2b18b5ff1a304ad2674fa1e0a5` (git)
  - affected: `1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to before 4c971d2f3548e4f11b1460ac048f5307e4b39fdb` (git)
  - affected: `before 5.18.3` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - unaffected: `5.18.3 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> This is a data race in the Linux kernel's networking code, where the bound device index (sk_bound_dev_if) of a socket can be changed by one thread while UDP sendmsg() reads it without a lock. The source reports this as a race that a kernel concurrency sanitizer flagged, with minor consequences, and gives few details about exploitability. Linux kernel versions before 5.18.3 are affected, and the fix is to upgrade to 5.18.3 or later (5.19 and later are unaffected); no workaround is listed.

Written 16 Nov 2026.

## 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 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 02:12 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49420)
- 26 Feb 2025, 07:01 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49420)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/20b2f61797873a2b18b5ff1a304ad2674fa1e0a5>
- <https://git.kernel.org/stable/c/4c971d2f3548e4f11b1460ac048f5307e4b39fdb>

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

---

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