Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> gpio/rockchip: fix refcount leak in rockchip_gpiolib_register()<br /> <br /> The node returned by of_get_parent() with refcount incremented,<br /> of_node_put() needs be called when finish using it. So add it in the<br /> end of of_pinctrl_get().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: mvneta: Prevent out of bounds read in mvneta_config_rss()<br /> <br /> The pp-&gt;indir[0] value comes from the user. It is passed to:<br /> <br /> if (cpu_online(pp-&gt;rxq_def))<br /> <br /> inside the mvneta_percpu_elect() function. It needs bounds checkeding<br /> to ensure that it is not beyond the end of the cpu bitmap.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> NFC: nci: Bounds check struct nfc_target arrays<br /> <br /> While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported:<br /> <br /> memcpy: detected field-spanning write (size 129) of single field "target-&gt;sensf_res" at net/nfc/nci/ntf.c:260 (size 18)<br /> <br /> This appears to be a legitimate lack of bounds checking in<br /> nci_add_new_protocol(). Add the missing checks.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> octeontx2-pf: Fix potential memory leak in otx2_init_tc()<br /> <br /> In otx2_init_tc(), if rhashtable_init() failed, it does not free<br /> tc-&gt;tc_entries_bitmap which is allocated in otx2_tc_alloc_ent_bitmap().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove()<br /> <br /> The cmd_buff needs to be freed when error happened in<br /> dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ethernet: aeroflex: fix potential skb leak in greth_init_rings()<br /> <br /> The greth_init_rings() function won&amp;#39;t free the newly allocated skb when<br /> dma_mapping_error() returns error, so add dev_kfree_skb() to fix it.<br /> <br /> Compile tested only.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions()<br /> <br /> When dsa_devlink_region_create failed in sja1105_setup_devlink_regions(),<br /> priv-&gt;regions is not released.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: hisilicon: Fix potential use-after-free in hix5hd2_rx()<br /> <br /> The skb is delivered to napi_gro_receive() which may free it, after<br /> calling this, dereferencing skb may trigger use-after-free.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: mdio: fix unbalanced fwnode reference count in mdio_device_release()<br /> <br /> There is warning report about of_node refcount leak<br /> while probing mdio device:<br /> <br /> OF: ERROR: memory leak, expected refcount 1 instead of 2,<br /> of_node_get()/of_node_put() unbalanced - destroy cset entry:<br /> attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4<br /> <br /> In of_mdiobus_register_device(), we increase fwnode refcount<br /> by fwnode_handle_get() before associating the of_node with<br /> mdio device, but it has never been decreased in normal path.<br /> Since that, in mdio_device_release(), it needs to call<br /> fwnode_handle_put() in addition instead of calling kfree()<br /> directly.<br /> <br /> After above, just calling mdio_device_free() in the error handle<br /> path of of_mdiobus_register_device() is enough to keep the<br /> refcount balanced.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> udf: Fix preallocation discarding at indirect extent boundary<br /> <br /> When preallocation extent is the first one in the extent block, the<br /> code would corrupt extent tree header instead. Fix the problem and use<br /> udf_delete_aext() for deleting extent to avoid some code duplication.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: L2CAP: Fix u8 overflow<br /> <br /> By keep sending L2CAP_CONF_REQ packets, chan-&gt;num_conf_rsp increases<br /> multiple times and eventually it will wrap around the maximum number<br /> (i.e., 255).<br /> This patch prevents this by adding a boundary check with<br /> L2CAP_MAX_CONF_RSP<br /> <br /> Btmon log:<br /> Bluetooth monitor ver 5.64<br /> = Note: Linux version 6.1.0-rc2 (x86_64) 0.264594<br /> = Note: Bluetooth subsystem version 2.22 0.264636<br /> @ MGMT Open: btmon (privileged) version 1.22 {0x0001} 0.272191<br /> = New Index: 00:00:00:00:00:00 (Primary,Virtual,hci0) [hci0] 13.877604<br /> @ RAW Open: 9496 (privileged) version 2.22 {0x0002} 13.890741<br /> = Open Index: 00:00:00:00:00:00 [hci0] 13.900426<br /> (...)<br /> &gt; ACL Data RX: Handle 200 flags 0x00 dlen 1033 #32 [hci0] 14.273106<br /> invalid packet size (12 != 1033)<br /> 08 00 01 00 02 01 04 00 01 10 ff ff ............<br /> &gt; ACL Data RX: Handle 200 flags 0x00 dlen 1547 #33 [hci0] 14.273561<br /> invalid packet size (14 != 1547)<br /> 0a 00 01 00 04 01 06 00 40 00 00 00 00 00 ........@.....<br /> &gt; ACL Data RX: Handle 200 flags 0x00 dlen 2061 #34 [hci0] 14.274390<br /> invalid packet size (16 != 2061)<br /> 0c 00 01 00 04 01 08 00 40 00 00 00 00 00 00 04 ........@.......<br /> &gt; ACL Data RX: Handle 200 flags 0x00 dlen 2061 #35 [hci0] 14.274932<br /> invalid packet size (16 != 2061)<br /> 0c 00 01 00 04 01 08 00 40 00 00 00 07 00 03 00 ........@.......<br /> = bluetoothd: Bluetooth daemon 5.43 14.401828<br /> &gt; ACL Data RX: Handle 200 flags 0x00 dlen 1033 #36 [hci0] 14.275753<br /> invalid packet size (12 != 1033)<br /> 08 00 01 00 04 01 04 00 40 00 00 00 ........@...

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: uvc: Prevent buffer overflow in setup handler<br /> <br /> Setup function uvc_function_setup permits control transfer<br /> requests with up to 64 bytes of payload (UVC_MAX_REQUEST_SIZE),<br /> data stage handler for OUT transfer uses memcpy to copy req-&gt;actual<br /> bytes to uvc_event-&gt;data.data array of size 60. This may result<br /> in an overflow of 4 bytes.