# nvmet-tcp: fix incorrect locking in state_change sk callback

CVE record · `CVE-2021-47041`

- **Identifiers:** `CVE-2021-47041`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 28 Feb 2024
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 28 Feb 2024, 08:13 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: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 999d606a820c36ae9b9e9611360c8b3d8d4bb777` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 60ade0d56b06537a28884745059b3801c78e03bc` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 06beaa1a9f6e501213195e47c30416032fd2bbd5` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 906c538340dde6d891df89fe7dac8eaa724e40da` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before b5332a9f3f3d884a1b646ce155e664cc558c1722` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.0`
  - unaffected: `before 5.0` (semver)
  - unaffected: `5.4.119 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.37 to 5.10.*, inclusive` (semver)
  - unaffected: `5.11.21 to 5.11.*, inclusive` (semver)
  - unaffected: `5.12.4 to 5.12.*, inclusive` (semver)
  - unaffected: `5.13 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 43rd 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 Feb 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/999d606a820c36ae9b9e9611360c8b3d8d4bb777>
- <https://git.kernel.org/stable/c/60ade0d56b06537a28884745059b3801c78e03bc>
- <https://git.kernel.org/stable/c/06beaa1a9f6e501213195e47c30416032fd2bbd5>
- <https://git.kernel.org/stable/c/906c538340dde6d891df89fe7dac8eaa724e40da>
- <https://git.kernel.org/stable/c/b5332a9f3f3d884a1b646ce155e664cc558c1722>

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

---

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