CVSS: -EPSS: %CPEs: 8EXPL: 0CVE-2023-53297 – Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
https://notcve.org/view.php?id=CVE-2023-53297
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp conn->chan_lock isn't acquired before l2cap_get_chan_by_scid, if l2cap_get_chan_by_scid returns NULL, then 'bad unlock balance' is triggered. • https://git.kernel.org/stable/c/5f352a56f0e607e6ff539cbf12156bfd8af232be •
CVSS: -EPSS: %CPEs: 8EXPL: 0CVE-2023-53295 – udf: Do not update file length for failed writes to inline files
https://notcve.org/view.php?id=CVE-2023-53295
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: udf: Do not update file length for failed writes to inline files When write to inline file fails (or happens only partly), we still updated length of inline data as if the whole write succeeded. Fix the update of length of inline data to happen only if the write succeeds. • https://git.kernel.org/stable/c/5621f7a8139053d0c3c47fb68ee9f602139eb40a •
CVSS: -EPSS: %CPEs: 3EXPL: 0CVE-2023-53293 – Bluetooth: btrtl: check for NULL in btrtl_set_quirks()
https://notcve.org/view.php?id=CVE-2023-53293
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: check for NULL in btrtl_set_quirks() The btrtl_set_quirks() has accessed btrtl_dev->ic_info->lmp_subver since b8e482d02513. However, if installing a Realtek Bluetooth controller without the driver supported, it will hit the NULL point accessed. Add a check for NULL to avoid the Kernel Oops. • https://git.kernel.org/stable/c/ea160ece08668a30ce69f92cc08e87da54a64a9c •
CVSS: -EPSS: %CPEs: 2EXPL: 0CVE-2023-53292 – blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none
https://notcve.org/view.php?id=CVE-2023-53292
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix NULL dereference on q->elevator in blk_mq_elv_switch_none After grabbing q->sysfs_lock, q->elevator may become NULL because of elevator switch. Fix the NULL dereference on q->elevator by checking it with lock. • https://git.kernel.org/stable/c/3e977386521b71471e66ec2ba82efdfcc456adf2 •
CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2023-53290 – samples/bpf: Fix fout leak in hbm's run_bpf_prog
https://notcve.org/view.php?id=CVE-2023-53290
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: samples/bpf: Fix fout leak in hbm's run_bpf_prog Fix fout being fopen'ed but then not subsequently fclose'd. In the affected branch, fout is otherwise going out of scope. • https://git.kernel.org/stable/c/a7ec2f424f6edad34651137783a0a59eca9aa37e •
CVSS: -EPSS: %CPEs: 6EXPL: 0CVE-2023-53288 – drm/client: Fix memory leak in drm_client_modeset_probe
https://notcve.org/view.php?id=CVE-2023-53288
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/client: Fix memory leak in drm_client_modeset_probe When a new mode is set to modeset->mode, the previous mode should be freed. This fixes the following kmemleak report: drm_mode_duplicate+0x45/0x220 [drm] drm_client_modeset_probe+0x944/0xf50 [drm] __drm_fb_helper_initial_config_and_unlock+0xb4/0x2c0 [drm_kms_helper] drm_fbdev_client_hotplug+0x2bc/0x4d0 [drm_kms_helper] drm_client_register+0x169/0x240 [drm] ast_pci_probe+0x142/0x190 [as... • https://git.kernel.org/stable/c/5d580017bdb9b3e930b6009e467e5e1589f8ca8a •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2023-53287 – usb: cdns3: Put the cdns set active part outside the spin lock
https://notcve.org/view.php?id=CVE-2023-53287
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: Put the cdns set active part outside the spin lock The device may be scheduled during the resume process, so this cannot appear in atomic operations. Since pm_runtime_set_active will resume suppliers, put set active outside the spin lock, which is only used to protect the struct cdns data structure, otherwise the kernel will report the following warning: BUG: sleeping function called from invalid context at drivers/base/power/ru... • https://git.kernel.org/stable/c/c861a61be6d30538ebcf7fcab1d43f244e298840 •
CVSS: -EPSS: %CPEs: 5EXPL: 0CVE-2023-53286 – RDMA/mlx5: Return the firmware result upon destroying QP/RQ
https://notcve.org/view.php?id=CVE-2023-53286
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Return the firmware result upon destroying QP/RQ Previously when destroying a QP/RQ, the result of the firmware destruction function was ignored and upper layers weren't informed about the failure. Which in turn could lead to various problems since when upper layer isn't aware of the failure it continues its operation thinking that the related QP/RQ was successfully destroyed while it actually wasn't, which could lead to the belo... • https://git.kernel.org/stable/c/73311dd831858d797cf8ebe140654ed519b41c36 •
CVSS: -EPSS: %CPEs: 9EXPL: 0CVE-2023-53285 – ext4: add bounds checking in get_max_inline_xattr_value_size()
https://notcve.org/view.php?id=CVE-2023-53285
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: ext4: add bounds checking in get_max_inline_xattr_value_size() Normally the extended attributes in the inode body would have been checked when the inode is first opened, but if someone is writing to the block device while the file system is mounted, it's possible for the inode table to get corrupted. Add bounds checking to avoid reading beyond the end of allocated memory if this happens. • https://git.kernel.org/stable/c/5a229d21b98d132673096710e8281ef522dab1d1 •
CVSS: -EPSS: %CPEs: 4EXPL: 0CVE-2023-53282 – scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write
https://notcve.org/view.php?id=CVE-2023-53282
16 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine: BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc] Use-after-free read at 0x0000000000cf164d (in kfence-#111): lpfc_wr_object+0x235/0x310 [lpfc] lpfc_write_firmware.cold+0x206/0x30d [lpfc] lpfc_sli4_request_firmware_update+0xa6/0x100... • https://git.kernel.org/stable/c/51ab4eb1a25e73c7fc2ad9026520c4d8369c93cc •