cve/2024/CVE-2024-40945.md
2025-09-29 21:09:30 +02:00

20 lines
1.3 KiB
Markdown

### [CVE-2024-40945](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40945)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=26b25a2b98e45aeb40eedcedc586ad5034cbd984%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=5.2%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)
### Description
In the Linux kernel, the following vulnerability has been resolved:iommu: Return right value in iommu_sva_bind_device()iommu_sva_bind_device() should return either a sva bond handle or anERR_PTR value in error cases. Existing drivers (idxd and uacce) onlycheck the return value with IS_ERR(). This could potentially lead toa kernel NULL pointer dereference issue if the function returns NULLinstead of an error pointer.In reality, this doesn't cause any problems because iommu_sva_bind_device()only returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA.In this case, iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) willreturn an error, and the device drivers won't call iommu_sva_bind_device()at all.
### POC
#### Reference
No PoCs from references.
#### Github
- https://github.com/w4zu/Debian_security