# KVM: x86/xen: Fix eventfd error handling in kvm_xen_eventfd_assign()

CVE record · `CVE-2022-49774`

- **Identifiers:** `CVE-2022-49774`
- **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: `2fd6df2f2b47d4301b1ee0fe9d627d1c061a5988 to before d76f46f47dfde220712d1420ee5dbc546c8fc674` (git)
  - affected: `2fd6df2f2b47d4301b1ee0fe9d627d1c061a5988 to before 7353633814f6e5b4899fb9ee1483709d6bb0e1cd` (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.

> The Linux kernel's KVM x86/xen code, in kvm_xen_eventfd_assign(), calls eventfd_ctx_put() on an error path where it should not. The source gives few details on the impact or what an attacker would need. Version 5.19 is listed as affected, so upgrade to 6.0.10 or later in the 6.0 series, or to 6.1 or later.

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-49774)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49774)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/d76f46f47dfde220712d1420ee5dbc546c8fc674>
- <https://git.kernel.org/stable/c/7353633814f6e5b4899fb9ee1483709d6bb0e1cd>

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

---

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