Kernel crash via empty Xen receive queue
Published Feb 26, 2025 · Updated May 11, 2026
NULL pointer dereference in Linux kernel Xen netback allows guest OS users to crash the host during network receive processing. During multiple iterations of xenvif_rx_action(), the code calls xenvif_rx_next_skb() again without confirming that another socket buffer remains in the receive queue. The condition requires Xen netback receive processing controlled by a guest; dereferencing the emptied queue causes a host-kernel oops and service interruption.
Summary
What happened
NULL pointer dereference in Linux kernel Xen netback allows guest OS users to crash the host during network receive processing. During multiple iterations of xenvif_rx_action(), the code calls xenvif_rx_next_skb() again without confirming that another socket buffer remains in the receive queue. The condition requires Xen netback receive processing controlled by a guest; dereferencing the emptied queue causes a host-kernel oops and service interruption.
The record
- CVE
- CVE-2022-49649
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.9
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <5a071aefd6414af5a20321ab58a0557b81993687
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <7425479d20f9e96f7c3ec8e8a93fe0d7478724cb
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <94e8100678889ab428e68acadf042de723f094b9
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <b99174ac57fe5d8867448c03b23828e63f24cb1c
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <b9c32a6886af79d6e0ad87a7b01800ed079cdd02
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <c0fcceb5f3f1ec197c014fe218c2f28108cacd27
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <d5320c6a27aa975aff740f9cb481dcbde48f4348
- Affected versionversion=98f6d57ced73b723551568262019f1d6c8771f20 <f0b5c819b062df8bf5f2acf4697e3871cb3722da
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo