Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: ASSERT when failing to find index by plane/stream id<br /> <br /> [WHY]<br /> find_disp_cfg_idx_by_plane_id and find_disp_cfg_idx_by_stream_id returns<br /> an array index and they return -1 when not found; however, -1 is not a<br /> valid index number.<br /> <br /> [HOW]<br /> When this happens, call ASSERT(), and return a positive number (which is<br /> fewer than callers&amp;#39; array size) instead.<br /> <br /> This fixes 4 OVERRUN and 2 NEGATIVE_RETURNS issues reported by Coverity.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Do not return negative stream id for array<br /> <br /> [WHY]<br /> resource_stream_to_stream_idx returns an array index and it return -1<br /> when not found; however, -1 is not a valid array index number.<br /> <br /> [HOW]<br /> When this happens, call ASSERT(), and return a zero instead.<br /> <br /> This fixes an OVERRUN and an NEGATIVE_RETURNS issues reported by Coverity.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: fix double free err_addr pointer warnings<br /> <br /> In amdgpu_umc_bad_page_polling_timeout, the amdgpu_umc_handle_bad_pages<br /> will be run many times so that double free err_addr in some special case.<br /> So set the err_addr to NULL to avoid the warnings.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: rtw89: fw: scan offload prohibit all 6 GHz channel if no 6 GHz sband<br /> <br /> We have some policy via BIOS to block uses of 6 GHz. In this case, 6 GHz<br /> sband will be NULL even if it is WiFi 7 chip. So, add NULL handling here<br /> to avoid crash.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> leds: an30259a: Use devm_mutex_init() for mutex initialization<br /> <br /> In this driver LEDs are registered using devm_led_classdev_register()<br /> so they are automatically unregistered after module&amp;#39;s remove() is done.<br /> led_classdev_unregister() calls module&amp;#39;s led_set_brightness() to turn off<br /> the LEDs and that callback uses mutex which was destroyed already<br /> in module&amp;#39;s remove() so use devm API instead.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Add NULL pointer check for kzalloc<br /> <br /> [Why &amp; How]<br /> Check return pointer of kzalloc before using it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> leds: mlxreg: Use devm_mutex_init() for mutex initialization<br /> <br /> In this driver LEDs are registered using devm_led_classdev_register()<br /> so they are automatically unregistered after module&amp;#39;s remove() is done.<br /> led_classdev_unregister() calls module&amp;#39;s led_set_brightness() to turn off<br /> the LEDs and that callback uses mutex which was destroyed already<br /> in module&amp;#39;s remove() so use devm API instead.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Skip finding free audio for unknown engine_id<br /> <br /> [WHY]<br /> ENGINE_ID_UNKNOWN = -1 and can not be used as an array index. Plus, it<br /> also means it is uninitialized and does not need free audio.<br /> <br /> [HOW]<br /> Skip and return NULL.<br /> <br /> This fixes 2 OVERRUN issues reported by Coverity.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Check pipe offset before setting vblank<br /> <br /> pipe_ctx has a size of MAX_PIPES so checking its index before accessing<br /> the array.<br /> <br /> This fixes an OVERRUN issue reported by Coverity.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: Check index msg_id before read or write<br /> <br /> [WHAT]<br /> msg_id is used as an array index and it cannot be a negative value, and<br /> therefore cannot be equal to MOD_HDCP_MESSAGE_ID_INVALID (-1).<br /> <br /> [HOW]<br /> Check whether msg_id is valid before reading and setting.<br /> <br /> This fixes 4 OVERRUN issues reported by Coverity.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qedf: Make qedf_execute_tmf() non-preemptible<br /> <br /> Stop calling smp_processor_id() from preemptible code in<br /> qedf_execute_tmf90. This results in BUG_ON() when running an RT kernel.<br /> <br /> [ 659.343280] BUG: using smp_processor_id() in preemptible [00000000] code: sg_reset/3646<br /> [ 659.343282] caller is qedf_execute_tmf+0x8b/0x360 [qedf]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt.<br /> <br /> nmi_enter()/nmi_exit() touches per cpu variables which can lead to kernel<br /> crash when invoked during real mode interrupt handling (e.g. early HMI/MCE<br /> interrupt handler) if percpu allocation comes from vmalloc area.<br /> <br /> Early HMI/MCE handlers are called through DEFINE_INTERRUPT_HANDLER_NMI()<br /> wrapper which invokes nmi_enter/nmi_exit calls. We don&amp;#39;t see any issue when<br /> percpu allocation is from the embedded first chunk. However with<br /> CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK enabled there are chances where percpu<br /> allocation can come from the vmalloc area.<br /> <br /> With kernel command line "percpu_alloc=page" we can force percpu allocation<br /> to come from vmalloc area and can see kernel crash in machine_check_early:<br /> <br /> [ 1.215714] NIP [c000000000e49eb4] rcu_nmi_enter+0x24/0x110<br /> [ 1.215717] LR [c0000000000461a0] machine_check_early+0xf0/0x2c0<br /> [ 1.215719] --- interrupt: 200<br /> [ 1.215720] [c000000fffd73180] [0000000000000000] 0x0 (unreliable)<br /> [ 1.215722] [c000000fffd731b0] [0000000000000000] 0x0<br /> [ 1.215724] [c000000fffd73210] [c000000000008364] machine_check_early_common+0x134/0x1f8<br /> <br /> Fix this by avoiding use of nmi_enter()/nmi_exit() in real mode if percpu<br /> first chunk is not embedded.