CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53576 – null_blk: Always check queue mode setting from configfs
https://notcve.org/view.php?id=CVE-2023-53576
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: null_blk: Always check queue mode setting from configfs Make sure to check device queue mode in the null_validate_conf() and return error for NULL_Q_RQ as we don't allow legacy I/O path, without this patch we get OOPs when queue mode is set to 1 from configfs, following are repro steps :- modprobe null_blk nr_devices=0 mkdir config/nullb/nullb0 echo 1 > config/nullb/nullb0/memory_backed echo 4096 > config/nullb/nullb0/blocksize echo 20480 >... • https://git.kernel.org/stable/c/e50b1e327aeb4b224364aa6f85c1713ff8b3654b • CWE-1288: Improper Validation of Consistency within Input •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53575 – wifi: iwlwifi: mvm: fix potential array out of bounds access
https://notcve.org/view.php?id=CVE-2023-53575
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix potential array out of bounds access Account for IWL_SEC_WEP_KEY_OFFSET when needed while verifying key_len size in iwl_mvm_sec_key_add(). In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix potential array out of bounds access Account for IWL_SEC_WEP_KEY_OFFSET when needed while verifying key_len size in iwl_mvm_sec_key_add(). The SUSE Linux Enterprise 15 SP6 Azure kernel was ... • https://git.kernel.org/stable/c/5c75a208c2449c6ea24f07610cc052f6a352246c • CWE-125: Out-of-bounds Read •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2023-53574 – wifi: rtw88: delete timer and free skb queue when unloading
https://notcve.org/view.php?id=CVE-2023-53574
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: delete timer and free skb queue when unloading Fix possible crash and memory leak on driver unload by deleting TX purge timer and freeing C2H queue in 'rtw_core_deinit()', shrink critical section in the latter by freeing COEX queue out of TX report lock scope. In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: delete timer and free skb queue when unloading Fix possible crash and memory leak on driv... • https://git.kernel.org/stable/c/e3037485c68ec1a299ff41160d8fedbd4abc29b9 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53573 – clk: rs9: Fix suspend/resume
https://notcve.org/view.php?id=CVE-2023-53573
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: rs9: Fix suspend/resume Disabling the cache in commit 2ff4ba9e3702 ("clk: rs9: Fix I2C accessors") without removing cache synchronization in resume path results in a kernel panic as map->cache_ops is unset, due to REGCACHE_NONE. Enable flat cache again to support resume again. num_reg_defaults_raw is necessary to read the cache defaults from hardware. Some registers are strapped in hardware and cannot be provided in software. In the Li... • https://git.kernel.org/stable/c/2ff4ba9e37024735f5cefc5ea2a73fc66addfe0e •
CVSS: 7.1EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53572 – clk: imx: scu: use _safe list iterator to avoid a use after free
https://notcve.org/view.php?id=CVE-2023-53572
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: use _safe list iterator to avoid a use after free This loop is freeing "clk" so it needs to use list_for_each_entry_safe(). Otherwise it dereferences a freed variable to get the next item on the loop. In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: use _safe list iterator to avoid a use after free This loop is freeing "clk" so it needs to use list_for_each_entry_safe(). Otherwise it derefere... • https://git.kernel.org/stable/c/77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 • CWE-825: Expired Pointer Dereference •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53571 – drm/i915: Make intel_get_crtc_new_encoder() less oopsy
https://notcve.org/view.php?id=CVE-2023-53571
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in the atomic state. Get the dev pointer from the atomic state instead of the potentially NULL encoder to avoid that. (cherry picked from commit 3b6692357f70498f617ea1b31a0378070a0acf1c) In the Linux kernel, the following vulnerability ... • https://git.kernel.org/stable/c/3a47ae201e074945bbde0b088e4c1215c07f4d75 •
CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53570 – wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems()
https://notcve.org/view.php?id=CVE-2023-53570
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems() nl80211_parse_mbssid_elems() uses a u8 variable num_elems to count the number of MBSSID elements in the nested netlink attribute attrs, which can lead to an integer overflow if a user of the nl80211 interface specifies 256 or more elements in the corresponding attribute in userspace. The integer overflow can lead to a heap buffer overflow as num_elems determines the size of... • https://git.kernel.org/stable/c/dc1e3cb8da8b414b37208b2fb6755fef8122504b • CWE-190: Integer Overflow or Wraparound •
CVSS: 7.1EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53569 – ext2: Check block size validity during mount
https://notcve.org/view.php?id=CVE-2023-53569
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: ext2: Check block size validity during mount Check that log of block size stored in the superblock has sensible value. Otherwise the shift computing the block size can overflow leading to undefined behavior. In the Linux kernel, the following vulnerability has been resolved: ext2: Check block size validity during mount Check that log of block size stored in the superblock has sensible value. Otherwise the shift computing the block size can ... • https://git.kernel.org/stable/c/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53568 – s390/zcrypt: don't leak memory if dev_set_name() fails
https://notcve.org/view.php?id=CVE-2023-53568
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: don't leak memory if dev_set_name() fails When dev_set_name() fails, zcdn_create() doesn't free the newly allocated resources. Do it. In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: don't leak memory if dev_set_name() fails When dev_set_name() fails, zcdn_create() doesn't free the newly allocated resources. Do it. The SUSE Linux Enterprise 15 SP6 Azure kernel was updated to fix various security ... • https://git.kernel.org/stable/c/00fab2350e6b91e57b3cdcd5d9f01056775a921d • CWE-772: Missing Release of Resource after Effective Lifetime •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53567 – spi: qup: Don't skip cleanup in remove's error path
https://notcve.org/view.php?id=CVE-2023-53567
04 Oct 2025 — In the Linux kernel, the following vulnerability has been resolved: spi: qup: Don't skip cleanup in remove's error path Returning early in a platform driver's remove callback is wrong. In this case the dma resources are not released in the error path. this is never retried later and so this is a permanent leak. To fix this, only skip hardware disabling if waking the device fails. In the Linux kernel, the following vulnerability has been resolved: spi: qup: Don't skip cleanup in remove's error path Returning... • https://git.kernel.org/stable/c/64ff247a978facc437d40f0c9b754675846a98f0 •