CVE-2022-50073
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-17
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | 5.12 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a NULL pointer dereference in the Linux kernel's tap driver. It occurs because the skb->dev field is null when the function virtio_net_hdr_to_skb calls dev_parse_header_protocol, which expects skb->dev to be valid. This leads to a kernel crash (NULL pointer dereference) when accessing dev->header_ops. The issue is fixed by setting skb->dev before the call in tap.c.
How can this vulnerability impact me? :
This vulnerability can cause a kernel crash due to a NULL pointer dereference in the tap driver. This may lead to denial of service (system instability or crash) on affected Linux systems using the tap driver.