Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f4ce5d4a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000133 RAX: ffffffffffffffda RBX: 00007f4ce5135f80 RCX: 00007f4ce4f7def9 RDX: 0000000000000001 RSI: 0000000020005d40 RDI: 0000000000000006 RBP: 00007f4ce4ff0b76 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f4ce5135f80 R15: 00007ffd4cbc6d68 </TASK> Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.ke
cbc6d68 </TASK> Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/50067d8b3f48e4cd4c9e817d3e9a5b5ff3507ca7 - https://git.kernel.org/stable/c/c0add6ed2cf1c4733cd489efc61faeccd3433b41 - https://git.kernel.org/stable/c/531754952f5dfc4b141523088147071d6e6112c4 - https://git.kernel.org/stable/c/38e3fd0c4a2616052eb3c8f4e6f32d1ff47cd663 - https://git.kernel.org/stable/c/b40b027a0c0cc1cb9471a13f9730bb2fff12a15b - https://git.kernel.org/stable/c/4e3542f40f3a94efa59ea328e307c50601ed7065 - https://git.kernel.org/stable/c/f839c5cd348201fec440d987cbca9b979bdb4fa7 - https://git.kernel.org/stable/c/752e1924604254f1708f3e3700283a86ebdd3
table/c/f839c5cd348201fec440d987cbca9b979bdb4fa7 - https://git.kernel.org/stable/c/752e1924604254f1708f3e3700283a86ebdd325d - https://git.kernel.org/stable/c/92ceba94de6fb4cee2bf40b485979c342f44a492
CVE ID: CVE-2024-49953 State: PUBLISHED Published: 2024-10-21T18:02:08.381Z Last Updated: 2025-05-04T09:42:13.793Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice The km.state is not checked in driver's delayed work. When xfrm_state_check_expire() is called, the state can be reset to XFRM_STATE_EXPIRED, even if it is XFRM_STATE_DEAD already. This happens when xfrm state is deleted, but not freed yet. As __xfrm_state_delete() is called again in xfrm timer, the following crash occurs. To fix this issue, skip xfrm_state_check_expire() if km.state is not XFRM_STATE_V
frm timer, the following crash occurs. To fix this issue, skip xfrm_state_check_expire() if km.state is not XFRM_STATE_VALID. Oops: general protection fault, probably for non-canonical address 0xdead000000000108: 0000 [#1] SMP CPU: 5 UID: 0 PID: 7448 Comm: kworker/u102:2 Not tainted 6.11.0-rc2+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5e_ipsec: eth%d mlx5e_ipsec_handle_sw_limits [mlx5_core] RIP: 0010:__xfrm_state_delete+0x3d/0x1b0 Code: 0f 84 8b 01 00 00 48 89 fd c6 87 c8 00 00 00 05 48 8d bb 40 10 00 00 e8 11 04 1a 00 48 8b 95 b8 00 00 00 48 8b 85 c0 00 00 00 <48> 89 42 08 48 89 10 48 8b 55 10 48 b8 00
8d bb 40 10 00 00 e8 11 04 1a 00 48 8b 95 b8 00 00 00 48 8b 85 c0 00 00 00 <48> 89 42 08 48 89 10 48 8b 55 10 48 b8 00 01 00 00 00 00 ad de 48 RSP: 0018:ffff88885f945ec8 EFLAGS: 00010246 RAX: dead000000000122 RBX: ffffffff82afa940 RCX: 0000000000000036 RDX: dead000000000100 RSI: 0000000000000000 RDI: ffffffff82afb980 RBP: ffff888109a20340 R08: ffff88885f945ea0 R09: 0000000000000000 R10: 0000000000000000 R11: ffff88885f945ff8 R12: 0000000000000246 R13: ffff888109a20340 R14: ffff88885f95f420 R15: ffff88885f95f400 FS: 0000000000000000(0000) GS:ffff88885f940000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2163102430 CR3: 00000001128d6001 CR4: 00000000
0000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2163102430 CR3: 00000001128d6001 CR4: 0000000000370eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> ? die_addr+0x33/0x90 ? exc_general_protection+0x1a2/0x390 ? asm_exc_general_protection+0x22/0x30 ? __xfrm_state_delete+0x3d/0x1b0 ? __xfrm_state_delete+0x2f/0x1b0 xfrm_timer_handler+0x174/0x350 ? __xfrm_state_delete+0x1b0/0x1b0 __hrtimer_run_queues+0x121/0x270 hrtimer_run_softirq+0x88/0xd0 handle_softirqs+0xcc/0x270 do_softirq+0x3c/0x50 </IRQ> <TASK> __local_bh_enable_ip+0x47/0x50 mlx5e_ipsec_handle_sw_limits+0x7d/0x9
tirqs+0xcc/0x270 do_softirq+0x3c/0x50 </IRQ> <TASK> __local_bh_enable_ip+0x47/0x50 mlx5e_ipsec_handle_sw_limits+0x7d/0x90 [mlx5_core] process_one_work+0x137/0x2d0 worker_thread+0x28d/0x3a0 ? rescuer_thread+0x480/0x480 kthread+0xb8/0xe0 ? kthread_park+0x80/0x80 ret_from_fork+0x2d/0x50 ? kthread_park+0x80/0x80 ret_from_fork_asm+0x11/0x20 </TASK> Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/fab615ac9fcb8589222303099975d464d8857527 - https://git.kernel.org/stable/c/0b1672834634df9ac9cedf856db9fc36d92c50ef - https://git.kernel.org/stable/c/151e7dead1f5399a73c19c4b50307ea48aff1dc0 - https://git.kernel.org/stable/c/7b124695db40d5c9c5295a94ae928a8d
org/stable/c/151e7dead1f5399a73c19c4b50307ea48aff1dc0 - https://git.kernel.org/stable/c/7b124695db40d5c9c5295a94ae928a8d67a01c3d
CVE ID: CVE-2024-49954 State: PUBLISHED Published: 2024-10-21T18:02:09.064Z Last Updated: 2025-11-03T22:23:33.788Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_w
ce application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/bc9356513d56b688775497b7ac6f2b967f46a80c - https://git.kernel.org/stable/c/ea2cdf4da093d0482f0ef36ba971e2e0c7673425 - https://git.kernel.org/stable/c/e67534bd31d79952b50e791e92adf0b3e6c13b8c - https://git.kernel.org/stable/c/85a104aaef1f56623acc10ba4c42d5f046ba65b7 - https://git.kernel.org/stable/c/b83bef74c121a3311240fc4002d23486b85355e4 - https://git.kernel.org/stable/c/fe513c2ef0a172a58f158e2e70465c4317f0a9a2
CVE ID: CVE-2024-49955 State: PUBLISHED Published: 2024-10-21T18:02:09.707Z Last Updated: 2025-11-03T22:23:35.245Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be
this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/76fb2cbf01571926da8ecf6876cc8cb07d3f5183 - https://git.kernel.org/stable/c/c47843a831e0eae007ad7e848d208e675ba4c132 - https://git.kernel.org/stable/c/da964de4c18199e14b961b5b2e5e6570552a313c - https://git.kernel.org/stable/c/07b98400cb0285a6348188aa8c5ec6a2ae0551f7 - https://git.kernel.org/stable/c/ca1fb7942a287b40659cc79551a1de54a2c2e7d5 - https://git.kernel.org/stable/c/ce31847f109c3a5b2abdd19d7bcaafaacfde53de - h
/ca1fb7942a287b40659cc79551a1de54a2c2e7d5 - https://git.kernel.org/stable/c/ce31847f109c3a5b2abdd19d7bcaafaacfde53de - https://git.kernel.org/stable/c/ca26e8eed9c1c6651f51f7fa38fe444f8573cd1b - https://git.kernel.org/stable/c/9f469ef1c79dac7f9ac1518643a33703918f7e13 - https://git.kernel.org/stable/c/76959aff14a0012ad6b984ec7686d163deccdc16
CVE ID: CVE-2024-49956 State: PUBLISHED Published: 2024-10-21T18:02:10.385Z Last Updated: 2025-05-04T09:42:18.451Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: gfs2: fix double destroy_workqueue error When gfs2_fill_super() fails, destroy_workqueue() is called within gfs2_gl_hash_clear(), and the subsequent code path calls destroy_workqueue() on the same work queue again. This issue can be fixed by setting the work queue pointer to NULL after the first destroy_workqueue() call and checking for a NULL pointer before attempting to destroy the work queue again. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - htt
before attempting to destroy the work queue again. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a5336035728d77efd76306940d742a6f23debe68 - https://git.kernel.org/stable/c/6cb9df81a2c462b89d2f9611009ab43ae8717841
CVE ID: CVE-2024-49957 State: PUBLISHED Published: 2024-10-21T18:02:11.046Z Last Updated: 2025-11-03T22:23:36.709Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix null-ptr-deref when journal load failed. During the mounting process, if journal_reset() fails because of too short journal, then lead to jbd2_journal_load() fails with NULL j_sb_buffer. Subsequently, ocfs2_journal_shutdown() calls jbd2_journal_flush()->jbd2_cleanup_journal_tail()-> __jbd2_update_log_tail()->jbd2_journal_update_sb_log_tail() ->lock_buffer(journal->j_sb_buffer), resulting in a null-pointer dereference error. To resolve this issue, we should c
) ->lock_buffer(journal->j_sb_buffer), resulting in a null-pointer dereference error. To resolve this issue, we should check the JBD2_LOADED flag to ensure the journal was properly loaded. Additionally, use journal instead of osb->journal directly to simplify the code. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/fd89d92c1140cee8f59de336cb37fa65e359c123 - https://git.kernel.org/stable/c/703b2c7e0798d263154dc8593dc2345f75dc077f - https://git.kernel.org/stable/c/bf605ae98dab5c15c5b631d4d7f88898cb41b649 - https://git.kernel.org/stable/c/ff55291fb36779819211b596da703389135f5b05 - https://git.kernel.org/stable/c/82dfdd1e
49 - https://git.kernel.org/stable/c/ff55291fb36779819211b596da703389135f5b05 - https://git.kernel.org/stable/c/82dfdd1e31e774578f76ce6dc90c834f96403a0f - https://git.kernel.org/stable/c/86a89e75e9e4dfa768b97db466ad6bedf2e7ea5b - https://git.kernel.org/stable/c/f60e94a83db799bde625ac8671a5b4a6354e7120 - https://git.kernel.org/stable/c/387bf565cc03e2e8c720b8b4798efea4aacb6962 - https://git.kernel.org/stable/c/5784d9fcfd43bd853654bb80c87ef293b9e8e80a
CVE ID: CVE-2024-49958 State: PUBLISHED Published: 2024-10-21T18:02:11.702Z Last Updated: 2025-11-03T22:23:38.186Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 sh
t fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the "Next Free Rec:" had overshot the "Count:" in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul
sters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the ti
link workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree
ng corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5c9807c523b4fca81d3e8e864dabc8c806402121 - https://git.kernel.org/stable/c/74364cb578dcc0b6c9109519d19cbe5a56afac9a - https://git.kernel.org/stable/c/aac31d654a0a31cb0d2fa36ae694f4e164a52707 - https://git.kernel.org/stable/c/020f5c53c17f66c0a8f2d37dad27ace301b8d8a1 - https://git.kernel.org/stable/c/5c2072f02c0d75802ec28ec703b7d43a0dd008b5 - https://git.kernel.org/stable/c/637c00e06564a945e9d0edb3d78d362
.org/stable/c/5c2072f02c0d75802ec28ec703b7d43a0dd008b5 - https://git.kernel.org/stable/c/637c00e06564a945e9d0edb3d78d362d64935f9f - https://git.kernel.org/stable/c/9f9a8f3ac65b4147f1a7b6c05fad5192c0e3c3d9 - https://git.kernel.org/stable/c/96ce4c3537114d1698be635f5e36c62dc49df7a4 - https://git.kernel.org/stable/c/5ca60b86f57a4d9648f68418a725b3a7de2816b0
CVE ID: CVE-2024-49959 State: PUBLISHED Published: 2024-10-21T18:02:12.355Z Last Updated: 2025-11-03T22:23:39.640Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don't stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain: =======================================
ng_transaction is NULL (i.e., the tid is 0), we will get the following complain: ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace: <TASK> add_transaction_credits+0x5d1/0x5e0 start_this_handle+0x1ef/0x6a0 jbd2__journal_start+0x18
x251/0x2e0 Call Trace: <TASK> add_transaction_credits+0x5d1/0x5e0 start_this_handle+0x1ef/0x6a0 jbd2__journal_start+0x18b/0x340 ext4_dirty_inode+0x5d/0xb0 __mark_inode_dirty+0xe4/0x5d0 generic_update_time+0x60/0x70 [...] ============================================ So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways. Note that this fix relies on commit 6f6a6fda2945 ("jbd2: fix ocfs2 corrupt when updating journal superblock fails") to make jbd2_cleanup_journal_tail return the correct error code. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://gi
correct error code. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/801a35dfef6996f3d5eaa96a59caf00440d9165e - https://git.kernel.org/stable/c/d5dc65370a746750dbb2f03eabcf86b18db65f32 - https://git.kernel.org/stable/c/481e8f18a290e39e04ddb7feb2bb2a2cc3b213ed - https://git.kernel.org/stable/c/ec7f8337c98ad281020ad1f11ba492462d80737a - https://git.kernel.org/stable/c/70bae48377a2c4296fd3caf4caf8f11079111019 - https://git.kernel.org/stable/c/1c62dc0d82c62f0dc8fcdc4843208e522acccaf5 - https://git.kernel.org/stable/c/3ced0fe6c0eff032733ea8b38778b34707270138 - https://git.kernel.org/stable/c/c6bf043b210eac67d35a114e345c4e558
rg/stable/c/3ced0fe6c0eff032733ea8b38778b34707270138 - https://git.kernel.org/stable/c/c6bf043b210eac67d35a114e345c4e5585672913 - https://git.kernel.org/stable/c/f5cacdc6f2bb2a9bf214469dd7112b43dd2dd68a
CVE ID: CVE-2024-49960 State: PUBLISHED Published: 2024-10-21T18:02:13.119Z Last Updated: 2025-11-03T22:23:41.082Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ext4: fix timer use-after-free on failed mount Syzbot has found an ODEBUG bug in ext4_fill_super The del_timer_sync function cancels the s_err_report timer, which reminds about filesystem errors daily. We should guarantee the timer is no longer active before kfree(sbi). When filesystem mounting fails, the flow goes to failed_mount3, where an error occurs when ext4_stop_mmpd is called, causing a read I/O failure. This triggers the ext4_handle_error function that ultimat
urs when ext4_stop_mmpd is called, causing a read I/O failure. This triggers the ext4_handle_error function that ultimately re-arms the timer, leaving the s_err_report timer active before kfree(sbi) is called. Fix the issue by canceling the s_err_report timer after calling ext4_stop_mmpd. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7aac0c17a8cdf4a3236991c1e60435c6a984076c - https://git.kernel.org/stable/c/22e9b83f0f33bc5a7a3181769d1dccbf021f5b04 - https://git.kernel.org/stable/c/cf3196e5e2f36cd80dab91ffae402e13935724bc - https://git.kernel.org/stable/c/9203817ba46ebba7c865c8de2aba399537b6e891 - https://git.kernel.o
ab91ffae402e13935724bc - https://git.kernel.org/stable/c/9203817ba46ebba7c865c8de2aba399537b6e891 - https://git.kernel.org/stable/c/fa78fb51d396f4f2f80f8e96a3b1516f394258be - https://git.kernel.org/stable/c/b85569585d0154d4db1e4f9e3e6a4731d407feb0 - https://git.kernel.org/stable/c/0ce160c5bdb67081a62293028dc85758a8efb22a
CVE ID: CVE-2024-49961 State: PUBLISHED Published: 2024-10-21T18:02:13.772Z Last Updated: 2025-11-03T22:23:42.541Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: i2c: ar0521: Use cansleep version of gpiod_set_value() If we use GPIO reset from I2C port expander, we must use *_cansleep() variant of GPIO functions. This was not done in ar0521_power_on()/ar0521_power_off() functions. Let's fix that. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 11 at drivers/gpio/gpiolib.c:3496 gpiod_set_value+0x74/0x7c Modules linked in: CPU: 0 PID: 11 Comm: kworker/u16:0 Not tainted 6.10.0 #53 Hardware name: Diasom DS-RK3568-SO
x74/0x7c Modules linked in: CPU: 0 PID: 11 Comm: kworker/u16:0 Not tainted 6.10.0 #53 Hardware name: Diasom DS-RK3568-SOM-EVB (DT) Workqueue: events_unbound deferred_probe_work_func pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : gpiod_set_value+0x74/0x7c lr : ar0521_power_on+0xcc/0x290 sp : ffffff8001d7ab70 x29: ffffff8001d7ab70 x28: ffffff80027dcc90 x27: ffffff8003c82000 x26: ffffff8003ca9250 x25: ffffffc080a39c60 x24: ffffff8003ca9088 x23: ffffff8002402720 x22: ffffff8003ca9080 x21: ffffff8003ca9088 x20: 0000000000000000 x19: ffffff8001eb2a00 x18: ffffff80efeeac80 x17: 756d2d6332692f30 x16: 0000000000000000 x15: 0000000000000000 x14: ffffff8001d91d40 x13: 000000000000
ffff80efeeac80 x17: 756d2d6332692f30 x16: 0000000000000000 x15: 0000000000000000 x14: ffffff8001d91d40 x13: 0000000000000016 x12: ffffffc080e98930 x11: ffffff8001eb2880 x10: 0000000000000890 x9 : ffffff8001d7a9f0 x8 : ffffff8001d92570 x7 : ffffff80efeeac80 x6 : 000000003fc6e780 x5 : ffffff8001d91c80 x4 : 0000000000000002 x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000001 Call trace: gpiod_set_value+0x74/0x7c ar0521_power_on+0xcc/0x290 ... Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/9f08876d766755a92f1b9543ae3ee21bfc596fb8 - https://git.kernel.org/stable/c/625a77b68c96349c16fcc1f
t.kernel.org/stable/c/9f08876d766755a92f1b9543ae3ee21bfc596fb8 - https://git.kernel.org/stable/c/625a77b68c96349c16fcc1faa42784313e0b1a85 - https://git.kernel.org/stable/c/2423b60a2d6d27e5f66c5021b494463aef2db212 - https://git.kernel.org/stable/c/3cf00ecfbf11ee8e6afff306a5bdcff4bf95d2cf - https://git.kernel.org/stable/c/bee1aed819a8cda47927436685d216906ed17f62
CVE ID: CVE-2024-49962 State: PUBLISHED Published: 2024-10-21T18:02:14.418Z Last Updated: 2025-11-03T22:23:44.027Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package() ACPICA commit 4d4547cf13cca820ff7e0f859ba83e1a610b9fd0 ACPI_ALLOCATE_ZEROED() may fail, elements might be NULL and will cause NULL pointer dereference later. [ rjw: Subject and changelog edits ] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/4669da66ebc5b09881487f30669b0fcdb462188e - https://git.kernel.org/stable
: References: - https://git.kernel.org/stable/c/4669da66ebc5b09881487f30669b0fcdb462188e - https://git.kernel.org/stable/c/402b4c6b7500c7cca6972d2456a4a422801035b5 - https://git.kernel.org/stable/c/cbb67e245dacd02b5e1d82733892647df1523982 - https://git.kernel.org/stable/c/1c9b8775062f8d854a80caf186af57fc617d454c - https://git.kernel.org/stable/c/f282db38953ad71dd4f3f8877a4e1d37e580e30a - https://git.kernel.org/stable/c/4588ea78d3904bebb613b0bb025669e75800f546 - https://git.kernel.org/stable/c/a907c113a8b66972f15f084d7dff960207b1f71d - https://git.kernel.org/stable/c/ae5d4c7e76ba393d20366dfea1f39f24560ffb1d - https://git.kernel.org/stable/c/a5242874488eba2b9062985bf13743c029821330
CVE ID: CVE-2024-49963 State: PUBLISHED Published: 2024-10-21T18:02:15.091Z Last Updated: 2025-11-03T22:23:45.557Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mailbox: bcm2835: Fix timeout during suspend mode During noirq suspend phase the Raspberry Pi power driver suffer of firmware property timeouts. The reason is that the IRQ of the underlying BCM2835 mailbox is disabled and rpi_firmware_property_list() will always run into a timeout [1]. Since the VideoCore side isn't consider as a wakeup source, set the IRQF_NO_SUSPEND flag for the mailbox IRQ in order to keep it enabled during suspend-resume cycle. [1] PM: late suspend