CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2023-53650 – fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe()
https://notcve.org/view.php?id=CVE-2023-53650
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe() If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak. • https://git.kernel.org/stable/c/66d2f99d0bb5a2972fb5c1d88b61169510e540d6 •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2023-53648 – ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer
https://notcve.org/view.php?id=CVE-2023-53648
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer smatch error: sound/pci/ac97/ac97_codec.c:2354 snd_ac97_mixer() error: we previously assumed 'rac97' could be null (see line 2072) remove redundant assignment, return error if rac97 is NULL. In the Linux kernel, the following vulnerability has been resolved: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer smatch error: sound/pci/ac97/ac97_codec.c:2354 snd_ac97_mixer() e... • https://git.kernel.org/stable/c/da3cec35dd3c31d8706db4bf379372ce70d92118 • CWE-476: NULL Pointer Dereference •
CVSS: 6.6EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53644 – media: radio-shark: Add endpoint checks
https://notcve.org/view.php?id=CVE-2023-53644
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: media: radio-shark: Add endpoint checks The syzbot fuzzer was able to provoke a WARNING from the radio-shark2 driver: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 1 != type 3 WARNING: CPU: 0 PID: 3271 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed2/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU: 0 PID: 3271 Comm: kworker/0:3 Not tainted 6.1.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Goo... • https://git.kernel.org/stable/c/3ed6a312ac1e7278f92b1b3d95377b335ae21e89 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53641 – wifi: ath9k: hif_usb: fix memory leak of remain_skbs
https://notcve.org/view.php?id=CVE-2023-53641
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: fix memory leak of remain_skbs hif_dev->remain_skb is allocated and used exclusively in ath9k_hif_usb_rx_stream(). It is implied that an allocated remain_skb is processed and subsequently freed (in error paths) only during the next call of ath9k_hif_usb_rx_stream(). So, if the urbs are deallocated between those two calls due to the device deinitialization or suspend, it is possible that ath9k_hif_usb_rx_stream() is not... • https://git.kernel.org/stable/c/fb9987d0f748c983bb795a86f47522313f701a08 • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53627 – scsi: hisi_sas: Grab sas_dev lock when traversing the members of sas_dev.list
https://notcve.org/view.php?id=CVE-2023-53627
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: hisi_sas: Grab sas_dev lock when traversing the members of sas_dev.list When freeing slots in function slot_complete_v3_hw(), it is possible that sas_dev.list is being traversed elsewhere, and it may trigger a NULL pointer exception, such as follows: ==>cq thread ==>scsi_eh_6 ==>scsi_error_handler() ==>sas_eh_handle_sas_errors() ==>sas_scsi_find_task() ==>lldd_abort_task() ==>slot_complete_v3_hw() ==>hisi_sas_abort_task() ==>hisi_sas_... • https://git.kernel.org/stable/c/6e2a40b3a332ea84079983be21c944de8ddbc4f3 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53622 – gfs2: Fix possible data races in gfs2_show_options()
https://notcve.org/view.php?id=CVE-2023-53622
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix possible data races in gfs2_show_options() Some fields such as gt_logd_secs of the struct gfs2_tune are accessed without holding the lock gt_spin in gfs2_show_options(): val = sdp->sd_tune.gt_logd_secs; if (val != 30) seq_printf(s, ",commit=%d", val); And thus can cause data races when gfs2_show_options() and other functions such as gfs2_reconfigure() are concurrently executed: spin_lock(>->gt_spin); gt->gt_logd_secs = newargs->... • https://git.kernel.org/stable/c/7e5bbeb7eb813bb2568e1d5d02587df943272e57 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53620 – md: fix soft lockup in status_resync
https://notcve.org/view.php?id=CVE-2023-53620
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: md: fix soft lockup in status_resync status_resync() will calculate 'curr_resync - recovery_active' to show user a progress bar like following: [============>........] resync = 61.4% 'curr_resync' and 'recovery_active' is updated in md_do_sync(), and status_resync() can read them concurrently, hence it's possible that 'curr_resync - recovery_active' can overflow to a huge number. In this case status_resync() will be stuck in the loop to pri... • https://git.kernel.org/stable/c/b4acb6c3ede88d6b7d33742a09e63cfce5e7fb69 •
CVSS: 9.3EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53618 – btrfs: reject invalid reloc tree root keys with stack dump
https://notcve.org/view.php?id=CVE-2023-53618
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the abo... • https://git.kernel.org/stable/c/314135b7bae9618a317874ae195272682cf2d5d4 •
CVSS: 7.2EPSS: 0%CPEs: 9EXPL: 0CVE-2022-50534 – dm thin: Use last transaction's pmd->root when commit failed
https://notcve.org/view.php?id=CVE-2022-50534
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: dm thin: Use last transaction's pmd->root when commit failed Recently we found a softlock up problem in dm thin pool btree lookup code due to corrupted metadata: Kernel panic - not syncing: softlockup: hung tasks CPU: 7 PID: 2669225 Comm: kworker/u16:3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: dm-thin do_worker [dm_thin_pool] Call Trace:
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2022-50527 – drm/amdgpu: Fix size validation for non-exclusive domains (v4)
https://notcve.org/view.php?id=CVE-2022-50527
07 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix size validation for non-exclusive domains (v4) Fix amdgpu_bo_validate_size() to check whether the TTM domain manager for the requested memory exists, else we get a kernel oops when dereferencing "man". v2: Make the patch standalone, i.e. not dependent on local patches. v3: Preserve old behaviour and just check that the manager pointer is not NULL. v4: Complain if GTT domain requested and it is uninitialized--most likely a bu... • https://git.kernel.org/stable/c/80546eef216854a7bd47e39e828f04b406c00599 • CWE-476: NULL Pointer Dereference •