Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block, bfq: fix bfqq uaf in bfq_limit_depth()<br /> <br /> Set new allocated bfqq to bic or remove freed bfqq from bic are both<br /> protected by bfqd-&gt;lock, however bfq_limit_depth() is deferencing bfqq<br /> from bic without the lock, this can lead to UAF if the io_context is<br /> shared by multiple tasks.<br /> <br /> For example, test bfq with io_uring can trigger following UAF in v6.6:<br /> <br /> ==================================================================<br /> BUG: KASAN: slab-use-after-free in bfqq_group+0x15/0x50<br /> <br /> Call Trace:<br /> <br /> dump_stack_lvl+0x47/0x80<br /> print_address_description.constprop.0+0x66/0x300<br /> print_report+0x3e/0x70<br /> kasan_report+0xb4/0xf0<br /> bfqq_group+0x15/0x50<br /> bfqq_request_over_limit+0x130/0x9a0<br /> bfq_limit_depth+0x1b5/0x480<br /> __blk_mq_alloc_requests+0x2b5/0xa00<br /> blk_mq_get_new_requests+0x11d/0x1d0<br /> blk_mq_submit_bio+0x286/0xb00<br /> submit_bio_noacct_nocheck+0x331/0x400<br /> __block_write_full_folio+0x3d0/0x640<br /> writepage_cb+0x3b/0xc0<br /> write_cache_pages+0x254/0x6c0<br /> write_cache_pages+0x254/0x6c0<br /> do_writepages+0x192/0x310<br /> filemap_fdatawrite_wbc+0x95/0xc0<br /> __filemap_fdatawrite_range+0x99/0xd0<br /> filemap_write_and_wait_range.part.0+0x4d/0xa0<br /> blkdev_read_iter+0xef/0x1e0<br /> io_read+0x1b6/0x8a0<br /> io_issue_sqe+0x87/0x300<br /> io_wq_submit_work+0xeb/0x390<br /> io_worker_handle_work+0x24d/0x550<br /> io_wq_worker+0x27f/0x6c0<br /> ret_from_fork_asm+0x1b/0x30<br /> <br /> <br /> Allocated by task 808602:<br /> kasan_save_stack+0x1e/0x40<br /> kasan_set_track+0x21/0x30<br /> __kasan_slab_alloc+0x83/0x90<br /> kmem_cache_alloc_node+0x1b1/0x6d0<br /> bfq_get_queue+0x138/0xfa0<br /> bfq_get_bfqq_handle_split+0xe3/0x2c0<br /> bfq_init_rq+0x196/0xbb0<br /> bfq_insert_request.isra.0+0xb5/0x480<br /> bfq_insert_requests+0x156/0x180<br /> blk_mq_insert_request+0x15d/0x440<br /> blk_mq_submit_bio+0x8a4/0xb00<br /> submit_bio_noacct_nocheck+0x331/0x400<br /> __blkdev_direct_IO_async+0x2dd/0x330<br /> blkdev_write_iter+0x39a/0x450<br /> io_write+0x22a/0x840<br /> io_issue_sqe+0x87/0x300<br /> io_wq_submit_work+0xeb/0x390<br /> io_worker_handle_work+0x24d/0x550<br /> io_wq_worker+0x27f/0x6c0<br /> ret_from_fork+0x2d/0x50<br /> ret_from_fork_asm+0x1b/0x30<br /> <br /> Freed by task 808589:<br /> kasan_save_stack+0x1e/0x40<br /> kasan_set_track+0x21/0x30<br /> kasan_save_free_info+0x27/0x40<br /> __kasan_slab_free+0x126/0x1b0<br /> kmem_cache_free+0x10c/0x750<br /> bfq_put_queue+0x2dd/0x770<br /> __bfq_insert_request.isra.0+0x155/0x7a0<br /> bfq_insert_request.isra.0+0x122/0x480<br /> bfq_insert_requests+0x156/0x180<br /> blk_mq_dispatch_plug_list+0x528/0x7e0<br /> blk_mq_flush_plug_list.part.0+0xe5/0x590<br /> __blk_flush_plug+0x3b/0x90<br /> blk_finish_plug+0x40/0x60<br /> do_writepages+0x19d/0x310<br /> filemap_fdatawrite_wbc+0x95/0xc0<br /> __filemap_fdatawrite_range+0x99/0xd0<br /> filemap_write_and_wait_range.part.0+0x4d/0xa0<br /> blkdev_read_iter+0xef/0x1e0<br /> io_read+0x1b6/0x8a0<br /> io_issue_sqe+0x87/0x300<br /> io_wq_submit_work+0xeb/0x390<br /> io_worker_handle_work+0x24d/0x550<br /> io_wq_worker+0x27f/0x6c0<br /> ret_from_fork+0x2d/0x50<br /> ret_from_fork_asm+0x1b/0x30<br /> <br /> Fix the problem by protecting bic_to_bfqq() with bfqd-&gt;lock.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK<br /> <br /> When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected,<br /> cpu_max_bits_warn() generates a runtime warning similar as below when<br /> showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)<br /> instead of NR_CPUS to iterate CPUs.<br /> <br /> [ 3.052463] ------------[ cut here ]------------<br /> [ 3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0<br /> [ 3.070072] Modules linked in: efivarfs autofs4<br /> [ 3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052<br /> [ 3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000<br /> [ 3.109127] 9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430<br /> [ 3.118774] 90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff<br /> [ 3.128412] 0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890<br /> [ 3.138056] 0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa<br /> [ 3.147711] ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000<br /> [ 3.157364] 900000000101c998 0000000000000004 9000000000ef7430 0000000000000000<br /> [ 3.167012] 0000000000000009 000000000000006c 0000000000000000 0000000000000000<br /> [ 3.176641] 9000000000d3de08 9000000001639390 90000000002086d8 00007ffff0080286<br /> [ 3.186260] 00000000000000b0 0000000000000004 0000000000000000 0000000000071c1c<br /> [ 3.195868] ...<br /> [ 3.199917] Call Trace:<br /> [ 3.203941] [] show_stack+0x38/0x14c<br /> [ 3.210666] [] dump_stack_lvl+0x60/0x88<br /> [ 3.217625] [] __warn+0xd0/0x100<br /> [ 3.223958] [] warn_slowpath_fmt+0x7c/0xcc<br /> [ 3.231150] [] show_cpuinfo+0x5e8/0x5f0<br /> [ 3.238080] [] seq_read_iter+0x354/0x4b4<br /> [ 3.245098] [] new_sync_read+0x17c/0x1c4<br /> [ 3.252114] [] vfs_read+0x138/0x1d0<br /> [ 3.258694] [] ksys_read+0x70/0x100<br /> [ 3.265265] [] do_syscall+0x7c/0x94<br /> [ 3.271820] [] handle_syscall+0xc4/0x160<br /> [ 3.281824] ---[ end trace 8b484262b4b8c24c ]---

A Denial of Service vulnerability in the DNS Security feature of Palo Alto Networks PAN-OS software allows an unauthenticated attacker to send a malicious packet through the data plane of the firewall that reboots the firewall. Repeated attempts to trigger this condition will cause the firewall to enter maintenance mode.

There is a stack overflow vulnerability in some Huawei smart phone. An attacker can craft specific packet to exploit this vulnerability. Due to insufficient verification, this could be exploited to tamper with the information to affect the availability. (Vulnerability ID: HWPSIRT-2019-11030)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9253.

There is a privilege escalation vulnerability in Huawei FusionCompute product. Due to insufficient verification on specific files that need to be deserialized, local attackers can exploit this vulnerability to elevate permissions. (Vulnerability ID: HWPSIRT-2020-05241)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9222.

There is an improper interface design vulnerability in Huawei product. A module interface of the impated product does not deal with some operations properly. Attackers can exploit this vulnerability to perform malicious operatation to compromise module service. (Vulnerability ID: HWPSIRT-2020-05010)<br /> <br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9236.

There is an insufficient integrity vulnerability in Huawei products. A module does not perform sufficient integrity check in a specific scenario. Attackers can exploit the vulnerability by physically install malware. This could compromise normal service of the affected device. (Vulnerability ID: HWPSIRT-2020-00145)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9210.

There is an out-of-bound read and write vulnerability in Huawei smartphone. A module dose not verify the input sufficiently. Attackers can exploit this vulnerability by modifying some configuration to cause out-of-bound read and write, causing denial of service. (Vulnerability ID: HWPSIRT-2020-05103)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9211.

There is an information vulnerability in Huawei smartphones. A function in a module can be called without verifying the caller&amp;#39;s access. Attackers with user access can exploit this vulnerability to obtain some information. This can lead to information leak. (Vulnerability ID: HWPSIRT-2019-12141)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9089.

There is a NULL pointer dereference vulnerability in some Huawei products. An attacker may send specially crafted POST messages to the affected products. Due to insufficient validation of some parameter in the message, successful exploit may cause some process abnormal. (Vulnerability ID: HWPSIRT-2017-10105)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9085.

There is a buffer error vulnerability in some Huawei product. An unauthenticated attacker may send special UPNP message to the affected products. Due to insufficient input validation of some value, successful exploit may cause some service abnormal. (Vulnerability ID: HWPSIRT-2017-08234)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9086.

There is an information disclosure vulnerability in several smartphones. The system has a logic judging error under certain scenario, the attacker should gain the permit to execute commands in ADB mode and then do a series of operation on the phone. Successful exploit could allow the attacker to gain certain information from certain apps locked by Applock. (Vulnerability ID: HWPSIRT-2019-07112)<br /> <br /> This vulnerability has been assigned a Common Vulnerabilities and Exposures (CVE) ID: CVE-2020-9082.