Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: dsa: microchip: ksz_common: Fix refcount leak bug<br /> <br /> In ksz_switch_register(), we should call of_node_put() for the<br /> reference returned by of_get_child_by_name() which has increased<br /> the refcount.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: stmmac: fix dma queue left shift overflow issue<br /> <br /> When queue number is &gt; 4, left shift overflows due to 32 bits<br /> integer variable. Mask calculation is wrong for MTL_RXQ_DMA_MAP1.<br /> <br /> If CONFIG_UBSAN is enabled, kernel dumps below warning:<br /> [ 10.363842] ==================================================================<br /> [ 10.363882] UBSAN: shift-out-of-bounds in /build/linux-intel-iotg-5.15-8e6Tf4/<br /> linux-intel-iotg-5.15-5.15.0/drivers/net/ethernet/stmicro/stmmac/dwmac4_core.c:224:12<br /> [ 10.363929] shift exponent 40 is too large for 32-bit type &amp;#39;unsigned int&amp;#39;<br /> [ 10.363953] CPU: 1 PID: 599 Comm: NetworkManager Not tainted 5.15.0-1003-intel-iotg<br /> [ 10.363956] Hardware name: ADLINK Technology Inc. LEC-EL/LEC-EL, BIOS 0.15.11 12/22/2021<br /> [ 10.363958] Call Trace:<br /> [ 10.363960] <br /> [ 10.363963] dump_stack_lvl+0x4a/0x5f<br /> [ 10.363971] dump_stack+0x10/0x12<br /> [ 10.363974] ubsan_epilogue+0x9/0x45<br /> [ 10.363976] __ubsan_handle_shift_out_of_bounds.cold+0x61/0x10e<br /> [ 10.363979] ? wake_up_klogd+0x4a/0x50<br /> [ 10.363983] ? vprintk_emit+0x8f/0x240<br /> [ 10.363986] dwmac4_map_mtl_dma.cold+0x42/0x91 [stmmac]<br /> [ 10.364001] stmmac_mtl_configuration+0x1ce/0x7a0 [stmmac]<br /> [ 10.364009] ? dwmac410_dma_init_channel+0x70/0x70 [stmmac]<br /> [ 10.364020] stmmac_hw_setup.cold+0xf/0xb14 [stmmac]<br /> [ 10.364030] ? page_pool_alloc_pages+0x4d/0x70<br /> [ 10.364034] ? stmmac_clear_tx_descriptors+0x6e/0xe0 [stmmac]<br /> [ 10.364042] stmmac_open+0x39e/0x920 [stmmac]<br /> [ 10.364050] __dev_open+0xf0/0x1a0<br /> [ 10.364054] __dev_change_flags+0x188/0x1f0<br /> [ 10.364057] dev_change_flags+0x26/0x60<br /> [ 10.364059] do_setlink+0x908/0xc40<br /> [ 10.364062] ? do_setlink+0xb10/0xc40<br /> [ 10.364064] ? __nla_validate_parse+0x4c/0x1a0<br /> [ 10.364068] __rtnl_newlink+0x597/0xa10<br /> [ 10.364072] ? __nla_reserve+0x41/0x50<br /> [ 10.364074] ? __kmalloc_node_track_caller+0x1d0/0x4d0<br /> [ 10.364079] ? pskb_expand_head+0x75/0x310<br /> [ 10.364082] ? nla_reserve_64bit+0x21/0x40<br /> [ 10.364086] ? skb_free_head+0x65/0x80<br /> [ 10.364089] ? security_sock_rcv_skb+0x2c/0x50<br /> [ 10.364094] ? __cond_resched+0x19/0x30<br /> [ 10.364097] ? kmem_cache_alloc_trace+0x15a/0x420<br /> [ 10.364100] rtnl_newlink+0x49/0x70<br /> <br /> This change fixes MTL_RXQ_DMA_MAP1 mask issue and channel/queue<br /> mapping warning.<br /> <br /> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=216195

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tcp: Fix a data-race around sysctl_tcp_probe_interval.<br /> <br /> While reading sysctl_tcp_probe_interval, it can be changed concurrently.<br /> Thus, we need to add READ_ONCE() to its reader.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tcp: Fix a data-race around sysctl_tcp_mtu_probe_floor.<br /> <br /> While reading sysctl_tcp_mtu_probe_floor, it can be changed concurrently.<br /> Thus, we need to add READ_ONCE() to its reader.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tcp: Fix data-races around sysctl_tcp_recovery.<br /> <br /> While reading sysctl_tcp_recovery, it can be changed concurrently.<br /> Thus, we need to add READ_ONCE() to its readers.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.<br /> <br /> While reading sysctl_tcp_thin_linear_timeouts, it can be changed<br /> concurrently. Thus, we need to add READ_ONCE() to its reader.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv4: Fix data-races around sysctl_fib_multipath_hash_fields.<br /> <br /> While reading sysctl_fib_multipath_hash_fields, it can be changed<br /> concurrently. Thus, we need to add READ_ONCE() to its readers.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> udp: Fix a data-race around sysctl_udp_l3mdev_accept.<br /> <br /> While reading sysctl_udp_l3mdev_accept, it can be changed concurrently.<br /> Thus, we need to add READ_ONCE() to its reader.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ip: Fix data-races around sysctl_ip_prot_sock.<br /> <br /> sysctl_ip_prot_sock is accessed concurrently, and there is always a chance<br /> of data-race. So, all readers and writers need some basic protection to<br /> avoid load/store-tearing.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv4: Fix data-races around sysctl_fib_multipath_hash_policy.<br /> <br /> While reading sysctl_fib_multipath_hash_policy, it can be changed<br /> concurrently. Thus, we need to add READ_ONCE() to its readers.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.<br /> <br /> While reading sysctl_fib_multipath_use_neigh, it can be changed<br /> concurrently. Thus, we need to add READ_ONCE() to its reader.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> be2net: Fix buffer overflow in be_get_module_eeprom<br /> <br /> be_cmd_read_port_transceiver_data assumes that it is given a buffer that<br /> is at least PAGE_DATA_LEN long, or twice that if the module supports SFF<br /> 8472. However, this is not always the case.<br /> <br /> Fix this by passing the desired offset and length to<br /> be_cmd_read_port_transceiver_data so that we only copy the bytes once.