VULNOS
All Threat Alerts
criticalCVE Alert
CVE-2022-50373

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

In the Linux kernel, the following vulnerability has been resolved: fs: dlm: fix race in lowcomms This patch fixes a race between queue_work() in _dlm_lowcomms_commit_msg() and srcu_read_unlock(). The queue_work() can take the final reference of a dlm_msg and so msg->idx can contain garbage which is signaled by the following warning: [ 676.237050] ------------[ cut here ]------------ [ 676.237052] WARNING: CPU: 0 PID: 1060 at include/linux/srcu.h:189 dlm_lowcomms_commit_msg+0x41/0x50 [ 676

Sunday, September 27, 2026linuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

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

fs: dlm: fix race in lowcomms

This patch fixes a race between queue_work() in

_dlm_lowcomms_commit_msg() and srcu_read_unlock(). The queue_work() can

take the final reference of a dlm_msg and so msg->idx can contain

garbage which is signaled by the following warning:

[ 676.237050] ------------[ cut here ]------------

[ 676.237052] WARNING: CPU: 0 PID: 1060 at include/linux/srcu.h:189 dlm_lowcomms_commit_msg+0x41/0x50

[ 676.238945] Modules linked in: dlm_locktorture torture rpcsec_gss_krb5 intel_rapl_msr intel_rapl_common iTCO_wdt iTCO_vendor_support qxl kvm_intel drm_ttm_helper vmw_vsock_virtio_transport kvm vmw_vsock_virtio_transport_common ttm irqbypass crc32_pclmul joydev crc32c_intel serio_raw drm_kms_helper vsock virtio_scsi virtio_console virtio_balloon snd_pcm drm syscopyarea sysfillrect sysimgblt snd_timer fb_sys_fops i2c_i801 lpc_ich snd i2c_smbus soundcore pcspkr

[ 676.244227] CPU: 0 PID: 1060 Comm: lo

Why It Matters

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

    References & Sources

  • https://git.kernel.org/stable/c/27d3e646dd83bafd7094890462eebfce3ac31e4a
  • https://git.kernel.org/stable/c/30ea3257e8766027c4d8d609dcbd256ff9a76073
  • https://git.kernel.org/stable/c/de7fdff754bb4d01e38e19964c309b6df6a79472
  • https://git.kernel.org/stable/c/eb97e60a9eae632ff9104a580dbc4fdc58dc23cb

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

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

    fs: dlm: fix race in lowcomms

    This patch fixes a race between queue_work() in

    _dlm_lowcomms_commit_msg() and srcu_read_unlock(). T

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