Wind River Support Network

Description

In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]erofs: wake up all waiters after z_erofs_lzma_head ready[EOL][EOL]When the user mounts the erofs second times, the decompression thread[EOL]may hung. The problem happens due to a sequence of steps like the[EOL]following:[EOL][EOL]1) Task A called z_erofs_load_lzma_config which obtain all of the node[EOL]   from the z_erofs_lzma_head.[EOL][EOL]2) At this time, task B called the z_erofs_lzma_decompress and wanted to[EOL]   get a node. But the z_erofs_lzma_head was empty, the Task B had to[EOL]   sleep.[EOL][EOL]3) Task A release nodes and push nodes into the z_erofs_lzma_head. But[EOL]   task B was still sleeping.[EOL][EOL]One example report when the hung happens:[EOL]task:kworker/u3:1 state:D stack:14384 pid: 86 ppid: 2 flags:0x00004000[EOL]Workqueue: erofs_unzipd z_erofs_decompressqueue_work[EOL]Call Trace:[EOL] <TASK>[EOL] __schedule+0x281/0x760[EOL] schedule+0x49/0xb0[EOL] z_erofs_lzma_decompress+0x4bc/0x580[EOL] ? cpu_core_flags+0x10/0x10[EOL] z_erofs_decompress_pcluster+0x49b/0xba0[EOL] ? __update_load_avg_se+0x2b0/0x330[EOL] ? __update_load_avg_se+0x2b0/0x330[EOL] ? update_load_avg+0x5f/0x690[EOL] ? update_load_avg+0x5f/0x690[EOL] ? set_next_entity+0xbd/0x110[EOL] ? _raw_spin_unlock+0xd/0x20[EOL] z_erofs_decompress_queue.isra.0+0x2e/0x50[EOL] z_erofs_decompressqueue_work+0x30/0x60[EOL] process_one_work+0x1d3/0x3a0[EOL] worker_thread+0x45/0x3a0[EOL] ? process_one_work+0x3a0/0x3a0[EOL] kthread+0xe2/0x110[EOL] ? kthread_complete_and_exit+0x20/0x20[EOL] ret_from_fork+0x22/0x30[EOL] </TASK>

CREATE(Triage):(User=lchen-cn) [CVE-2022-50193 (https://nvd.nist.gov/vuln/detail/CVE-2022-50193)