Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nvme-loop: fix memory leak in nvme_loop_create_ctrl()<br /> <br /> When creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()<br /> fails, the loop ctrl should be freed before jumping to the "out" label.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nvmet: fix memory leak in nvmet_alloc_ctrl()<br /> <br /> When creating ctrl in nvmet_alloc_ctrl(), if the cntlid_min is larger<br /> than cntlid_max of the subsystem, and jumps to the<br /> "out_free_changed_ns_list" label, but the ctrl-&gt;sqs lack of be freed.<br /> Fix this by jumping to the "out_free_sqs" label.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/rxe: Return CQE error if invalid lkey was supplied<br /> <br /> RXE is missing update of WQE status in LOCAL_WRITE failures. This caused<br /> the following kernel panic if someone sent an atomic operation with an<br /> explicitly wrong lkey.<br /> <br /> [leonro@vm ~]$ mkt test<br /> test_atomic_invalid_lkey (tests.test_atomic.AtomicTest) ...<br /> WARNING: CPU: 5 PID: 263 at drivers/infiniband/sw/rxe/rxe_comp.c:740 rxe_completer+0x1a6d/0x2e30 [rdma_rxe]<br /> Modules linked in: crc32_generic rdma_rxe ip6_udp_tunnel udp_tunnel rdma_ucm rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core mlx5_core ptp pps_core<br /> CPU: 5 PID: 263 Comm: python3 Not tainted 5.13.0-rc1+ #2936<br /> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014<br /> RIP: 0010:rxe_completer+0x1a6d/0x2e30 [rdma_rxe]<br /> Code: 03 0f 8e 65 0e 00 00 3b 93 10 06 00 00 0f 84 82 0a 00 00 4c 89 ff 4c 89 44 24 38 e8 2d 74 a9 e1 4c 8b 44 24 38 e9 1c f5 ff ff 0b e9 0c e8 ff ff b8 05 00 00 00 41 bf 05 00 00 00 e9 ab e7 ff<br /> RSP: 0018:ffff8880158af090 EFLAGS: 00010246<br /> RAX: 0000000000000000 RBX: ffff888016a78000 RCX: ffffffffa0cf1652<br /> RDX: 1ffff9200004b442 RSI: 0000000000000004 RDI: ffffc9000025a210<br /> RBP: dffffc0000000000 R08: 00000000ffffffea R09: ffff88801617740b<br /> R10: ffffed1002c2ee81 R11: 0000000000000007 R12: ffff88800f3b63e8<br /> R13: ffff888016a78008 R14: ffffc9000025a180 R15: 000000000000000c<br /> FS: 00007f88b622a740(0000) GS:ffff88806d540000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00007f88b5a1fa10 CR3: 000000000d848004 CR4: 0000000000370ea0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> rxe_do_task+0x130/0x230 [rdma_rxe]<br /> rxe_rcv+0xb11/0x1df0 [rdma_rxe]<br /> rxe_loopback+0x157/0x1e0 [rdma_rxe]<br /> rxe_responder+0x5532/0x7620 [rdma_rxe]<br /> rxe_do_task+0x130/0x230 [rdma_rxe]<br /> rxe_rcv+0x9c8/0x1df0 [rdma_rxe]<br /> rxe_loopback+0x157/0x1e0 [rdma_rxe]<br /> rxe_requester+0x1efd/0x58c0 [rdma_rxe]<br /> rxe_do_task+0x130/0x230 [rdma_rxe]<br /> rxe_post_send+0x998/0x1860 [rdma_rxe]<br /> ib_uverbs_post_send+0xd5f/0x1220 [ib_uverbs]<br /> ib_uverbs_write+0x847/0xc80 [ib_uverbs]<br /> vfs_write+0x1c5/0x840<br /> ksys_write+0x176/0x1d0<br /> do_syscall_64+0x3f/0x80<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qedf: Add pointer checks in qedf_update_link_speed()<br /> <br /> The following trace was observed:<br /> <br /> [ 14.042059] Call Trace:<br /> [ 14.042061] <br /> [ 14.042068] qedf_link_update+0x144/0x1f0 [qedf]<br /> [ 14.042117] qed_link_update+0x5c/0x80 [qed]<br /> [ 14.042135] qed_mcp_handle_link_change+0x2d2/0x410 [qed]<br /> [ 14.042155] ? qed_set_ptt+0x70/0x80 [qed]<br /> [ 14.042170] ? qed_set_ptt+0x70/0x80 [qed]<br /> [ 14.042186] ? qed_rd+0x13/0x40 [qed]<br /> [ 14.042205] qed_mcp_handle_events+0x437/0x690 [qed]<br /> [ 14.042221] ? qed_set_ptt+0x70/0x80 [qed]<br /> [ 14.042239] qed_int_sp_dpc+0x3a6/0x3e0 [qed]<br /> [ 14.042245] tasklet_action_common.isra.14+0x5a/0x100<br /> [ 14.042250] __do_softirq+0xe4/0x2f8<br /> [ 14.042253] irq_exit+0xf7/0x100<br /> [ 14.042255] do_IRQ+0x7f/0xd0<br /> [ 14.042257] common_interrupt+0xf/0xf<br /> [ 14.042259] <br /> <br /> API qedf_link_update() is getting called from QED but by that time<br /> shost_data is not initialised. This results in a NULL pointer dereference<br /> when we try to dereference shost_data while updating supported_speeds.<br /> <br /> Add a NULL pointer check before dereferencing shost_data.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/rxe: Clear all QP fields if creation failed<br /> <br /> rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly<br /> created ones, but in case rxe_qp_from_init() failed it was filled with<br /> garbage and caused tot the following error.<br /> <br /> refcount_t: underflow; use-after-free.<br /> WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28<br /> Modules linked in:<br /> CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011<br /> RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28<br /> Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55<br /> RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286<br /> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000<br /> RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67<br /> RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000<br /> R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800<br /> R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000<br /> FS: 00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> __refcount_sub_and_test include/linux/refcount.h:283 [inline]<br /> __refcount_dec_and_test include/linux/refcount.h:315 [inline]<br /> refcount_dec_and_test include/linux/refcount.h:333 [inline]<br /> kref_put include/linux/kref.h:64 [inline]<br /> rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805<br /> execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327<br /> rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391<br /> kref_put include/linux/kref.h:65 [inline]<br /> rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425<br /> _ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline]<br /> ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231<br /> ib_create_qp include/rdma/ib_verbs.h:3644 [inline]<br /> create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920<br /> ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline]<br /> ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092<br /> add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717<br /> enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331<br /> ib_register_device drivers/infiniband/core/device.c:1413 [inline]<br /> ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365<br /> rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147<br /> rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247<br /> rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503<br /> rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline]<br /> rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250<br /> nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555<br /> rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195<br /> rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]<br /> rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]<br /> netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338<br /> netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927<br /> sock_sendmsg_nosec net/socket.c:654 [inline]<br /> sock_sendmsg+0xcf/0x120 net/socket.c:674<br /> ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350<br /> ___sys_sendmsg+0xf3/0x170 net/socket.c:2404<br /> __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433<br /> do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47<br /> entry_SYSCALL_64_after_hwframe+0<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> platform/x86: ideapad-laptop: fix a NULL pointer dereference<br /> <br /> The third parameter of dytc_cql_command should not be NULL since it will<br /> be dereferenced immediately.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/core: Prevent divide-by-zero error triggered by the user<br /> <br /> The user_entry_size is supplied by the user and later used as a<br /> denominator to calculate number of entries. The zero supplied by the user<br /> will trigger the following divide-by-zero error:<br /> <br /> divide error: 0000 [#1] SMP KASAN PTI<br /> CPU: 4 PID: 497 Comm: c_repro Not tainted 5.13.0-rc1+ #281<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014<br /> RIP: 0010:ib_uverbs_handler_UVERBS_METHOD_QUERY_GID_TABLE+0x1b1/0x510<br /> Code: 87 59 03 00 00 e8 9f ab 1e ff 48 8d bd a8 00 00 00 e8 d3 70 41 ff 44 0f b7 b5 a8 00 00 00 e8 86 ab 1e ff 31 d2 4c 89 f0 31 ff f7 f5 48 89 d6 48 89 54 24 10 48 89 04 24 e8 1b ad 1e ff 48 8b<br /> RSP: 0018:ffff88810416f828 EFLAGS: 00010246<br /> RAX: 0000000000000008 RBX: 1ffff1102082df09 RCX: ffffffff82183f3d<br /> RDX: 0000000000000000 RSI: ffff888105f2da00 RDI: 0000000000000000<br /> RBP: ffff88810416fa98 R08: 0000000000000001 R09: ffffed102082df5f<br /> R10: ffff88810416faf7 R11: ffffed102082df5e R12: 0000000000000000<br /> R13: 0000000000000000 R14: 0000000000000008 R15: ffff88810416faf0<br /> FS: 00007f5715efa740(0000) GS:ffff88811a700000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 0000000020000840 CR3: 000000010c2e0001 CR4: 0000000000370ea0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> ? ib_uverbs_handler_UVERBS_METHOD_INFO_HANDLES+0x4b0/0x4b0<br /> ib_uverbs_cmd_verbs+0x1546/0x1940<br /> ib_uverbs_ioctl+0x186/0x240<br /> __x64_sys_ioctl+0x38a/0x1220<br /> do_syscall_64+0x3f/0x80<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> habanalabs/gaudi: Fix a potential use after free in gaudi_memset_device_memory<br /> <br /> Our code analyzer reported a uaf.<br /> <br /> In gaudi_memset_device_memory, cb is get via hl_cb_kernel_create()<br /> with 2 refcount.<br /> If hl_cs_allocate_job() failed, the execution runs into release_cb<br /> branch. One ref of cb is dropped by hl_cb_put(cb) and could be freed<br /> if other thread also drops one ref. Then cb is used by cb-&gt;id later,<br /> which is a potential uaf.<br /> <br /> My patch add a variable &amp;#39;id&amp;#39; to accept the value of cb-&gt;id before the<br /> hl_cb_put(cb) is called, to avoid the potential uaf.

Book Store Management System v1.0 was discovered to contain a cross-site scripting (XSS) vulnerability in /bsms_ci/index.php/category. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the category parameter.

Book Store Management System v1.0 was discovered to contain a cross-site scripting (XSS) vulnerability in /bsms_ci/index.php/history. This vulnerability allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the history parameter.

Incorrect access control in Book Store Management System v1 allows attackers to access unauthorized pages and execute administrative functions without authenticating.

A local file inclusion (LFI) in Customer Support System v1 allows attackers to include internal PHP files and gain unauthorized acces via manipulation of the page= parameter at /customer_support/index.php.