LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26788: dmaengine: fsl-qdma: init irq after reg initialization

In the Linux kernel, the following vulnerability has been resolved: dmaengine: fsl-qdma: init irq after reg initialization Initialize the qDMA irqs after the registers are configured so that interrupts that may have been pending from a primary kernel don't get processed by the irq handler before it is ready to and cause panic with the following trace: Call trace: fsl_qdma_queue_handler+0xf8/0x3e8 __handle_irq_event_percpu+0x78/0x2b0 handle_irq_event_percpu+0x1c/0x68 handle_irq_event+0x44/0x78 handle_fasteoi_irq+0xc8/0x178 generic_handle_irq+0x24/0x38 __handle_domain_irq+0x90/0x100 gic_handle_irq+0x5c/0xb8 el1_irq+0xb8/0x180 _raw_spin_unlock_irqrestore+0x14/0x40 __setup_irq+0x4bc/0x798 request_threaded_irq+0xd8/0x190 devm_request_threaded_irq+0x74/0xe8 fsl_qdma_probe+0x4d4/0xca8 platform_drv_probe+0x50/0xa0 really_probe+0xe0/0x3f8 driver_probe_device+0x64/0x130 device_driver_attach+0x6c/0x78 __driver_attach+0xbc/0x158 bus_for_each_dev+0x5c/0x98 driver_attach+0x20/0x28 bus_add_driver+0x158/0x220 driver_register+0x60/0x110 __platform_driver_register+0x44/0x50 fsl_qdma_driver_init+0x18/0x20 do_one_initcall+0x48/0x258 kernel_init_freeable+0x1a4/0x23c kernel_init+0x10/0xf8 ret_from_fork+0x10/0x18

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel stability vulnerability in the Freescale qDMA driver. On affected systems, pending interrupts can be handled before the driver is fully ready, causing a kernel panic. The business impact is availability, not confirmed data theft or remote compromise.

Executive priority

Treat this as a targeted availability issue for specialized Linux platforms. Patch affected qDMA systems through normal kernel maintenance, escalating if those systems support critical operations or have shown boot-time panics.

Technical view

The fsl-qdma dmaengine driver requested IRQ handling before qDMA registers were fully initialized. Pending interrupts from a primary kernel could reach fsl_qdma_queue_handler during probe and trigger a panic. Stable kernel commits reorder initialization so registers are configured before IRQ setup.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the fsl-qdma driver and compatible qDMA hardware. General Linux fleets without this driver or hardware are less likely to be affected.

Exploitation context

The bundle does not show KEV listing, active exploitation, public exploit use, CVSS, or CWE data. The described failure mode is a kernel panic during driver initialization, suggesting availability risk under specific platform conditions.

Researcher notes

The strongest evidence is the upstream kernel fix description and stable backports. Severity scoring is absent, affected version data is broad, and exploitation evidence is not provided. Validate exposure by hardware, driver use, and downstream package status.

Mitigation direction

  • Update to a vendor or distribution kernel containing the referenced stable fixes.
  • Review Debian LTS and other distribution advisories for fixed package versions.
  • Prioritize systems using Freescale/NXP qDMA hardware or the fsl-qdma driver.
  • If patch timing is unclear, follow kernel or distribution vendor guidance.

Validation and detection

  • Inventory Linux kernel versions against the affected and fixed ranges in vendor advisories.
  • Confirm whether the fsl-qdma driver is built, loaded, or required on target systems.
  • Check boot and kernel logs for fsl_qdma_queue_handler panic traces.
  • Verify patched kernels include one of the referenced stable commits or downstream backports.
Prepared
Confidence
medium
Sources
10

Public sources used

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-26788 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb092529e0aa09829a6404424ce167bf3ce3235e2, b092529e0aa09829a6404424ce167bf3ce3235e2, b092529e0aa09829a6404424ce167bf3ce3235e2, b092529e0aa09829a6404424ce167bf3ce3235e2, b092529e0aa09829a6404424ce167bf3ce3235e2, b092529e0aa09829a6404424ce167bf3ce3235e2, b092529e0aa09829a6404424ce167bf3ce3235e2unaffected
LinuxLinux5.1, 0, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.