Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
f codec->regmap is set to NULL right after the condition is checked, a null-pointer dereference can occur in the called function regcache_sync(): map->lock(map->lock_arg); --> Line 360 in drivers/base/regmap/regcache.c To fix this possible null-pointer dereference caused by data race, the mutex_lock coverage is extended to protect the if statement as well as the function call to regcache_sync(). [ Note: the lack of the regmap_lock itself is harmless for the current codec driver implementations, as snd_hdac_regmap_sync() is only for PM runtime resume that is prohibited during the codec probe. But the change makes the whole code more consistent, so it's merged as is -- tiwai ] References: - ht
g the codec probe. But the change makes the whole code more consistent, so it's merged as is -- tiwai ] References: - https://git.kernel.org/stable/c/109f0aaa0b8838a88af9125b79579023539300a7 - https://git.kernel.org/stable/c/9f9eed451176ffcac6b5ba0f6dae1a6b4a1cb0eb - https://git.kernel.org/stable/c/8703b26387e1fa4f8749db98d24c67617b873acb - https://git.kernel.org/stable/c/cdd412b528dee6e0851c4735d6676ec138da13a4 - https://git.kernel.org/stable/c/b32e40379e5b2814de0c4bc199edc2d82317dc07 - https://git.kernel.org/stable/c/1f4a08fed450db87fbb5ff5105354158bdbe1a22
CVE ID: CVE-2023-53276 State: PUBLISHED Published: 2025-09-16T08:11:11.328Z Last Updated: 2025-09-16T08:11:11.328Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory is not freed. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program 'tmpfile' just opening a tmpfile: unreferenced object 0xffff888101
ak. The report below is triggered by a simple program 'tmpfile' just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode. References: - https://git.kernel.org/stable/c/8ad8c67a897e68426e85990ebfe0a7d1f71fc79f - https://git.kernel.org/stable/c/107d481642c356a5668058066360fc473911e628 - https://git.kernel.org/stable/c/823f554747f8aafaa965fb2f3ae794110ed429ef - https://git.kernel.org/stable/c/b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3 - https://git.kernel.org/sta
3ae794110ed429ef - https://git.kernel.org/stable/c/b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3 - https://git.kernel.org/stable/c/ce840284929b75dbbf062e0ce7fcb78a63b08b5e - https://git.kernel.org/stable/c/29738e1bcc799dd754711d4e4aab967f0c018175 - https://git.kernel.org/stable/c/fd197308c0e4f738c7ea687d5332035c5753881c - https://git.kernel.org/stable/c/1e43d4284bdc3bd34bd770fea13910ac37ab0618 - https://git.kernel.org/stable/c/1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3
CVE ID: CVE-2023-53277 State: PUBLISHED Published: 2025-09-16T08:11:12.194Z Last Updated: 2025-09-16T08:11:12.194Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: iwl3945: Add missing check for create_singlethread_workqueue Add the check for the return value of the create_singlethread_workqueue in order to avoid NULL pointer dereference. References: - https://git.kernel.org/stable/c/3ae2fc4de12686f3fe695824169c1272c9f798f7 - https://git.kernel.org/stable/c/7e594abc0424e4f8c2385f11aefeaadcfc507aa5 - https://git.kernel.org/stable/c/2f80b3ff92514ebd227e5c55d3d1e480401b02b7 - https://git.kernel.org/stable/c/505c74c4c0b1c5bcaa9
//git.kernel.org/stable/c/2f80b3ff92514ebd227e5c55d3d1e480401b02b7 - https://git.kernel.org/stable/c/505c74c4c0b1c5bcaa98a93b3087c268156070f1 - https://git.kernel.org/stable/c/34f611204ae589bd5c494b10b41fb13436bd3c3f - https://git.kernel.org/stable/c/17e07d6587c55015956862ef3b101fd45fa49fbc - https://git.kernel.org/stable/c/1fdeb8b9f29dfd64805bb49475ac7566a3cb06cb
CVE ID: CVE-2023-53278 State: PUBLISHED Published: 2025-09-16T08:11:12.997Z Last Updated: 2025-09-16T08:11:12.997Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memory leak in ubifs_sysfs_init() When insmod ubifs.ko, a kmemleak reported as below: unreferenced object 0xffff88817fb1a780 (size 8): comm "insmod", pid 25265, jiffies 4295239702 (age 100.130s) hex dump (first 8 bytes): 75 62 69 66 73 00 ff ff ubifs... backtrace: [<ffffffff81b3fc4c>] slab_post_alloc_hook+0x9c/0x3c0 [<ffffffff81b44bf3>] __kmalloc_track_caller+0x183/0x410 [<ffffffff8198d3da>] kstrdup+0x3a/0x80 [<ffffffff8198d486>] kstrdup_const+0x66/0x80 [<ff
malloc_track_caller+0x183/0x410 [<ffffffff8198d3da>] kstrdup+0x3a/0x80 [<ffffffff8198d486>] kstrdup_const+0x66/0x80 [<ffffffff83989325>] kvasprintf_const+0x155/0x190 [<ffffffff83bf55bb>] kobject_set_name_vargs+0x5b/0x150 [<ffffffff83bf576b>] kobject_set_name+0xbb/0xf0 [<ffffffff8100204c>] do_one_initcall+0x14c/0x5a0 [<ffffffff8157e380>] do_init_module+0x1f0/0x660 [<ffffffff815857be>] load_module+0x6d7e/0x7590 [<ffffffff8158644f>] __do_sys_finit_module+0x19f/0x230 [<ffffffff815866b3>] __x64_sys_finit_module+0x73/0xb0 [<ffffffff88c98e85>] do_syscall_64+0x35/0x80 [<ffffffff88e00087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd When kset_register() failed, we should call kset_put to cleanup it. Ref
00087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd When kset_register() failed, we should call kset_put to cleanup it. References: - https://git.kernel.org/stable/c/1c5fdf2d4647219d2267ccb08c7f2c7095bf3450 - https://git.kernel.org/stable/c/d42c2b18c42da7378e67b6414aafe93b65de89d1 - https://git.kernel.org/stable/c/203a55f04f66eea1a1ca7e5a302a7f5c99c62327
CVE ID: CVE-2023-53279 State: PUBLISHED Published: 2025-09-16T08:11:13.712Z Last Updated: 2025-09-16T08:11:13.712Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: misc: vmw_balloon: 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. References: - https://git.kernel.org/stable/c/b94b39bf3d545671f210a2257d18e33c8b874699 - https://git.kernel.org/stable/c/d1c545e44c1ec08bef0c0c14e632eec516431e9c - https://git.kernel.org
a2257d18e33c8b874699 - https://git.kernel.org/stable/c/d1c545e44c1ec08bef0c0c14e632eec516431e9c - https://git.kernel.org/stable/c/f7651fa88b17c2d7af949981a2423179db5e9453 - https://git.kernel.org/stable/c/209cdbd07cfaa4b7385bad4eeb47e5ec1887d33d
CVE ID: CVE-2023-53280 State: PUBLISHED Published: 2025-09-16T08:11:14.533Z Last Updated: 2025-09-16T08:11:14.533Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue System crash when qla2x00_start_sp(sp) returns error code EGAIN and wake_up gets called for uninitialized wait queue sp->nvme_ls_waitq. qla2xxx [0000:37:00.1]-2121:5: Returning existing qpair of ffff8ae2c0513400 for idx=0 qla2xxx [0000:37:00.1]-700e:5: qla2x00_start_sp failed = 11 BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI Hardware name: HPE ProLia
ndle kernel NULL pointer dereference at 0000000000000000 PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 09/03/2021 Workqueue: nvme-wq nvme_fc_connect_ctrl_work [nvme_fc] RIP: 0010:__wake_up_common+0x4c/0x190 RSP: 0018:ffff95f3e0cb7cd0 EFLAGS: 00010086 RAX: 0000000000000000 RBX: ffff8b08d3b26328 RCX: 0000000000000000 RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffff8b08d3b26320 RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffffffffffe8 R10: 0000000000000000 R11: ffff95f3e0cb7a60 R12: ffff95f3e0cb7d20 R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8b2fdf6c0000(0000) knl
3: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8b2fdf6c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000002f1e410002 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: __wake_up_common_lock+0x7c/0xc0 qla_nvme_ls_req+0x355/0x4c0 [qla2xxx] ? __nvme_fc_send_ls_req+0x260/0x380 [nvme_fc] ? nvme_fc_send_ls_req.constprop.42+0x1a/0x45 [nvme_fc] ? nvme_fc_connect_ctrl_work.cold.63+0x1e3/0xa7d [nvme_fc] Remove unused nvme_ls_waitq wait queue. nvme_ls_waitq log
_fc] ? nvme_fc_connect_ctrl_work.cold.63+0x1e3/0xa7d [nvme_fc] Remove unused nvme_ls_waitq wait queue. nvme_ls_waitq logic was removed previously in the commits tagged Fixed: below. References: - https://git.kernel.org/stable/c/b7084ebf4f54d46fed5153112d685f4137334175 - https://git.kernel.org/stable/c/0b1ce92fabdb7d02ddf8641230a06e2752ae5baa - https://git.kernel.org/stable/c/522ee1b3030f3b6b5fd59489d12b4ca767c9e5da - https://git.kernel.org/stable/c/f459d586fdf12c53116c9fddf43065165fdd5969 - https://git.kernel.org/stable/c/92529387a0066754fd9cda080fb3298b8cca750c - https://git.kernel.org/stable/c/20fce500b232b970e40312a9c97e7f3b6d7a709c
CVE ID: CVE-2023-53281 State: PUBLISHED Published: 2025-09-16T08:11:15.364Z Last Updated: 2025-09-16T08:11:15.364Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8723bs: Fix locking in _rtw_join_timeout_handler() Commit 041879b12ddb ("drivers: staging: rtl8192bs: Fix deadlock in rtw_joinbss_event_prehandle()") besides fixing the deadlock also modified _rtw_join_timeout_handler() to use spin_[un]lock_irq() instead of spin_[un]lock_bh(). _rtw_join_timeout_handler() calls rtw_do_join() which takes pmlmepriv->scanned_queue.lock using spin_[un]lock_bh(). This spin_unlock_bh() call re-enables softirqs which trigg
takes pmlmepriv->scanned_queue.lock using spin_[un]lock_bh(). This spin_unlock_bh() call re-enables softirqs which triggers an oops in kernel/softirq.c: __local_bh_enable_ip() when it calls lockdep_assert_irqs_enabled(): [ 244.506087] WARNING: CPU: 2 PID: 0 at kernel/softirq.c:376 __local_bh_enable_ip+0xa6/0x100 ... [ 244.509022] Call Trace: [ 244.509048] <IRQ> [ 244.509100] _rtw_join_timeout_handler+0x134/0x170 [r8723bs] [ 244.509468] ? __pfx__rtw_join_timeout_handler+0x10/0x10 [r8723bs] [ 244.509772] ? __pfx__rtw_join_timeout_handler+0x10/0x10 [r8723bs] [ 244.510076] call_timer_fn+0x95/0x2a0 [ 244.510200] __run_timers.part.0+0x1da/0x2d0 This oops is causd by the switch to spin_[un]lock_irq
_timer_fn+0x95/0x2a0 [ 244.510200] __run_timers.part.0+0x1da/0x2d0 This oops is causd by the switch to spin_[un]lock_irq() which disables the IRQs for the entire duration of _rtw_join_timeout_handler(). Disabling the IRQs is not necessary since all code taking this lock runs from either user contexts or from softirqs, switch back to spin_[un]lock_bh() to fix this. References: - https://git.kernel.org/stable/c/209850f17717a3b5cc558578bef5631ac7045539 - https://git.kernel.org/stable/c/2a50e44a66d268ee5db3d177f1fdc1503dbce6e7 - https://git.kernel.org/stable/c/dc327e87c6d9bfd9ee08e76396b3c0ba848ec554 - https://git.kernel.org/stable/c/4ab1bace1dd3875371b481ef4301c4671bddea22 - https://git.kernel.
e08e76396b3c0ba848ec554 - https://git.kernel.org/stable/c/4ab1bace1dd3875371b481ef4301c4671bddea22 - https://git.kernel.org/stable/c/215792eda008f6a1e7ed9d77fa20d582d22bb114
CVE ID: CVE-2023-53282 State: PUBLISHED Published: 2025-09-16T08:11:16.083Z Last Updated: 2025-09-16T08:11:16.083Z Vendors: Linux Products: Linux Description: 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 [lpfc] lpfc_request_firmware
c] lpfc_write_firmware.cold+0x206/0x30d [lpfc] lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc] lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc] kernfs_fop_write_iter+0x121/0x1b0 new_sync_write+0x11c/0x1b0 vfs_write+0x1ef/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x59/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd The driver accessed wr_object pointer data, which was initialized into mailbox payload memory, after the mailbox object was released back to the mailbox pool. Fix by moving the mailbox free calls to the end of the routine ensuring that we don't reference internal mailbox memory after release. References: - https://git.kernel.org/stable/c/51ab4eb1a25e73c7fc2ad9026520c4d8369c93c
rnal mailbox memory after release. References: - https://git.kernel.org/stable/c/51ab4eb1a25e73c7fc2ad9026520c4d8369c93cc - https://git.kernel.org/stable/c/8dfefa8f424ab208e552df1bfd008b732f3d0ad1 - https://git.kernel.org/stable/c/8becb97918f04bb177bc9c4e00c2bdb302e00944 - https://git.kernel.org/stable/c/21681b81b9ae548c5dae7ae00d931197a27f480c
CVE ID: CVE-2023-53283 State: REJECTED Published: 2025-09-16T08:11:16.808Z Last Updated: 2025-09-16T09:01:55.354Z Description: No description available.
CVE ID: CVE-2023-53284 State: PUBLISHED Published: 2025-09-16T08:11:17.741Z Last Updated: 2025-09-16T08:11:17.741Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: check for null return of devm_kzalloc() in dpu_writeback_init() Because of the possilble failure of devm_kzalloc(), dpu_wb_conn might be NULL and will cause null pointer dereference later. Therefore, it might be better to check it and directly return -ENOMEM. Patchwork: https://patchwork.freedesktop.org/patch/512277/ [DB: fixed typo in commit message] References: - https://git.kernel.org/stable/c/3723c4dbcd14cc96771000ce0b0540801e6ba059 - https://git.kerne
mmit message] References: - https://git.kernel.org/stable/c/3723c4dbcd14cc96771000ce0b0540801e6ba059 - https://git.kernel.org/stable/c/5ee51b19855c5dd72aca57b8014f3b70d7798733 - https://git.kernel.org/stable/c/21e9a838f505178e109ccb3bf19d7808eb0326f4
CVE ID: CVE-2023-53285 State: PUBLISHED Published: 2025-09-16T08:11:18.585Z Last Updated: 2025-09-16T08:11:18.585Z Vendors: Linux Products: Linux Description: 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. References: - https://git.kernel.org/stable/c/5a229d21b98d132673096710e8281ef522da
of allocated memory if this happens. References: - https://git.kernel.org/stable/c/5a229d21b98d132673096710e8281ef522dab1d1 - https://git.kernel.org/stable/c/3d7b8fbcd2273e2b9f4c6de5ce2f4c0cd3cb1205 - https://git.kernel.org/stable/c/486efbbc9445dca7890a1b86adbccb88b91284b0 - https://git.kernel.org/stable/c/4597554b4f7b29e7fd78aa449bab648f8da4ee2c - https://git.kernel.org/stable/c/f22b274429e88d3dc7e79d375b56ce4f2f59f0b4 - https://git.kernel.org/stable/c/1d2caddbeeee56fbbc36b428c5b909c3ad88eb7f - https://git.kernel.org/stable/c/e780058bd75614b66882bc02620ddbd884171560 - https://git.kernel.org/stable/c/88a06a94942c5c0a896e9da1113a6bb29e36cbef - https://git.kernel.org/stable/c/2220eaf90992c11d
ps://git.kernel.org/stable/c/88a06a94942c5c0a896e9da1113a6bb29e36cbef - https://git.kernel.org/stable/c/2220eaf90992c11d888fe771055d4de330385f01
CVE ID: CVE-2023-53286 State: PUBLISHED Published: 2025-09-16T08:11:19.426Z Last Updated: 2025-09-16T08:11:19.426Z Vendors: Linux Products: Linux Description: 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 below kernel WARN. Currently, we
ted QP/RQ was successfully destroyed while it actually wasn't, which could lead to the below kernel WARN. Currently, we return the correct firmware destruction status to upper layers which in case of the RQ would be mlx5_ib_destroy_wq() which was already capable of handling RQ destruction failure or in case of a QP to destroy_qp_common(), which now would actually warn upon qp destruction failure. WARNING: CPU: 3 PID: 995 at drivers/infiniband/core/rdma_core.c:940 uverbs_destroy_ufile_hw+0xcb/0xe0 [ib_uverbs] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm ib
nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core overlay mlx5_core fuse CPU: 3 PID: 995 Comm: python3 Not tainted 5.16.0-rc5+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:uverbs_destroy_ufile_hw+0xcb/0xe0 [ib_uverbs] Code: 41 5c 41 5d 41 5e e9 44 34 f0 e0 48 89 df e8 4c 77 ff ff 49 8b 86 10 01 00 00 48 85 c0 74 a1 4c 89 e7 ff d0 eb 9a 0f 0b eb c1 <0f> 0b be 04 00 00 00 48 89 df e8 b6 f6 ff ff e9 75 ff ff ff 90 0f RSP: 0018:ffff8881533e3e78 EFLAGS: 00010287 RAX: ffff88811b2cf3e0 RBX: ffff888
89 df e8 b6 f6 ff ff e9 75 ff ff ff 90 0f RSP: 0018:ffff8881533e3e78 EFLAGS: 00010287 RAX: ffff88811b2cf3e0 RBX: ffff888106209700 RCX: 0000000000000000 RDX: ffff888106209780 RSI: ffff8881533e3d30 RDI: ffff888109b101a0 RBP: 0000000000000001 R08: ffff888127cb381c R09: 0de9890000000009 R10: ffff888127cb3800 R11: 0000000000000000 R12: ffff888106209780 R13: ffff888106209750 R14: ffff888100f20660 R15: 0000000000000000 FS: 00007f8be353b740(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8bd5b117c0 CR3: 000000012cd8a004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
a004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ib_uverbs_close+0x1a/0x90 [ib_uverbs] __fput+0x82/0x230 task_work_run+0x59/0x90 exit_to_user_mode_prepare+0x138/0x140 syscall_exit_to_user_mode+0x1d/0x50 ? __x64_sys_close+0xe/0x40 do_syscall_64+0x4a/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f8be3ae0abb Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 83 43 f9 ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 c1 43 f9 ff 8b 44 RSP: 002b:00007ffdb51909c0 EFLAGS: 00000293 ORIG_RA
<48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 c1 43 f9 ff 8b 44 RSP: 002b:00007ffdb51909c0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000557bb7f7c020 RCX: 00007f8be3ae0abb RDX: 0000557bb7c74010 RSI: 0000557bb7f14ca0 RDI: 0000000000000005 RBP: 0000557bb7fbd598 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000293 R12: 0000557bb7fbd5b8 R13: 0000557bb7fbd5a8 R14: 0000000000001000 R15: 0000557bb7f7c020 </TASK> References: - https://git.kernel.org/stable/c/73311dd831858d797cf8ebe140654ed519b41c36 - https://git.kernel.org/stable/c/1a650d3ccd79cdd5796edd864683a6b8dd0bf576 - https://git.kernel.org/stable/c/5fe7815e784bf21061885f8112
ernel.org/stable/c/1a650d3ccd79cdd5796edd864683a6b8dd0bf576 - https://git.kernel.org/stable/c/5fe7815e784bf21061885f8112a7108aef5c45bd - https://git.kernel.org/stable/c/04704c201bb08efaf96d7b1396c6864f8984e244 - https://git.kernel.org/stable/c/22664c06e997087fe37f9ba208008c948571214a
CVE ID: CVE-2023-53287 State: PUBLISHED Published: 2025-09-16T08:11:20.304Z Last Updated: 2025-09-17T11:02:53.235Z Vendors: Linux Products: Linux Description: 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/runtime.c:1163 in_atomic(): 1,
lowing warning: BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1163 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 651, name: sh preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 CPU: 0 PID: 651 Comm: sh Tainted: G WC 6.1.20 #1 Hardware name: Freescale i.MX8QM MEK (DT) Call trace: dump_backtrace.part.0+0xe0/0xf0 show_stack+0x18/0x30 dump_stack_lvl+0x64/0x80 dump_stack+0x1c/0x38 __might_resched+0x1fc/0x240 __might_sleep+0x68/0xc0 __pm_runtime_resume+0x9c/0xe0 rpm_get_suppliers+0x68/0x1b0 __pm_runtime_set_status+0x298/0x560 cdns_resume+0xb0/0x1c0 cdns3_controller_resume.isra.0+0x1e0/0x250 cdns3_plat_resume+0x28/0x40 References: - https://g
60 cdns_resume+0xb0/0x1c0 cdns3_controller_resume.isra.0+0x1e0/0x250 cdns3_plat_resume+0x28/0x40 References: - https://git.kernel.org/stable/c/c861a61be6d30538ebcf7fcab1d43f244e298840 - https://git.kernel.org/stable/c/bbc9c3652708108738009e096d608ece3cd9fa8a - https://git.kernel.org/stable/c/d3f372ec95b89776f72d5c9a475424e27734c223 - https://git.kernel.org/stable/c/2319b9c87fe243327285f2fefd7374ffd75a65fc
CVE ID: CVE-2023-53288 State: PUBLISHED Published: 2025-09-16T08:11:21.150Z Last Updated: 2025-09-16T08:11:21.150Z Vendors: Linux Products: Linux Description: 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 [ast] local_pci_probe+0xdc/0x180
/0x4d0 [drm_kms_helper] drm_client_register+0x169/0x240 [drm] ast_pci_probe+0x142/0x190 [ast] local_pci_probe+0xdc/0x180 work_for_cpu_fn+0x4e/0xa0 process_one_work+0x8b7/0x1540 worker_thread+0x70a/0xed0 kthread+0x29f/0x340 ret_from_fork+0x1f/0x30 References: - https://git.kernel.org/stable/c/5d580017bdb9b3e930b6009e467e5e1589f8ca8a - https://git.kernel.org/stable/c/5f2a12f64347f535c6ef55fa7eb36a2874d69b59 - https://git.kernel.org/stable/c/1369d0c586ad44f2d18fe2f4cbc5bcb24132fa71 - https://git.kernel.org/stable/c/917bef37cfaca07781c6fbaf6cd9404d27e64e6f - https://git.kernel.org/stable/c/8108a494639e56aea77e7196a1d6ea89792b9d4a - https://git.kernel.org/stable/c/2329cc7a101af1a844fbf706c0724c0b
org/stable/c/8108a494639e56aea77e7196a1d6ea89792b9d4a - https://git.kernel.org/stable/c/2329cc7a101af1a844fbf706c0724c0baea38365