VULNOS
All Threat Alerts
criticalCVE Alert
CVE-2022-49201

Critical Vulnerability: CVE-2022-49201 — linux — linux_kernel

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: fix race between xmit and reset There is a race between reset and the transmit paths that can lead to ibmvnic_xmit() accessing an scrq after it has been freed in the reset path. It can result in a crash like: Kernel attempted to read user page (0) - exploit attempt? (uid: 0) BUG: Kernel NULL pointer dereference on read at 0x00000000 Faulting instruction address: 0xc0080000016189f8 Oops: Kernel access of bad area,

Sunday, September 27, 2026linuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2022-49201 is rated CRITICAL — exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: linux_kernel.

Executive Summary

In the Linux kernel, the following vulnerability has been resolved:

ibmvnic: fix race between xmit and reset

There is a race between reset and the transmit paths that can lead to

ibmvnic_xmit() accessing an scrq after it has been freed in the reset

path. It can result in a crash like:

Kernel attempted to read user page (0) - exploit attempt? (uid: 0)

BUG: Kernel NULL pointer dereference on read at 0x00000000

Faulting instruction address: 0xc0080000016189f8

Oops: Kernel access of bad area, sig: 11 [#1]

...

NIP [c0080000016189f8] ibmvnic_xmit+0x60/0xb60 [ibmvnic]

LR [c000000000c0046c] dev_hard_start_xmit+0x11c/0x280

Call Trace:

[c008000001618f08] ibmvnic_xmit+0x570/0xb60 [ibmvnic] (unreliable)

[c000000000c0046c] dev_hard_start_xmit+0x11c/0x280

[c000000000c9cfcc] sch_direct_xmit+0xec/0x330

[c000000000bfe640] __dev_xmit_skb+0x3a0/0x9d0

[c000000000c00ad4] __dev_queue_xmit+0x394/0x730

[c008000002db813c] __bond_start_xmit+0x254/0x450 [bonding]

[c008000002db8378] bond_start_x

Why It Matters

CVE-2022-49201 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.8/10

Affected Technologies

Vendors: linux

Products: linux_kernel

🛡️What Defenders Should Check

  • Check if you are affected — Review your asset inventory for products listed in CVE-2022-49201.
  • Apply available patches — Visit vendor advisories for the latest security updates.
  • Monitor for exploitation — Check your SIEM/IDS logs for related indicators.

    • Use Vulnios to continuously monitor your exposure to CVE-2022-49201 and similar vulnerabilities.

    References & Sources

  • https://git.kernel.org/stable/c/1bd58abf595b6cf1ba6dd47ec887c4c009155fc9
  • https://git.kernel.org/stable/c/4219196d1f662cb10a462eb9e076633a3fc31a15
  • https://git.kernel.org/stable/c/475f9cce98b63bc145b4efa66fa51175d4cb345f
  • https://git.kernel.org/stable/c/8507c6ade73cdbbbda5c3d31d67f52f2e1cf03fe

    • How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for CVE matching against your container images and OS package manifests. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat — including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Affected Products

    linux_kernel

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2022-49201?

    CVE-2022-49201 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. In the Linux kernel, the following vulnerability has been resolved:

    ibmvnic: fix race between xmit and reset

    There is a race between reset and the transmit paths that can lead to

    ibmvnic_xmit() acce

    Am I affected?

    Check whether your environment runs linux_kernel. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2022-49201. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts — all in one platform.

    Get Started FreeFree Security ScanOSINT Dashboard

    Weekly threat digest

    KEV-listed exploits and vendor advisories, every Monday.

    One email a week. Unsubscribe any time.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios