CVSS: 7.1EPSS: %CPEs: 8EXPL: 0CVE-2023-53174 – scsi: core: Fix possible memory leak if device_add() fails
https://notcve.org/view.php?id=CVE-2023-53174
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to decrease the reference count in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanp(). In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix possible memory ... • https://git.kernel.org/stable/c/ee959b00c335d7780136c5abda37809191fe52c3 •
CVSS: 5.5EPSS: %CPEs: 4EXPL: 0CVE-2023-53173 – tty: pcn_uart: fix memory leak with using debugfs_lookup()
https://notcve.org/view.php?id=CVE-2023-53173
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: tty: pcn_uart: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. In the Linux kernel, the following vulnerability has been resolved: tty: pcn_uart: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the ... • https://git.kernel.org/stable/c/cf042964c2fa72950bbbf25b2cdd732b873e89db •
CVSS: 7.1EPSS: %CPEs: 5EXPL: 0CVE-2023-53171 – vfio/type1: prevent underflow of locked_vm via exec()
https://notcve.org/view.php?id=CVE-2023-53171
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: vfio/type1: prevent underflow of locked_vm via exec() When a vfio container is preserved across exec, the task does not change, but it gets a new mm with locked_vm=0, and loses the count from existing dma mappings. If the user later unmaps a dma mapping, locked_vm underflows to a large unsigned value, and a subsequent dma map request fails with ENOMEM in __account_locked_vm. To avoid underflow, grab and save the mm at the time a dma is mapp... • https://git.kernel.org/stable/c/73fa0d10d077d9521ee2dace2307ae2c9a965336 •
CVSS: 7.1EPSS: %CPEs: 8EXPL: 0CVE-2023-53165 – udf: Fix uninitialized array access for some pathnames
https://notcve.org/view.php?id=CVE-2023-53165
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: udf: Fix uninitialized array access for some pathnames For filenames that begin with . and are between 2 and 5 characters long, UDF charset conversion code would read uninitialized memory in the output buffer. The only practical impact is that the name may be prepended a "unification hash" when it is not actually needed but still it is good to fix this. In the Linux kernel, the following vulnerability has been resolved: udf: Fix uninitializ... • https://git.kernel.org/stable/c/008ae78d1e12efa904dc819b1ec83e2bca6b2c56 •
CVSS: 7.1EPSS: %CPEs: 8EXPL: 0CVE-2023-53153 – wifi: cfg80211: Fix use after free for wext
https://notcve.org/view.php?id=CVE-2023-53153
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: Fix use after free for wext Key information in wext.connect is not reset on (re)connect and can hold data from a previous connection. Reset key data to avoid that drivers or mac80211 incorrectly detect a WEP connection request and access the freed or already reused memory. Additionally optimize cfg80211_sme_connect() and avoid an useless schedule of conn_work. In the Linux kernel, the following vulnerability has been resolve... • https://git.kernel.org/stable/c/fffd0934b9390f34bec45762192b7edd3b12b4b5 •
CVSS: 7.8EPSS: %CPEs: 8EXPL: 0CVE-2023-53151 – md/raid10: prevent soft lockup while flush writes
https://notcve.org/view.php?id=CVE-2023-53151
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: md/raid10: prevent soft lockup while flush writes Currently, there is no limit for raid1/raid10 plugged bio. While flushing writes, raid1 has cond_resched() while raid10 doesn't, and too many writes can cause soft lockup. Follow up soft lockup can be triggered easily with writeback test for raid10 with ramdisks: watchdog: BUG: soft lockup - CPU#10 stuck for 27s! [md0_raid10:1293] Call Trace:
CVSS: 7.1EPSS: %CPEs: 8EXPL: 0CVE-2023-53150 – scsi: qla2xxx: Pointer may be dereferenced
https://notcve.org/view.php?id=CVE-2023-53150
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Pointer may be dereferenced Klocwork tool reported pointer 'rport' returned from call to function fc_bsg_to_rport() may be NULL and will be dereferenced. Add a fix to validate rport before dereferencing. In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Pointer may be dereferenced Klocwork tool reported pointer 'rport' returned from call to function fc_bsg_to_rport() may be NULL and will be de... • https://git.kernel.org/stable/c/005961bd8f066fe931104f67c34ebfcc7f240099 •
CVSS: 5.5EPSS: %CPEs: 8EXPL: 0CVE-2023-53148 – igb: Fix igb_down hung on surprise removal
https://notcve.org/view.php?id=CVE-2023-53148
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: igb: Fix igb_down hung on surprise removal In a setup where a Thunderbolt hub connects to Ethernet and a display through USB Type-C, users may experience a hung task timeout when they remove the cable between the PC and the Thunderbolt hub. This is because the igb_down function is called multiple times when the Thunderbolt hub is unplugged. For example, the igb_io_error_detected triggers the first call, and the igb_remove triggers the secon... • https://git.kernel.org/stable/c/c2312e1d12b1c3ee4100c173131b102e2aed4d04 •
CVSS: 5.5EPSS: %CPEs: 8EXPL: 0CVE-2023-53147 – xfrm: add NULL check in xfrm_update_ae_params
https://notcve.org/view.php?id=CVE-2023-53147
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: xfrm: add NULL check in xfrm_update_ae_params Normally, x->replay_esn and x->preplay_esn should be allocated at xfrm_alloc_replay_state_esn(...) in xfrm_state_construct(...), hence the xfrm_update_ae_params(...) is okay to update them. However, the current implementation of xfrm_new_ae(...) allows a malicious user to directly dereference a NULL pointer and crash the kernel like below. BUG: kernel NULL pointer dereference, address: 000000000... • https://git.kernel.org/stable/c/d8647b79c3b7e223ac051439d165bc8e7bbb832f •
CVSS: 8.8EPSS: %CPEs: 9EXPL: 0CVE-2022-50261 – drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()
https://notcve.org/view.php?id=CVE-2022-50261
15 Sep 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid() With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. A proposed warning in clang... • https://git.kernel.org/stable/c/b2c92b2a3801b09b709cbefd9a9e4944b72400bf •