# cipso: Fix data-races around sysctl.

CVE record · `CVE-2022-49639`

- **Identifiers:** `CVE-2022-49639`
- **State:** Confirmed
- **Severity:** CVSS 4.7 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-362](https://cwe.mitre.org/data/definitions/362.html)
- **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md)
- **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: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before 2764f82bbc158d106693ae3ced3675cf4b963b35` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before c321e99d2725d11f7e6a4ebd9ce752259f0bae81` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before ca26ca5e2f3eeb3e6fe699cd6effa3b4b2aa8698` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before 0e41a0f73ccb9be112a80bde3804a771633caaef` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before fe2a35fa2c4f9c8ce5ef970eb927031387f9446a` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before 07b0caf8aeb9b82e6ecc6c292a3e47c7fcdb1148` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before 59e26906b89cc35bb54476498772b45cbc32323f` (git)
  - affected: `446fda4f26822b2d42ab3396aafcedf38a9ff2b6 to before dd44f04b9214adb68ef5684ae87a81ba03632250` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.19`
  - unaffected: `before 2.6.19` (semver)
  - unaffected: `4.9.324 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.289 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.253 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.207 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.132 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.56 to 5.15.*, inclusive` (semver)
  - unaffected: `5.18.13 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

- 4.7 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th 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-49639](https://www.cve.org/CVERecord?id=CVE-2022-49639)
- [NVD: CVE-2022-49639](https://nvd.nist.gov/vuln/detail/CVE-2022-49639)

### References from the CNA

- <https://git.kernel.org/stable/c/2764f82bbc158d106693ae3ced3675cf4b963b35>
- <https://git.kernel.org/stable/c/c321e99d2725d11f7e6a4ebd9ce752259f0bae81>
- <https://git.kernel.org/stable/c/ca26ca5e2f3eeb3e6fe699cd6effa3b4b2aa8698>
- <https://git.kernel.org/stable/c/0e41a0f73ccb9be112a80bde3804a771633caaef>
- <https://git.kernel.org/stable/c/fe2a35fa2c4f9c8ce5ef970eb927031387f9446a>
- <https://git.kernel.org/stable/c/07b0caf8aeb9b82e6ecc6c292a3e47c7fcdb1148>
- <https://git.kernel.org/stable/c/59e26906b89cc35bb54476498772b45cbc32323f>
- <https://git.kernel.org/stable/c/dd44f04b9214adb68ef5684ae87a81ba03632250>

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

---

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