# fbdev: Fix unregistering of framebuffers without device

CVE record · `CVE-2022-49070`

- **Identifiers:** `CVE-2022-49070`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-476](https://cwe.mitre.org/data/definitions/476.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:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 01:54 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: `c894ac44786cfed383a6c6b20c1bfb12eb96018a to before 2388f826cdc9af2651991adc0feb79de9bdf2232` (git)
  - affected: `9565a3b5203a4d57acbc1d0e981c6df71864b4ab to before de33df481545974ba47c46f05194e769e4307843` (git)
  - affected: `4d695d7c276f15adb1d2b64c584c3cf8f4f9e9ce to before feed87ff122b1640c221d4dd559442ab2cd50bb1` (git)
  - affected: `27599aacbaefcbf2af7b06b0029459bbf682000d to before 0f525289ff0ddeb380813bd81e0f9bdaaa1c9078` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15.33 to before 5.15.34` (semver)
  - affected: `5.16.19 to before 5.16.20` (semver)
  - affected: `5.17.2 to before 5.17.3` (semver)
  - Other versions: unaffected

## 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

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

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

### References from the CNA

- <https://git.kernel.org/stable/c/2388f826cdc9af2651991adc0feb79de9bdf2232>
- <https://git.kernel.org/stable/c/de33df481545974ba47c46f05194e769e4307843>
- <https://git.kernel.org/stable/c/feed87ff122b1640c221d4dd559442ab2cd50bb1>
- <https://git.kernel.org/stable/c/0f525289ff0ddeb380813bd81e0f9bdaaa1c9078>

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

---

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