Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49568KVM: Don't null dereference ops->destroy

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: Don't null dereference ops->destroy A KVM device cleanup happens in either of two callbacks: 1) destroy() which is called when the VM is being destroyed; 2) release() which is called when a device fd is closed. Most KVM devices use 1) but Book3s's interrupt controller KVM devices (XICS, XIVE, XIVE-native) use 2) as they need to close and reopen during the machine execution. The error handling in kvm_ioctl_create_device() assumes destroy() is always defined which leads to NULL dereference as discovered by Syzkaller. This adds a checks for destroy!=NULL and adds a missing release(). This is not changing kvm_destroy_devices() as devices with defined release() should have been removed from the KVM devices list by then.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49568, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.30% · top 77% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 852b6d57dc7fa378019786fa84727036e56839ea – < 170465715a60cbb7876e6b961b21bd3225469da8
    • affected 852b6d57dc7fa378019786fa84727036e56839ea – < 3616776bc51cd3262bb1be60cc01c72e0a1959cf
    • affected 852b6d57dc7fa378019786fa84727036e56839ea – < e91665fbbf3ccb268b268a7d71a6513538d813ac
    • affected 852b6d57dc7fa378019786fa84727036e56839ea – < d4a5a79b780891c5cbdfdc6124d46fdf8d13dba1
    • affected 852b6d57dc7fa378019786fa84727036e56839ea – < e8bc2427018826e02add7b0ed0fc625a60390ae5
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.4.210 – ≤ 5.4.*
    • unaffected 5.10.134 – ≤ 5.10.*
    • unaffected 5.15.58 – ≤ 5.15.*
    • unaffected 5.18.15 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49568 badge
[![CVE-2022-49568](https://cveledger.app/badge/CVE-2022-49568.svg)](https://cveledger.app/cve/CVE-2022-49568)

Record last updated .