# blk-cgroup: properly pin the parent in blkcg_css_online

CVE record · `CVE-2022-49786`

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

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:09 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: `397c9f46ee4d99024c64954b007c1b5762d01cb4 to before d118247e404d6338f7b90636a3c6b95a387ed163` (git)
  - affected: `397c9f46ee4d99024c64954b007c1b5762d01cb4 to before d7dbd43f4a828fa1d9a8614d5b0ac40aee6375fe` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.19`
  - unaffected: `before 5.19` (semver)
  - unaffected: `6.0.10 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 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.

> Linux kernel versions from 5.19 are affected because blkcg_css_online pins the css instead of the parent blkcg, leaking blkcg and cgroup objects. The source gives few details on attacker requirements or impact. Upgrade to 6.0.10 or later in the 6.0 series, or to 6.1 or later; 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.0017, the 6th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 14:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49786)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49786)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/d118247e404d6338f7b90636a3c6b95a387ed163>
- <https://git.kernel.org/stable/c/d7dbd43f4a828fa1d9a8614d5b0ac40aee6375fe>

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

---

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