Kernel crash via uninitialized TAP device pointer
Published Jun 18, 2025 · Updated Aug 12, 2026
NULL pointer dereference in the Linux tap driver allows local users to crash affected kernels by sending crafted virtual network data. In tap_get_user, the driver calls virtio_net_hdr_to_skb before assigning skb->dev, so dev_parse_header_protocol dereferences a null device pointer. Exploitation requires local low-privileged access to a TAP or vhost-net transmit path and affects availability by producing a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux tap driver allows local users to crash affected kernels by sending crafted virtual network data. In tap_get_user, the driver calls virtio_net_hdr_to_skb before assigning skb->dev, so dev_parse_header_protocol dereferences a null device pointer. Exploitation requires local low-privileged access to a TAP or vhost-net transmit path and affects availability by producing a kernel crash.
The record
- CVE
- CVE-2022-50073
- Published
- Jun 18, 2025
- Updated
- Aug 12, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 12, 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.14.226 <4.15
- Affected versionversion=4.19.181 <4.20
- Affected versionversion=5.10.24 <5.10.258
- Affected versionversion=5.11.7 <5.12
- Affected versionversion=5.12
- Affected versionversion=5.4.106 <5.5
- Affected versionversion=54ef8243c3c8e90f1ea5792e6752e021a25c8eb3
- Affected versionversion=924a9bc362a5223cd448ca08c3dde21235adc310 <447ba770cfe798925f4923548b367fd49f0ee5f0
- Affected versionversion=924a9bc362a5223cd448ca08c3dde21235adc310 <4f61f133f354853bc394ec7d6028adb9b02dd701
- Affected versionversion=924a9bc362a5223cd448ca08c3dde21235adc310 <dd29648fcf69339713f2d25f7014ae905dcdfc18
- Affected versionversion=99b1d3f74b9ef72c2f74c8e4c078e1bc0706e748
- Affected versionversion=ca278267d6cd9544645731732455b6b20cb0e895
- Affected versionversion=ea3fb2ce5fa794d02135f5c079e05cd6fc3f545d
- Affected versionversion=faa3baa2828c5e1c4374f3e60041f75c64f5fcb6 <8f90163f9e013c8fc791aab338aab44a46044cfc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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