VULNOS
All Threat Alerts
criticalCVE Alert
CVE-2022-49418

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

In the Linux kernel, the following vulnerability has been resolved: NFSv4: Fix free of uninitialized nfs4_label on referral lookup. Send along the already-allocated fattr along with nfs4_fs_locations, and drop the memcpy of fattr. We end up growing two more allocations, but this fixes up a crash as: PID: 790 TASK: ffff88811b43c000 CPU: 0 COMMAND: "ls" #0 [ffffc90000857920] panic at ffffffff81b9bfde #1 [ffffc900008579c0] do_trap at ffffffff81023a9b #2 [ffffc90000857a10] do_error_trap

Sunday, September 27, 2026linuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2022-49418 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:

NFSv4: Fix free of uninitialized nfs4_label on referral lookup.

Send along the already-allocated fattr along with nfs4_fs_locations, and

drop the memcpy of fattr. We end up growing two more allocations, but this

fixes up a crash as:

PID: 790 TASK: ffff88811b43c000 CPU: 0 COMMAND: "ls"

#0 [ffffc90000857920] panic at ffffffff81b9bfde

#1 [ffffc900008579c0] do_trap at ffffffff81023a9b

#2 [ffffc90000857a10] do_error_trap at ffffffff81023b78

#3 [ffffc90000857a58] exc_stack_segment at ffffffff81be1f45

#4 [ffffc90000857a80] asm_exc_stack_segment at ffffffff81c009de

#5 [ffffc90000857b08] nfs_lookup at ffffffffa0302322 [nfs]

#6 [ffffc90000857b70] __lookup_slow at ffffffff813a4a5f

#7 [ffffc90000857c60] walk_component at ffffffff813a86c4

#8 [ffffc90000857cb8] path_lookupat at ffffffff813a9553

#9 [ffffc90000857cf0] filename_lookup at ffffffff813ab86b

Why It Matters

CVE-2022-49418 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-49418.
  • 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-49418 and similar vulnerabilities.

    References & Sources

  • https://git.kernel.org/stable/c/6015292653d95ba9f72906e2b65e536aa5807d64
  • https://git.kernel.org/stable/c/c3ed222745d9ad7b69299b349a64ba533c64a34f

    • 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-49418?

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

    NFSv4: Fix free of uninitialized nfs4_label on referral lookup.

    Send along the already-allocated fattr along with nfs4_fs_location

    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-49418. 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