Description (CNA)
In the Linux kernel, the following vulnerability has been resolved: intel_th: msu: Fix vmalloced buffers After commit f5ff79fddf0e ("dma-mapping: remove CONFIG_DMA_REMAP") there's a chance of DMA buffer getting allocated via vmalloc(), which messes up the mmapping code: > RIP: msc_mmap_fault [intel_th_msu] > Call Trace: > <TASK> > __do_fault > do_fault ... Fix this by accounting for vmalloc possibility.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected ba39bd8306057fb343dfb75d93a76d824b625236 before b5d924cb4c7b952eaa61622f14427723a78137a3; affected ba39bd8306057fb343dfb75d93a76d824b625236 before 6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828; affected ba39bd8306057fb343dfb75d93a76d824b625236 before 566887bad7ff2297d6b3f9659c702ba075f3d62d; affected ba39bd8306057fb343dfb75d93a76d824b625236 before 0ed72c6bc632cbf8d979ac60f982ff84b7bb610a; affected ba39bd8306057fb343dfb75d93a76d824b625236 before 4914c50670b6a531e2cb17cd984cc565b4681312; affected ba39bd8306057fb343dfb75d93a76d824b625236 before ac12ad3ccf6d386e64a9d6a890595a2509d24edd |
| Linux / Linux | affected 5.2; unaffected 0 before 5.2; unaffected 5.4.211 through 5.4.*; unaffected 5.10.137 through 5.10.*; unaffected 5.15.61 through 5.15.*; unaffected 5.18.18 through 5.18.*; unaffected 5.19.2 through 5.19.*; unaffected 6.0 through * |
CWE
No CWE identifiers supplied.
References
- https://git.kernel.org/stable/c/b5d924cb4c7b952eaa61622f14427723a78137a3
- https://git.kernel.org/stable/c/6ae2881c1d1fa0e33f4763b7c786f8ef05a9c828
- https://git.kernel.org/stable/c/566887bad7ff2297d6b3f9659c702ba075f3d62d
- https://git.kernel.org/stable/c/0ed72c6bc632cbf8d979ac60f982ff84b7bb610a
- https://git.kernel.org/stable/c/4914c50670b6a531e2cb17cd984cc565b4681312
- https://git.kernel.org/stable/c/ac12ad3ccf6d386e64a9d6a890595a2509d24edd