CVE-2024-46716: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: altera-msgdma: properly free descriptor in msgdmafreedescriptor
Remove listdel call in msgdmachandesccleanup, this should be the role of msgdmafreedescriptor. In consequence replace listaddtail with listmovetail in msgdmafreedescriptor.
This fixes the path: msgdmafreechanresources -> msgdmafreedescriptors -> msgdmafreedesclist -> msgdmafreedescriptor
which does not correctly free the descriptors as first nodes were not removed from the list.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Configuration
In dmaengine/altera-msgdma, in msgdma_free_descriptor replace list_add_tail with list_move_tail.
Linux kernel (dmaengine: altera-msgdma) Use list_move_tail instead of list_add_tail in msgdma_free_descriptor = list_move_tail (replace list_add_tail) - Configuration
In dmaengine/altera-msgdma, remove the list_del call in msgdma_chan_desc_cleanup, so descriptor removal/freeing is handled by msgdma_free_descriptor.
Linux kernel (dmaengine: altera-msgdma) Remove list_del call in msgdma_chan_desc_cleanup = remove list_del call
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46716?
CVE-2024-46716 is classified as a moderate severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-46716?
To fix CVE-2024-46716, ensure your Linux kernel is updated to versions 6.1.123-1, 6.1.119-1, 6.12.9-1, or 6.12.10-1.
Which systems are affected by CVE-2024-46716?
CVE-2024-46716 affects Debian Linux packages such as linux and linux-6.1.
What type of vulnerability is CVE-2024-46716?
CVE-2024-46716 is a memory management issue related to descriptor handling in the dmaengine of the Linux kernel.
Is there a workaround for CVE-2024-46716?
There are no known workarounds for CVE-2024-46716; applying the appropriate updates is recommended.