CVE-2024-42271
Linux Kernel vulnerability analysis and mitigation

Overview

CVE-2024-42271 is a use-after-free vulnerability discovered in the Linux kernel's IUCV (Inter-User Communication Vehicle) network implementation. The vulnerability specifically affects the iucv_sock_close() function in the net/iucv subsystem. This issue affects Linux kernel versions from 3.4 through 6.10.4, as identified on August 17, 2024 (NVD).

Technical details

The vulnerability occurs when iucv_sever_path() is called from both process context and bh (bottom half) context. The issue stems from improper synchronization of iucv->path, which is used as an indicator for path severing status. The vulnerability manifests due to a race condition where iucv_sock_close() attempts to work with a path that has already been severed and freed by iucv_callback_connrej() called by iucv_tasklet_fn(). The CVSS v3.1 base score is 7.8 (High), with the vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (NVD).

Impact

The vulnerability can lead to a kernel panic and system crash, as demonstrated by the provided call trace. In more severe cases, it could potentially result in memory corruption and unauthorized access to kernel memory. The high CVSS score indicates potential for significant impact on system confidentiality, integrity, and availability (NVD).

Exploitability

The vulnerability requires local access with low privileges to exploit. The attack complexity is considered low, and no user interaction is required for exploitation. The vulnerability has been observed to cause kernel panics in real-world scenarios, as evidenced by the provided call trace in the kernel patch (Kernel Patch).

Mitigation and workarounds

The issue has been fixed by implementing atomic compare and swap operations for handling the path pointer. The fix involves replacing the direct path assignment with xchg(&iucv->path, NULL) to ensure proper synchronization. System administrators should update to patched kernel versions. Two potential future clean-up approaches have been suggested: implementing correct usage of bh_lock_sock() in tasklet context or changing the iucv tasklet into a worker and using only lock_sock() in af_iucv (Kernel Patch).

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-74573CRITICAL9.3
  • Linux Kernel logoLinux Kernel
  • kernel-64k-debug-devel-matched
NoYesAug 15, 2026
CVE-2026-74562HIGH8.8
  • Linux Kernel logoLinux Kernel
  • kernel-64k-debug-devel-matched
NoYesAug 15, 2026
CVE-2026-74565HIGH7.8
  • Linux Kernel logoLinux Kernel
  • kernel-uki-virt
NoYesAug 15, 2026
CVE-2026-74578HIGH7.1
  • Linux Kernel logoLinux Kernel
  • linux-nvidia-tegra
NoYesAug 16, 2026
CVE-2026-74579NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-xilinx-zynqmp
NoYesAug 17, 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