Vulnerability · Published Apr 4, 2024 · Assigned by Linux
CVE-2024-26788dmaengine: fsl-qdma: init irq after reg initialization
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.82-1 | DEBIAN-CVE-2024-26788 |
| Debian:13 | linux | 6.7.9-1 | DEBIAN-CVE-2024-26788 |
| Debian:14 | linux | 6.7.9-1 | DEBIAN-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux | 5.15.0-112.122 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1063.69 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1066.75 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1067.76.1 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1062.70 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1060.66 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1046.53 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1056.59 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1058.64 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1060.65 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-110.120 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1058.59 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1026.26 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1015.15 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1061.67 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1058.61 | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-26788 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1030.34 | UBUNTU-CVE-2024-26788 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | b092529e0aa09829a6404424ce167bf3ce3235e2 – before 3cc5fb824c2125aa3740d905b3e5b378c8a09478b092529e0aa09829a6404424ce167bf3ce3235e2 – before 9579a21e99fe8dab22a253050ddff28d340d74e1b092529e0aa09829a6404424ce167bf3ce3235e2 – before 4529c084a320be78ff2c5e64297ae998c6fdf66bb092529e0aa09829a6404424ce167bf3ce3235e2 – before 474d521da890b3e3585335fb80a6044cb2553d99b092529e0aa09829a6404424ce167bf3ce3235e2 – before a69c8bbb946936ac4eb6a6ae1e849435aa8d947db092529e0aa09829a6404424ce167bf3ce3235e2 – before 677102a930643c31f1b4c512b041407058bdfef8b092529e0aa09829a6404424ce167bf3ce3235e2 – before 87a39071e0b639f45e05d296cc0538eef44ec0bd |
| Linux | Linux | 5.1 |
References
- https://git.kernel.org/stable/c/3cc5fb824c2125aa3740d905b3e5b378c8a09478
- https://git.kernel.org/stable/c/9579a21e99fe8dab22a253050ddff28d340d74e1
- https://git.kernel.org/stable/c/4529c084a320be78ff2c5e64297ae998c6fdf66b
- https://git.kernel.org/stable/c/474d521da890b3e3585335fb80a6044cb2553d99
- https://git.kernel.org/stable/c/a69c8bbb946936ac4eb6a6ae1e849435aa8d947d
- https://git.kernel.org/stable/c/677102a930643c31f1b4c512b041407058bdfef8
- https://git.kernel.org/stable/c/87a39071e0b639f45e05d296cc0538eef44ec0bd
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html x_transferred