In the Linux kernel, the following vulnerability has been resolved: mmc: jz4740: Apply DMA engine limits to maximum segment size Do what is done in other DMA-enabled MMC host drivers (cf. host/mmci.c) and limit the maximum segment size based on the DMA engine's capabilities. This is needed to avoid warnings like the following with CONFIG_DMA_API_DEBUG=y. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 21 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2f4/0x39c DMA-API: jz4780-dma 13420000.dma-controller: mapping sg segment longer than device claims to support [len=98304] [max=65536] CPU: 0 PID: 21 Comm: kworker/0:1H Not tainted 5.18.0-rc1 #19 Workqueue: kblockd blk_mq_run_work_fn Stack : 81575aec 00000004 80620000 80620000 80620000 805e7358 00000009 801537ac 814c832c 806276e3 806e34b4 80620000 81575aec 00000001 81575ab8 09291444 00000000 00000000 805e7358 81575958 ffffffea 8157596c 00000000 636f6c62 6220646b 80387a70 0000000f 6d5f6b6c 80620000 00000000 81575ba4 00000009 805e170c 80896640 00000001 00010000 00000000 00000000 00006098 806e0000 ... Call Trace: [] show_stack+0x84/0x120 [] __warn+0xb8/0xec [] warn_slowpath_fmt+0x6c/0xb8 [] debug_dma_map_sg+0x2f4/0x39c [] __dma_map_sg_attrs+0xf0/0x118 [] dma_map_sg_attrs+0x14/0x28 [] jz4740_mmc_prepare_dma_data+0x74/0xa4 [] jz4740_mmc_pre_request+0x30/0x54 [] mmc_blk_mq_issue_rq+0x6e0/0x7bc [] mmc_mq_queue_rq+0x220/0x2d4 [] blk_mq_dispatch_rq_list+0x480/0x664 [] blk_mq_do_dispatch_sched+0x2dc/0x370 [] __blk_mq_sched_dispatch_requests+0xec/0x164 [] blk_mq_sched_dispatch_requests+0x44/0x94 [] __blk_mq_run_hw_queue+0xb0/0xcc [] process_one_work+0x1b8/0x264 [] worker_thread+0x2ec/0x3b8 [] kthread+0x104/0x10c [] ret_from_kernel_thread+0x14/0x1c ---[ end trace 0000000000000000 ]---
This Cyber News was published on www.tenable.com. Publication date: Thu, 27 Feb 2025 02:56:03 +0000