# mm/slub: add missing TID updates on slab deactivation

CVE record · `CVE-2022-49700`

- **Identifiers:** `CVE-2022-49700`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:24 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: `03e404af26dc2ea0d278d7a342de0aab394793ce to before 308c6d0e1f200fd26c71270c6e6bfcf0fc6ff082` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before d6a597450e686d4c6388bd3cdcb17224b4dae7f0` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before e2b2f0e2e34d71ae6c2a1114fd3c525930e84bc7` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before e7e3e90d671078455a3a08189f89d85b3da2de9e` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before 6c32496964da0dc230cea763a0e934b2e02dabd5` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before 0515cc9b6b24877f59b222ade704bfaa42caa2a6` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before 197e257da473c725dfe47759c3ee02f2398d8ea5` (git)
  - affected: `03e404af26dc2ea0d278d7a342de0aab394793ce to before eeaa345e128515135ccb864c04482180c08e3259` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.1`
  - unaffected: `before 3.1` (semver)
  - unaffected: `4.9.323 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.288 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.252 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.205 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.130 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.54 to 5.15.*, inclusive` (semver)
  - unaffected: `5.18.8 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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux) (used for this record)
- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

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

### References from the CNA

- <https://git.kernel.org/stable/c/308c6d0e1f200fd26c71270c6e6bfcf0fc6ff082>
- <https://git.kernel.org/stable/c/d6a597450e686d4c6388bd3cdcb17224b4dae7f0>
- <https://git.kernel.org/stable/c/e2b2f0e2e34d71ae6c2a1114fd3c525930e84bc7>
- <https://git.kernel.org/stable/c/e7e3e90d671078455a3a08189f89d85b3da2de9e>
- <https://git.kernel.org/stable/c/6c32496964da0dc230cea763a0e934b2e02dabd5>
- <https://git.kernel.org/stable/c/0515cc9b6b24877f59b222ade704bfaa42caa2a6>
- <https://git.kernel.org/stable/c/197e257da473c725dfe47759c3ee02f2398d8ea5>
- <https://git.kernel.org/stable/c/eeaa345e128515135ccb864c04482180c08e3259>

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

---

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