CVE-2022-50705
Linux Kernel vulnerability analysis and mitigation

Overview

CVE-2022-50705 is a vulnerability in the Linux kernel's io_uring subsystem, specifically in the read/write (rw) path, where fsnotify calls are incorrectly made from kiocb completion context, which may execute in soft or hard IRQ context. The fix defers these calls to task context when processing task_work for the request, avoiding invalid locking states detected by lockdep. It was published on December 24, 2025, and affects the Linux kernel. No CVSS score has been officially assigned at this time (Feedly, CVE.org).

Technical details

The root cause is improper context handling (CWE-362 or improper synchronization) in the io_uring/rw subsystem: fsnotify calls are triggered from kiocb completion handlers that may run in soft or hard IRQ context, where memory allocation and certain locking operations are not permitted. This triggers lockdep warnings because fs_reclaim_acquire is called from IRQ context, violating locking rules — specifically, the kernel's memory reclaim lock cannot be acquired in interrupt context. The fix defers fsnotify invocations to task_work processing, ensuring they run in safe task context (Feedly). Patch commits are available in the stable kernel tree at git.kernel.org (commits 2a853c206e55, 89a410dbd0f1, b000145e9907).

Impact

Exploitation or triggering of this bug can cause kernel instability or a system crash (denial of service) due to invalid locking state violations detected by lockdep in IRQ context. The vulnerability primarily affects availability; there is no direct evidence of confidentiality or integrity impact. Systems using io_uring for asynchronous I/O with filesystem notification (fsnotify/inotify) are most at risk (Feedly).

Mitigation and workarounds

Apply the upstream Linux kernel patches that defer fsnotify calls to task context in io_uring/rw. The relevant stable kernel commits are 2a853c206e55, 89a410dbd0f1, and b000145e9907 on git.kernel.org. SUSE has issued advisories (SUSE-2026:0263-1 and SUSE-2026:0317-1) addressing this CVE in their kernel packages; users of SUSE Linux should apply the available updates (Feedly, Linux Security SUSE). As a workaround, disabling io_uring (via sysctl kernel.io_uring_disabled=1 on supported kernels) would mitigate exposure, though this impacts application performance.

Community reactions

SUSE Linux has issued kernel security updates addressing CVE-2022-50705 as part of broader kernel patch batches in early 2026 (Linux Security SUSE, Linux Compatible). No notable independent researcher commentary or significant social media discussion has been identified for this vulnerability.

Additional resources


SourceThis report was generated using AI

Related Linux Kernel vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-64557NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-selftests-internal
NoNoJul 29, 2026
CVE-2026-64556NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-64k-devel
NoNoJul 29, 2026
CVE-2026-64555NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-azure-fde-6.14
NoNoJul 27, 2026
CVE-2026-64554NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-gcp-6.14
NoYesJul 27, 2026
CVE-2026-64553NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-64k-debug-modules-internal
NoYesJul 27, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management