CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2021-47002 – SUNRPC: Fix null pointer dereference in svc_rqst_free()
https://notcve.org/view.php?id=CVE-2021-47002
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix null pointer dereference in svc_rqst_free() When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). Fix it by adding a null check. Addresses-Coverity: ("Dereference after null check") En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: SUNRPC: corrige la desreferencia del puntero nulo en svc_rqst_free() Cuando alloc_pages_node() devuelve nulo en svc_rqst_alloc(), el puntero nulo rq_scratch_page será desreferenciado al llamar a put_page() en svc_rqst_free(). Solucionarlo agregando una marca nula. Direcciones-Cobertura: ("Desreferencia después de verificación nula") • https://git.kernel.org/stable/c/79e4e0d489c8e72b9efa388e504a036eec1550c6 https://git.kernel.org/stable/c/5191955d6fc65e6d4efe8f4f10a6028298f57281 https://git.kernel.org/stable/c/3de81c1e84bf84803308da3272a829a7655c5336 https://git.kernel.org/stable/c/1e10f58f1c9a6b667b045513c7a4e6111c24fe7c https://git.kernel.org/stable/c/c664aaec9aee544538a78ba4893a44bc73a6d742 https://git.kernel.org/stable/c/b9f83ffaa0c096b4c832a43964fe6bff3acffe10 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2021-47001 – xprtrdma: Fix cwnd update ordering
https://notcve.org/view.php?id=CVE-2021-47001
In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix cwnd update ordering After a reconnect, the reply handler is opening the cwnd (and thus enabling more RPC Calls to be sent) /before/ rpcrdma_post_recvs() can post enough Receive WRs to receive their replies. This causes an RNR and the new connection is lost immediately. The race is most clearly exposed when KASAN and disconnect injection are enabled. This slows down rpcrdma_rep_create() enough to allow the send side to post a bunch of RPC Calls before the Receive completion handler can invoke ib_post_recv(). En el kernel de Linux, se resolvió la siguiente vulnerabilidad: xprtrdma: corrige el orden de actualización de cwnd Después de una reconexión, el controlador de respuesta abre cwnd (y así permite que se envíen más llamadas RPC) /antes/ rpcrdma_post_recvs() puede publicar suficiente recepción WR para recibir sus respuestas. Esto provoca un RNR y la nueva conexión se pierde inmediatamente. • https://git.kernel.org/stable/c/2ae50ad68cd79224198b525f7bd645c9da98b6ff https://git.kernel.org/stable/c/3791c5982ba1eebf2900ee7ca7b9a89619c26d54 https://git.kernel.org/stable/c/eddae8be7944096419c2ae29477a45f767d0fcd4 https://git.kernel.org/stable/c/8834ecb5df22b7ff3c9b0deba7726579bb613f95 https://git.kernel.org/stable/c/19b5fa9489b5706bc878c3a522a7f771079e2fa0 https://git.kernel.org/stable/c/35d8b10a25884050bb3b0149b62c3818ec59f77c •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2021-47000 – ceph: fix inode leak on getattr error in __fh_to_dentry
https://notcve.org/view.php?id=CVE-2021-47000
In the Linux kernel, the following vulnerability has been resolved: ceph: fix inode leak on getattr error in __fh_to_dentry En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ceph: corrige la fuga de inodo en el error getattr en __fh_to_dentry • https://git.kernel.org/stable/c/807460787179dee5f74906965eeb5f3ca2353992 https://git.kernel.org/stable/c/878dabb64117406abd40977b87544d05bb3031fc https://git.kernel.org/stable/c/10b7ddff50b3334414c0be4b6009671b18ba4845 https://git.kernel.org/stable/c/2ad8af2b70e986284050213230428b823b950a38 https://git.kernel.org/stable/c/bf45c9fe99aa8003d2703f1bd353f956dea47e40 https://git.kernel.org/stable/c/22fa4c8288f1ec40f6d62d7a32c57ac176f9f0bc https://git.kernel.org/stable/c/0a219432127d396120fc88cabd82785e0ff72a2f https://git.kernel.org/stable/c/1775c7ddacfcea29051c67409087578f8 •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2021-46999 – sctp: do asoc update earlier in sctp_sf_do_dupcook_a
https://notcve.org/view.php?id=CVE-2021-46999
In the Linux kernel, the following vulnerability has been resolved: sctp: do asoc update earlier in sctp_sf_do_dupcook_a There's a panic that occurs in a few of envs, the call trace is as below: [] general protection fault, ... 0x29acd70f1000a: 0000 [#1] SMP PTI [] RIP: 0010:sctp_ulpevent_notify_peer_addr_change+0x4b/0x1fa [sctp] [] sctp_assoc_control_transport+0x1b9/0x210 [sctp] [] sctp_do_8_2_transport_strike.isra.16+0x15c/0x220 [sctp] [] sctp_cmd_interpreter.isra.21+0x1231/0x1a10 [sctp] [] sctp_do_sm+0xc3/0x2a0 [sctp] [] sctp_generate_timeout_event+0x81/0xf0 [sctp] This is caused by a transport use-after-free issue. When processing a duplicate COOKIE-ECHO chunk in sctp_sf_do_dupcook_a(), both COOKIE-ACK and SHUTDOWN chunks are allocated with the transort from the new asoc. However, later in the sideeffect machine, the old asoc is used to send them out and old asoc's shutdown_last_sent_to is set to the transport that SHUTDOWN chunk attached to in sctp_cmd_setup_t2(), which actually belongs to the new asoc. After the new_asoc is freed and the old asoc T2 timeout, the old asoc's shutdown_last_sent_to that is already freed would be accessed in sctp_sf_t2_timer_expire(). Thanks Alexander and Jere for helping dig into this issue. To fix it, this patch is to do the asoc update first, then allocate the COOKIE-ACK and SHUTDOWN chunks with the 'updated' old asoc. This would make more sense, as a chunk from an asoc shouldn't be sent out with another asoc. We had fixed quite a few issues caused by this. • https://git.kernel.org/stable/c/db8bf823e70f239372c62f13e4eb6f08a1665e8c https://git.kernel.org/stable/c/a204d577be70e0a0a6023cf1b9859c9ebffaeecd https://git.kernel.org/stable/c/145cb2f7177d94bc54563ed26027e952ee0ae03c https://git.kernel.org/stable/c/a5ce8531ea508d270822b2bc6140c6198c8a2a7b https://git.kernel.org/stable/c/d624f2991b977821375fbd56c91b0c91d456a697 https://git.kernel.org/stable/c/b1b31948c0af44628e43353828453461bb74098f https://git.kernel.org/stable/c/f01988ecf3654f805282dce2d3bb9afe68d2691e https://git.kernel.org/stable/c/61b877bad9bb0d82b7d8841be50872557 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2021-46998 – ethernet:enic: Fix a use after free bug in enic_hard_start_xmit
https://notcve.org/view.php?id=CVE-2021-46998
In the Linux kernel, the following vulnerability has been resolved: ethernet:enic: Fix a use after free bug in enic_hard_start_xmit In enic_hard_start_xmit, it calls enic_queue_wq_skb(). Inside enic_queue_wq_skb, if some error happens, the skb will be freed by dev_kfree_skb(skb). But the freed skb is still used in skb_tx_timestamp(skb). My patch makes enic_queue_wq_skb() return error and goto spin_unlock() incase of error. The solution is provided by Govind. See https://lkml.org/lkml/2021/4/30/961. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ethernet:enic: corrige un error de use after free en enic_hard_start_xmit. • https://git.kernel.org/stable/c/fb7516d42478ebc8e2f00efb76ef96f7b68fd8d3 https://git.kernel.org/stable/c/25a87b1f566b5eb2af2857a928f0e2310d900976 https://git.kernel.org/stable/c/f7f6f07774091a6ddd98500b85386c3c6afb30d3 https://git.kernel.org/stable/c/7afdd6aba95c8a526038e7abe283eeac3e4320f1 https://git.kernel.org/stable/c/6892396ebf04ea2c021d80e10f4075e014cd7cc3 https://git.kernel.org/stable/c/d90529392aaf498dafa95d212295d64b2cea4e24 https://git.kernel.org/stable/c/643001b47adc844ae33510c4bb93c236667008a3 •