DEBIAN-CVE-2022-50774

In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix DMA transfer direction When CONFIGDMAAPIDEBUG is selected, while running the crypto self test on the QAT crypto algorithms, the function adddmaentry() reports a warning similar to the one below, saying that overlapping mappings are not supported. This occurs in tests where the input and the output scatter list point to the same buffers (i.e. two different scatter lists which point to the same chunks of memory). The logic that implements the mapping uses the flag DMABIDIRECTIONAL for both the input and the output scatter lists which leads to overlapped write mappings. These are not supported by the DMA layer. Fix by specifying the correct DMA transfer directions when mapping buffers. For in-place operations where the input scatter list matches the output scatter list, buffers are mapped once with DMABIDIRECTIONAL, otherwise input buffers are mapped using the flag DMATODEVICE and output buffers are mapped with DMAFROMDEVICE. Overlapping a read mapping with a write mapping is a valid case in dma-coherent devices like QAT. The function that frees and unmaps the buffers, qatalgfreebufl() has been changed accordingly to the changes to the mapping function. DMA-API: 4xxx 0000:06:00.0: cacheline tracking EEXIST, overlapping mappings aren't supported WARNING: CPU: 53 PID: 4362 at kernel/dma/debug.c:570 adddmaentry+0x1e9/0x270 ... Call Trace: dmamappageattrs+0x82/0x2d0 ? preemptcountadd+0x6a/0xa0 qatalgsgltobufl+0x45b/0x990 [intelqat] qatalgaeaddec+0x71/0x250 [intelqat] cryptoaeaddecrypt+0x3d/0x70 testaeadveccfg+0x649/0x810 ? number+0x310/0x3a0 ? vsnprintf+0x2a3/0x550 ? scnprintf+0x42/0x70 ? validsgdivisions.constprop.0+0x86/0xa0 ? testaeadvec+0xdf/0x120 testaeadvec+0xdf/0x120 algtestaead+0x185/0x400 algtest+0x3d8/0x500 ? cryptoacompscompfreectx+0x30/0x30 ? _schedule+0x32a/0x12a0 ? ttwuqueuewakelist+0xbf/0x110 ? _rawspinunlockirqrestore+0x23/0x40 ? trytowakeup+0x83/0x570 ? _rawspinunlockirqrestore+0x23/0x40 ? _setcpusallowedptrlocked+0xea/0x1b0 ? cryptoacompscompfreectx+0x30/0x30 cryptomgrtest+0x27/0x50 kthread+0xe6/0x110 ? kthreadcompleteandexit+0x20/0x20 retfrom_fork+0x1f/0x30