Loading story…
CVE-2022-50053 is a Linux kernel denial-of-service flaw in the Intel Adaptive Virtual Function (iavf) network driver. During rapid virtual-function resets, a VF mailbox initialization failure can send iavf_reset_task through an erroneous cleanup path that calls iavf_close; this invokes napi_disable twice, deadlocking the driver. The resulting lock contention can leave iavf_remove blocked, produce hung tasks, and potentially cause a kernel panic.
The flaw affects code introduced in Linux kernel 4.14 and was fixed upstream in versions 5.15.63, 5.19.4, and 6.0 by using iavf_disable_vf to safely clean up invalid resources. Red Hat rates the issue Moderate with a CVSS v3.1 score of 7.0 and has released fixes for affected RHEL 8, RHEL 9, Red Hat Virtualization 4 for RHEL 8, and RHEL 7 Extended Lifecycle Support packages; RHEL 8 kernel-rt remains affected without a qualifying mitigation. Organizations using Intel VF networking should apply the applicable kernel updates or move to a current stable kernel.
See affected versions and whether adversaries are exploiting it.
9 events from the most recent confirmed update back to the earliest known activity.
Red Hat released RHSA-2026:10756, addressing CVE-2022-50053 in Red Hat Enterprise Linux 7 Extended Lifecycle Support kernel-rt packages.
Red Hat released RHSA-2026:9870, addressing CVE-2022-50053 in Red Hat Enterprise Linux 7 Extended Lifecycle Support kernel packages.
The Linux kernel iavf reset-error handling flaw was published as CVE-2022-50053. The issue can deadlock a system and cause denial of service when a reset failure invokes iavf_close and calls napi_disable twice.
Red Hat released RHSA-2023:2458 with a further fix for affected Red Hat Enterprise Linux 9 kernel packages.
Red Hat released RHSA-2023:0334 to fix CVE-2022-50053 in affected Red Hat Enterprise Linux 9 kernel packages.
Red Hat released RHSA-2022:7683 with an additional fix for affected Red Hat Enterprise Linux 8 kernel packages.
Red Hat released RHSA-2022:7110, providing a fix for affected Red Hat Enterprise Linux 8 kernel packages and Red Hat Virtualization 4 for RHEL 8.
Linux kernel releases 5.15.63, 5.19.4, and 6.0 included fixes that replace the erroneous cleanup path with iavf_disable_vf, preventing the double napi_disable deadlock during failed VF mailbox setup.
The iavf driver's vulnerable reset-error handling was introduced in Linux kernel 4.14 by commit f0db78928783f0a4cce4940e8c03c2e9a760e629. The flaw could call iavf_close during reset failure handling, leading to a duplicate napi_disable call and deadlock.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
bugzilla.redhat.com
Open sourceredhat.com
Open sourcelore.kernel.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
**CVE-2021-47284** affects the Linux kernel's mISDN Netjet ISDN driver (`drivers/isdn/hardware/mISDN/netjet.c`). When `nj_setup` fails with `-EIO` after the driver initializes `card->irq`, its cleanup routine can call `free_irq` for an interrupt that was never requested. This produces a kernel warning and can crash the system when `panic_on_warn` is enabled, creating a locally exploitable availability risk for systems using the affected hardware. The fix removes the premature IRQ assignment and preserves assignment immediately before `request_irq`. Fixed Linux stable releases include 4.4.273, 4.9.273, 4.14.237, 4.19.195, 5.4.126, 5.10.44, 5.12.11, and 5.13; organizations should deploy a current stable kernel. Red Hat rated the issue **Low** severity (CVSS 3.1: 5.5) and issued fixes for RHEL 8 `kernel` and `kernel-rt`; RHEL 9 is not affected, while RHEL 6 and 7 are out of support.
Aug 26, 2026
**CVE-2024-26939** is a use-after-free flaw in the Linux kernel's Intel i915 DRM graphics driver, in `drivers/gpu/drm/i915/i915_vma.c`. A race between i915 VMA destruction and asynchronous retirement can free a VMA while retirement logic still accesses it, allowing a local low-privileged attacker to crash the affected system. The vulnerability was introduced in Linux 5.19 and can produce debug-object warnings when a GPU GT is parked. The issue is fixed upstream in Linux kernel versions 6.1.88, 6.6.29, 6.8.3, and 6.9-rc2 and later stable releases. Red Hat has issued fixes for RHEL 8, RHEL 8 kernel-rt, RHEL 9, and RHEL 9.4 Extended Update Support; RHEL 9 kernel-rt is marked will not fix, while RHEL 6 and 7 variants are outside support scope. Red Hat rates the flaw Moderate at CVSS 5.5, compared with scores of 7.0 from NVD and 7.8 from CVE.org.
Aug 26, 2026
**CVE-2023-42754** is a moderate-severity NULL-pointer dereference in the Linux kernel IPv4 routing stack that can allow a local attacker to crash an affected host. When traffic is rerouted through IPVS, an `sk_buff` may lack an associated network device, but `ipv4_send_dest_unreach()` assumes `skb->dev` is present and dereferences it through `dev_net(skb->dev)`, triggering a kernel panic. A proof of concept produced a KASAN-detected fault and fatal panic on a Linux 6.1.47+ test kernel. The upstream correction, commit `0113d9c9d1ccc07f5a3710dac4aa24b6d711278c`, was incorporated in Linux 6.6-rc3 and queued for stable kernel branches from 4.14 through 6.5. Red Hat rates the issue CVSS 5.5, with high availability impact and no confidentiality or integrity impact; fixed kernel packages are available for RHEL 8 and RHEL 9, while RHEL 9 `kernel-rt` remained affected in Red Hat's advisory. RHEL 6, RHEL 7, and RHEL 7 `kernel-rt` are not affected, and Red Hat lists no qualifying mitigation beyond applying updated packages.
Aug 26, 2026