CVE-2024-40979 in Linux
Sumário
de VulDB • 11/05/2026
No, the kernel did not crash because of a memory leak or a size mismatch in `dma_free_coherent`. The crash described in the truncated text is a **hypothetical scenario** or a **bug report explanation** illustrating *why* the current code is broken, not what actually happened in a stable system.
Here’s the breakdown:
### 1. The Log Shows Normal Operation The `dmesg` output you provided shows the **QMI (Qualcomm Modem Interface) memory segment allocation** during firmware loading/resume. These messages are informational and indicate that the driver is successfully requesting memory segments from the firmware. The fact that "ath12k is working" confirms that the driver loaded and initialized correctly.
### 2. The Truncated Text Describes a Bug, Not a Crash The text after the logs is **not** a continuation of the `dmesg` output. It is a **developer’s analysis** of a bug in the `ath12k` driver’s suspend/resume handling. It explains:
- **What happens during resume:** The firmware requests two large memory segments. - **What goes wrong:** The driver tries to allocate these segments. If allocation fails, it calls `ath12k_qmi_free_target_mem_chunk()` to clean up. - **The bug:** - The first segment’s `v.addr` is cleared due to allocation failure, so it’s skipped during free (causing a **memory leak**). - The second segment’s size is incorrectly set to a large value (8454144) instead of its actual allocated size (524288). When `dma_free_coherent()` is called with this wrong size, it **would** cause a kernel panic/crash if it actually happened.
### 3. Why No Crash Occurred - The crash described is **potential**, not actual. It illustrates a flaw in the error-handling path. - In your case, the driver loaded successfully ("ath12k is working"), meaning the allocation likely succeeded, or the error path was not triggered in a way that caused a crash. - If the allocation had failed and the buggy free path was executed, **yes, it would crash** due to the size mismatch in `dma_free_coherent()`.
### Conclusion - **Your system is stable:** The `dmesg` logs show normal firmware loading. - **The text describes a known bug:** The `ath12k` driver has a flaw in its suspend/resume memory management that could cause a crash if allocation fails during resume. This is likely being fixed in newer kernel versions. - **No action needed:** If your Wi-Fi is working, you’re fine. If you encounter crashes during suspend/resume, consider updating your kernel to a version that includes the fix for this `ath12k` bug.
If you want to get best quality of vulnerability data, you may have to visit VulDB.