All Threat Alerts
criticalCVE Alert
CVE-2022-50335

Critical Vulnerability: CVE-2022-50335 โ€” linux โ€” linux_kernel

In the Linux kernel, the following vulnerability has been resolved: 9p: set req refcount to zero to avoid uninitialized usage When a new request is allocated, the refcount will be zero if it is reused, but if the request is newly allocated from slab, it is not fully initialized before being added to idr. If the p9_read_work got a response before the refcount initiated. It will use a uninitialized req, which will result in a bad request data struct. Here is the logs from syzbot. Corrupted me

Sunday, September 27, 2026linuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

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

9p: set req refcount to zero to avoid uninitialized usage

When a new request is allocated, the refcount will be zero if it is

reused, but if the request is newly allocated from slab, it is not fully

initialized before being added to idr.

If the p9_read_work got a response before the refcount initiated. It will

use a uninitialized req, which will result in a bad request data struct.

Here is the logs from syzbot.

Corrupted memory at 0xffff88807eade00b [ 0xff 0x07 0x00 0x00 0x00 0x00

0x00 0x00 . . . . . . . . ] (in kfence-#110):

p9_fcall_fini net/9p/client.c:248 [inline]

p9_req_put net/9p/client.c:396 [inline]

p9_req_put+0x208/0x250 net/9p/client.c:390

p9_client_walk+0x247/0x540 net/9p/client.c:1165

clone_fid fs/9p/fid.h:21 [inline]

v9fs_fid_xattr_set+0xe4/0x2b0 fs/9p/xattr.c:118

v9fs_xattr_set fs/9p/xattr.c:100 [inline]

v9fs_xattr_handler_set+0x6f/0x120 fs/9p/xattr.c:159

__vfs_setxattr+0x119/0x180 fs/xattr.

Why It Matters

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

    References & Sources

    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-50335?

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

    9p: set req refcount to zero to avoid uninitialized usage

    When a new request is allocated, the refcount will be zero if it is

    reus

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

    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