CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53842 – ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove
https://notcve.org/view.php?id=CVE-2023-53842
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove The MBHC resources must be released on component probe failure and removal so can not be tied to the lifetime of the component device. This is specifically needed to allow probe deferrals of the sound card which otherwise fails when reprobing the codec component: snd-sc8280xp sound: ASoC: failed to instantiate card -517 genirq: Flags mismatch irq 299. 00002001 (mbhc sw intr) ... • https://git.kernel.org/stable/c/0e5c9e7ff899808afa4e2b08c2e6ccc469bed681 •
CVSS: 7.8EPSS: 0%CPEs: 6EXPL: 0CVE-2023-53841 – devlink: report devlink_port_type_warn source device
https://notcve.org/view.php?id=CVE-2023-53841
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: devlink: report devlink_port_type_warn source device devlink_port_type_warn is scheduled for port devlink and warning when the port type is not set. But from this warning it is not easy found out which device (driver) has no devlink port set. [ 3709.975552] Type was not set for devlink port. [ 3709.975579] WARNING: CPU: 1 PID: 13092 at net/devlink/leftover.c:6775 devlink_port_type_warn+0x11/0x20 [ 3709.993967] Modules linked in: openvswitch... • https://git.kernel.org/stable/c/970c7035f4b03c7be9f49c403ccf6fb0b70039a1 •
CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53840 – usb: early: xhci-dbc: Fix a potential out-of-bound memory access
https://notcve.org/view.php?id=CVE-2023-53840
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: usb: early: xhci-dbc: Fix a potential out-of-bound memory access If xdbc_bulk_write() fails, the values in 'buf' can be anything. So the string is not guaranteed to be NULL terminated when xdbc_trace() is called. Reserve an extra byte, which will be zeroed automatically because 'buf' is a static variable, in order to avoid troubles, should it happen. In the Linux kernel, the following vulnerability has been resolved: usb: early: xhci-dbc: F... • https://git.kernel.org/stable/c/aeb9dd1de98c1a5f2007ea5d2a154c1244caf8a0 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53839 – dccp: fix data-race around dp->dccps_mss_cache
https://notcve.org/view.php?id=CVE-2023-53839
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: dccp: fix data-race around dp->dccps_mss_cache dccp_sendmsg() reads dp->dccps_mss_cache before locking the socket. Same thing in do_dccp_getsockopt(). Add READ_ONCE()/WRITE_ONCE() annotations, and change dccp_sendmsg() to check again dccps_mss_cache after socket is locked. In the Linux kernel, the following vulnerability has been resolved: dccp: fix data-race around dp->dccps_mss_cache dccp_sendmsg() reads dp->dccps_mss_cache before locking... • https://git.kernel.org/stable/c/7c657876b63cb1d8a2ec06f8fc6c37bb8412e66c •
CVSS: 6.3EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53838 – f2fs: synchronize atomic write aborts
https://notcve.org/view.php?id=CVE-2023-53838
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: f2fs: synchronize atomic write aborts To fix a race condition between atomic write aborts, I use the inode lock and make COW inode to be re-usable thoroughout the whole atomic file inode lifetime. In the Linux kernel, the following vulnerability has been resolved: f2fs: synchronize atomic write aborts To fix a race condition between atomic write aborts, I use the inode lock and make COW inode to be re-usable thoroughout the whole atomic fil... • https://git.kernel.org/stable/c/3db1de0e582c358dd013f3703cd55b5fe4076436 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-53837 – drm/msm: fix NULL-deref on snapshot tear down
https://notcve.org/view.php?id=CVE-2023-53837
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/msm: fix NULL-deref on snapshot tear down In case of early initialisation errors and on platforms that do not use the DPU controller, the deinitilisation code can be called with the kms pointer set to NULL. Patchwork: https://patchwork.freedesktop.org/patch/525099/ In the Linux kernel, the following vulnerability has been resolved: drm/msm: fix NULL-deref on snapshot tear down In case of early initialisation errors and on platforms that... • https://git.kernel.org/stable/c/98659487b845c05b6bed85d881713545db674c7c •
CVSS: 6.9EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53836 – bpf, sockmap: Fix skb refcnt race after locking changes
https://notcve.org/view.php?id=CVE-2023-53836
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix skb refcnt race after locking changes There is a race where skb's from the sk_psock_backlog can be referenced after userspace side has already skb_consumed() the sk_buff and its refcnt dropped to zer0 causing use after free. The flow is the following: while ((skb = skb_peek(&psock->ingress_skb)) sk_psock_handle_Skb(psock, skb, ..., ingress) if (!ingress) ... sk_psock_skb_ingress sk_psock_skb_ingress_enqueue(skb) msg->skb =... • https://git.kernel.org/stable/c/799aa7f98d53e0f541fa6b4dc9aa47b4ff2178e3 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2023-53834 – iio: adc: ina2xx: avoid NULL pointer dereference on OF device match
https://notcve.org/view.php?id=CVE-2023-53834
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: iio: adc: ina2xx: avoid NULL pointer dereference on OF device match The affected lines were resulting in a NULL pointer dereference on our platform because the device tree contained the following list of compatible strings: power-sensor@40 { compatible = "ti,ina232", "ti,ina231"; ... }; Since the driver doesn't declare a compatible string "ti,ina232", the OF matching succeeds on "ti,ina231". But the I2C device ID info is populated via the f... • https://git.kernel.org/stable/c/c43a102e67db99c8bfe6e8a9280cec13ff53b789 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-53833 – drm/i915: Fix NULL ptr deref by checking new_crtc_state
https://notcve.org/view.php?id=CVE-2023-53833
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/i915: Fix NULL ptr deref by checking new_crtc_state intel_atomic_get_new_crtc_state can return NULL, unless crtc state wasn't obtained previously with intel_atomic_get_crtc_state, so we must check it for NULLness here, just as in many other places, where we can't guarantee that intel_atomic_get_crtc_state was called. We are currently getting NULL ptr deref because of that, so this fix was confirmed to help. (cherry picked from commit 1d... • https://git.kernel.org/stable/c/74a75dc908692dd0548209004e53832c02433c0c •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-53832 – md/raid10: fix null-ptr-deref in raid10_sync_request
https://notcve.org/view.php?id=CVE-2023-53832
09 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref in raid10_sync_request init_resync() inits mempool and sets conf->have_replacemnt at the beginning of sync, close_sync() frees the mempool when sync is completed. After [1] recovery might be skipped and init_resync() is called but close_sync() is not. null-ptr-deref occurs with r10bio->dev[i].repl_bio. The following is one way to reproduce the issue. 1) create a array, wait for resync to complete, mddev->recove... • https://git.kernel.org/stable/c/7e83ccbecd608b971f340e951c9e84cd0343002f •