CVE-2024-26838: RDMA/irdma: Fix KASAN issue with tasklet
In the Linux kernel, the following vulnerability has been resolved:
RDMA/irdma: Fix KASAN issue with tasklet
KASAN testing revealed the following issue assocated with freeing an IRQ.
[50006.466686] Call Trace:
[50006.466691] <IRQ>
[50006.489538] dump_stack+0x5c/0x80
[50006.493475] print_address_description.constprop.6+0x1a/0x150
[50006.499872] ? irdma_sc_process_ceq+0x483/0x790 [irdma]
[50006.505742] ? irdma_sc_process_ceq+0x483/0x790 [irdma]
[50006.511644] kasan_report.cold.11+0x7f/0x118
[50006.516572] ? irdma_sc_process_ceq+0x483/0x790 [irdma]
[50006.522473] irdma_sc_process_ceq+0x483/0x790 [irdma]
[50006.528232] irdma_process_ceq+0xb2/0x400 [irdma]
[50006.533601] ? irdma_hw_flush_wqes_callback+0x370/0x370 [irdma]
[50006.540298] irdma_ceq_dpc+0x44/0x100 [irdma]
[50006.545306] tasklet_action_common.isra.14+0x148/0x2c0
[50006.551096] __do_softirq+0x1d0/0xaf8
[50006.555396] irq_exit_rcu+0x219/0x260
[50006.559670] irq_exit+0xa/0x20
[50006.563320] smp_apic_timer_interrupt+0x1bf/0x690
[50006.568645] apic_timer_interrupt+0xf/0x20
[50006.573341] </IRQ>
The issue is that a tasklet could be pending on another core racing
the delete of the irq.
Fix by insuring any scheduled tasklet is killed after deleting the
irq.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux irdma RDMA driver can leave deferred interrupt work running while an IRQ is being removed. On an affected system, a locally privileged user may be able to trigger serious memory corruption, potentially affecting confidentiality, integrity, and availability.
Executive priority
Prioritize affected RDMA hosts because successful exploitation could have system-wide impact. Treat patching as high priority, especially on shared or multi-user systems where untrusted local users have accounts. Internet-facing status alone does not determine exposure because the stated attack vector is local.
Technical view
A scheduled tasklet can remain pending on another CPU while the irdma driver deletes its IRQ. Subsequent CEQ processing may access invalid state, as detected by KASAN. The kernel fix kills scheduled tasklets after IRQ deletion. CVSS 3.1 rates the issue 7.8 with local, low-privilege, no-user-interaction access.
Likely exposure
Exposure is limited to affected Linux kernels using the RDMA irdma driver and relevant hardware or configuration. Systems without this driver loaded or used are less likely to be exposed. The supplied version data is ambiguous, so distribution-specific package status should determine applicability.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as being in CISA KEV. The CVSS vector requires local access and low privileges. No evidence provided establishes reliable exploitation, internet-scale exposure, or a specific attacker campaign.
Researcher notes
The record describes a cross-core tasklet-versus-IRQ-deletion race in irdma CEQ processing. Multiple stable-kernel commits are supplied, but the normalized affected-version list lacks clear ranges and should not be treated as a complete package matrix. No CWE, proof of exploitation, or exploit reliability evidence is provided.
Mitigation direction
Install a supported kernel update containing the vendor's CVE-2024-26838 fix.
Check Linux distribution advisories for the exact fixed package version.
Where operationally acceptable, disable or avoid loading unused irdma functionality until patched.
Schedule a reboot if required to activate the updated kernel.
Validation and detection
Inventory kernel versions and identify systems with the irdma module loaded or configured.
Compare installed packages against distribution guidance for CVE-2024-26838.
Confirm the running kernel changed after patching and any required reboot.
Review kernel logs for irdma, KASAN, tasklet, IRQ, or memory-corruption warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26838 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.