Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
rp_data_ready strp_read_sock read_sock -> tcp_read_sock strp_recv cb.rcv_msg -> sk_psock_strp_read # now stream_verdict return SK_PASS without peer sock assign __SK_PASS = sk_psock_map_verd(SK_PASS, NULL) sk_psock_verdict_apply sk_psock_skb_ingress_self sk_psock_skb_ingress_enqueue sk_psock_data_ready read_lock_bh(&sk->sk_callback_lock) <= dead lock ''' This topic has been discussed before, but it has not been fixed. Previous discussion: https://lore.kernel.org/all/6684a5864ec86_403d20898@john.notmuch Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/221109ba2127eabd0aa64718543638b58b15df56 - https://git.kernel.org/stable/c/6694f7acd625ed854bf63
git.kernel.org/stable/c/221109ba2127eabd0aa64718543638b58b15df56 - https://git.kernel.org/stable/c/6694f7acd625ed854bf6342926e771d65dad7f69 - https://git.kernel.org/stable/c/386efa339e08563dd33e83bc951aea5d407fe578 - https://git.kernel.org/stable/c/da2bc8a0c8f3ac66fdf980fc59936f851a083561 - https://git.kernel.org/stable/c/01f1b88acfd79103da0610b45471f6c88ea98d72 - https://git.kernel.org/stable/c/f84c5ef6ca23cc2f72f3b830d74f67944684bb05 - https://git.kernel.org/stable/c/8ca2a1eeadf09862190b2810697702d803ceef2d
CVE ID: CVE-2024-56695 State: PUBLISHED Published: 2024-12-28T09:46:19.468Z Last Updated: 2025-10-01T20:07:08.149Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Use dynamic allocation for CU occupancy array in 'kfd_get_cu_occupancy()' The `kfd_get_cu_occupancy` function previously declared a large `cu_occupancy` array as a local variable, which could lead to stack overflows due to excessive stack usage. This commit replaces the static array allocation with dynamic memory allocation using `kcalloc`, thereby reducing the stack size. This change avoids the risk of stack overflows in kernel space, in scenarios where `A
, thereby reducing the stack size. This change avoids the risk of stack overflows in kernel space, in scenarios where `AMDGPU_MAX_QUEUES` is large. The allocated memory is freed using `kfree` before the function returns to prevent memory leaks. Fixes the below with gcc W=1: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c: In function ‘kfd_get_cu_occupancy’: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:322:1: warning: the frame size of 1056 bytes is larger than 1024 bytes [-Wframe-larger-than=] 322 | } | ^ Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6d9f07196389f35a3afebcf1a12c1425725caddd - https://git.kernel.org/stable/c/922f0e00
s: - https://git.kernel.org/stable/c/6d9f07196389f35a3afebcf1a12c1425725caddd - https://git.kernel.org/stable/c/922f0e00017b09d9d47e3efac008c8b20ed546a0
CVE ID: CVE-2024-56696 State: PUBLISHED Published: 2024-12-28T09:46:20.094Z Last Updated: 2025-10-01T20:07:08.001Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix possible NULL dereference caused by kunit_kzalloc() kunit_kzalloc() may return a NULL pointer, dereferencing it without NULL check may lead to NULL dereference. Add NULL checks for all the kunit_kzalloc() in sound_kunit.c Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/f5486bf8abfe778b368d8fd1aa655dc01d0013ca - https://git.kernel.org/stable/c/8bfff486ecc79a72e9380e2d5e0ff234d5542d2f - https://git.kernel.o
8d8fd1aa655dc01d0013ca - https://git.kernel.org/stable/c/8bfff486ecc79a72e9380e2d5e0ff234d5542d2f - https://git.kernel.org/stable/c/9ad467a2b2716d4ed12f003b041aa6c776a13ff5
CVE ID: CVE-2024-56697 State: PUBLISHED Published: 2024-12-28T09:46:20.728Z Last Updated: 2025-10-01T20:07:07.847Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix the memory allocation issue in amdgpu_discovery_get_nps_info() Fix two issues with memory allocation in amdgpu_discovery_get_nps_info() for mem_ranges: - Add a check for allocation failure to avoid dereferencing a null pointer. - As suggested by Christophe, use kvcalloc() for memory allocation, which checks for multiplication overflow. Additionally, assign the output parameters nps_type and range_cnt after the kvcalloc() call to prevent modifying the ou
Additionally, assign the output parameters nps_type and range_cnt after the kvcalloc() call to prevent modifying the output parameters in case of an error return. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/d14bea4e094871226ea69772d69dab8b7b5f4915 - https://git.kernel.org/stable/c/e8f1dbaa0437eba4e8c1d6a6d81eca2e2ce3d197 - https://git.kernel.org/stable/c/a1144da794adedb9447437c57d69add56494309d
CVE ID: CVE-2024-56698 State: PUBLISHED Published: 2024-12-28T09:46:21.363Z Last Updated: 2025-11-03T20:52:46.763Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: Fix looping of queued SG entries The dwc3_request->num_queued_sgs is decremented on completion. If a partially completed request is handled, then the dwc3_request->num_queued_sgs no longer reflects the total number of num_queued_sgs (it would be cleared). Correctly check the number of request SG entries remained to be prepare and queued. Failure to do this may cause null pointer dereference when accessing non-existent SG entry. Additional Analyst Not
eued. Failure to do this may cause null pointer dereference when accessing non-existent SG entry. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8ceb21d76426bbe7072cc3e43281e70c0d664cc7 - https://git.kernel.org/stable/c/0247da93bf62d33304b7bf97850ebf2a86e06d28 - https://git.kernel.org/stable/c/c9e72352a10ae89a430449f7bfeb043e75c255d9 - https://git.kernel.org/stable/c/1534f6f69393aac773465d80d31801b554352627 - https://git.kernel.org/stable/c/b7c3d0b59213ebeedff63d128728ce0b3d7a51ec - https://git.kernel.org/stable/c/70777a23a54e359cfdfafc625a57cd56434f3859 - https://git.kernel.org/stable/c/b7fc65f5141c24785dc8c19249ca4e
l.org/stable/c/70777a23a54e359cfdfafc625a57cd56434f3859 - https://git.kernel.org/stable/c/b7fc65f5141c24785dc8c19249ca4efcf71b3524
CVE ID: CVE-2024-56699 State: PUBLISHED Published: 2024-12-28T09:46:22.034Z Last Updated: 2025-05-04T10:02:45.480Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/pci: Fix potential double remove of hotplug slot In commit 6ee600bfbe0f ("s390/pci: remove hotplug slot when releasing the device") the zpci_exit_slot() was moved from zpci_device_reserved() to zpci_release_device() with the intention of keeping the hotplug slot around until the device is actually removed. Now zpci_release_device() is only called once all references are dropped. Since the zPCI subsystem only drops its reference once the device is in the reserved s
once all references are dropped. Since the zPCI subsystem only drops its reference once the device is in the reserved state it follows that zpci_release_device() must only deal with devices in the reserved state. Despite that it contains code to tear down from both configured and standby state. For the standby case this already includes the removal of the hotplug slot so would cause a double removal if a device was ever removed in either configured or standby state. Instead of causing a potential double removal in a case that should never happen explicitly WARN_ON() if a device in non-reserved state is released and get rid of the dead code cases. References: - https://git.kernel.org/stable/
evice in non-reserved state is released and get rid of the dead code cases. References: - https://git.kernel.org/stable/c/c1489651071ab1be46d2af1da8adb15c9fc3c069 - https://git.kernel.org/stable/c/371bd905599d18da62d75e3974acbf6a41e315c7 - https://git.kernel.org/stable/c/c4a585e952ca403a370586d3f16e8331a7564901
CVE ID: CVE-2024-56700 State: PUBLISHED Published: 2024-12-28T09:46:22.770Z Last Updated: 2025-11-03T20:52:49.567Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: wl128x: Fix atomicity violation in fmc_send_cmd() Atomicity violation occurs when the fmc_send_cmd() function is executed simultaneously with the modification of the fmdev->resp_skb value. Consider a scenario where, after passing the validity check within the function, a non-null fmdev->resp_skb variable is assigned a null value. This results in an invalid fmdev->resp_skb variable passing the validity check. As seen in the later part of the function, skb = fmdev
n an invalid fmdev->resp_skb variable passing the validity check. As seen in the later part of the function, skb = fmdev->resp_skb; when the invalid fmdev->resp_skb passes the check, a null pointer dereference error may occur at line 478, evt_hdr = (void *)skb->data; To address this issue, it is recommended to include the validity check of fmdev->resp_skb within the locked section of the function. This modification ensures that the value of fmdev->resp_skb does not change during the validation process, thereby maintaining its validity. This possible bug is found by an experimental static analysis tool developed by our team. This tool analyzes the locking APIs to extract function pairs that c
imental static analysis tool developed by our team. This tool analyzes the locking APIs to extract function pairs that can be concurrently executed, and then analyzes the instructions in the paired functions to identify possible concurrency bugs including data races and atomicity violations. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/d16109c9fdc1b8cea4fe63b42e06e926c3f68990 - https://git.kernel.org/stable/c/3c818ad07e964bca3d27adac1e1f50e1e3c9180e - https://git.kernel.org/stable/c/d7408a052aa1b4f6fb6f1c7a8877b84017a07ac9 - https://git.kernel.org/stable/c/ed228b74d8a500380150965d5becabf9a1e33141 - https://git.kernel.org/stable/c/372dc95091
- https://git.kernel.org/stable/c/ed228b74d8a500380150965d5becabf9a1e33141 - https://git.kernel.org/stable/c/372dc9509122e5d45d4c12978e31c3c7d00aaca4 - https://git.kernel.org/stable/c/378ce4e08ca2b1ac7bbf1d57b68643ca4226c5f8 - https://git.kernel.org/stable/c/2e63c908de357048180516b84740ed62dac0b269 - https://git.kernel.org/stable/c/80a3b2ee01eecf22dfa06968b3cde92c691dea10 - https://git.kernel.org/stable/c/ca59f9956d4519ab18ab2270be47c6b8c6ced091
CVE ID: CVE-2024-56701 State: PUBLISHED Published: 2024-12-28T09:46:23.516Z Last Updated: 2025-11-03T20:52:50.956Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Fix dtl_access_lock to be a rw_semaphore The dtl_access_lock needs to be a rw_sempahore, a sleeping lock, because the code calls kmalloc() while holding it, which can sleep: # echo 1 > /proc/powerpc/vcpudispatch_stats BUG: sleeping function called from invalid context at include/linux/sched/mm.h:337 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 199, name: sh preempt_count: 1, expected: 0 3 locks held by sh/199: #0: c00000000a0743f8 (sb_writers
non_block: 0, pid: 199, name: sh preempt_count: 1, expected: 0 3 locks held by sh/199: #0: c00000000a0743f8 (sb_writers#3){.+.+}-{0:0}, at: vfs_write+0x324/0x438 #1: c0000000028c7058 (dtl_enable_mutex){+.+.}-{3:3}, at: vcpudispatch_stats_write+0xd4/0x5f4 #2: c0000000028c70b8 (dtl_access_lock){+.+.}-{2:2}, at: vcpudispatch_stats_write+0x220/0x5f4 CPU: 0 PID: 199 Comm: sh Not tainted 6.10.0-rc4 #152 Hardware name: IBM pSeries (emulated by qemu) POWER9 (raw) 0x4e1202 0xf000005 of:SLOF,HEAD hv:linux,kvm pSeries Call Trace: dump_stack_lvl+0x130/0x148 (unreliable) __might_resched+0x174/0x410 kmem_cache_alloc_noprof+0x340/0x3d0 alloc_dtl_buffers+0x124/0x1ac vcpudispatch_stats_write+0x2a8/0x5f4 pro
d+0x174/0x410 kmem_cache_alloc_noprof+0x340/0x3d0 alloc_dtl_buffers+0x124/0x1ac vcpudispatch_stats_write+0x2a8/0x5f4 proc_reg_write+0xf4/0x150 vfs_write+0xfc/0x438 ksys_write+0x88/0x148 system_call_exception+0x1c4/0x5a0 system_call_common+0xf4/0x258 Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/6956c0e7346ce1bbfc726755aa8da10d26e84276 - https://git.kernel.org/stable/c/f6ec133668757f84e5143f1eb141fd0b83778b9e - https://git.kernel.org/stable/c/fa5b5ea257135e771b489c83a2e93b5935d0108e - https://git.kernel.org/stable/c/a246daa26b717e755ccc9061f47f7cd1c0b358dd - https://git.kernel.org/stable/c/b125d0cf1adde7b2b47d7337fed7e9133eea3463 - https://gi
6b717e755ccc9061f47f7cd1c0b358dd - https://git.kernel.org/stable/c/b125d0cf1adde7b2b47d7337fed7e9133eea3463 - https://git.kernel.org/stable/c/525e18f1ba7c2b098c8ba587fb397efb34a6574c - https://git.kernel.org/stable/c/cadae3a45d23aa4f6485938a67cbc47aaaa25e38
CVE ID: CVE-2024-56702 State: PUBLISHED Published: 2024-12-28T09:46:24.244Z Last Updated: 2025-10-01T20:07:07.564Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bpf: Mark raw_tp arguments with PTR_MAYBE_NULL Arguments to a raw tracepoint are tagged as trusted, which carries the semantics that the pointer will be non-NULL. However, in certain cases, a raw tracepoint argument may end up being NULL. More context about this issue is available in [0]. Thus, there is a discrepancy between the reality, that raw_tp arguments can actually be NULL, and the verifier's knowledge, that they are never NULL, causing explicit NULL checks to b
rguments can actually be NULL, and the verifier's knowledge, that they are never NULL, causing explicit NULL checks to be deleted, and accesses to such pointers potentially crashing the kernel. To fix this, mark raw_tp arguments as PTR_MAYBE_NULL, and then special case the dereference and pointer arithmetic to permit it, and allow passing them into helpers/kfuncs; these exceptions are made for raw_tp programs only. Ensure that we don't do this when ref_obj_id > 0, as in that case this is an acquired object and doesn't need such adjustment. The reason we do mask_raw_tp_trusted_reg logic is because other will recheck in places whether the register is a trusted_reg, and then consider our regist
ed_reg logic is because other will recheck in places whether the register is a trusted_reg, and then consider our register as untrusted when detecting the presence of the PTR_MAYBE_NULL flag. To allow safe dereference, we enable PROBE_MEM marking when we see loads into trusted pointers with PTR_MAYBE_NULL. While trusted raw_tp arguments can also be passed into helpers or kfuncs where such broken assumption may cause issues, a future patch set will tackle their case separately, as PTR_TO_BTF_ID (without PTR_TRUSTED) can already be passed into helpers and causes similar problems. Thus, they are left alone for now. It is possible that these checks also permit passing non-raw_tp args that are tr
ems. Thus, they are left alone for now. It is possible that these checks also permit passing non-raw_tp args that are trusted PTR_TO_BTF_ID with null marking. In such a case, allowing dereference when pointer is NULL expands allowed behavior, so won't regress existing programs, and the case of passing these into helpers is the same as above and will be dealt with later. Also update the failure case in tp_btf_nullable selftest to capture the new behavior, as the verifier will no longer cause an error when directly dereference a raw tracepoint argument marked as __nullable. [0]: https://lore.kernel.org/bpf/ZrCZS6nisraEqehw@jlelli-thinkpadt14gen4.remote.csb Additional Analyst Notes: - CISA ADP
0]: https://lore.kernel.org/bpf/ZrCZS6nisraEqehw@jlelli-thinkpadt14gen4.remote.csb Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c9b91d2d54175f781ad2c361cb2ac2c0e29b14b6 - https://git.kernel.org/stable/c/3634d4a310820567fc634bf8f1ee2b91378773e8 - https://git.kernel.org/stable/c/cb4158ce8ec8a5bb528cc1693356a5eb8058094d
CVE ID: CVE-2024-56703 State: PUBLISHED Published: 2024-12-28T09:46:24.978Z Last Updated: 2025-11-03T20:52:52.353Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix soft lockups in fib6_select_path under high next hop churn Soft lockups have been observed on a cluster of Linux-based edge routers located in a highly dynamic environment. Using the `bird` service, these routers continuously update BGP-advertised routes due to frequently changing nexthop destinations, while also managing significant IPv6 traffic. The lockups occur during the traversal of the multipath circular linked-list in the `fib6_select_path` function,
affic. The lockups occur during the traversal of the multipath circular linked-list in the `fib6_select_path` function, particularly while iterating through the siblings in the list. The issue typically arises when the nodes of the linked list are unexpectedly deleted concurrently on a different core—indicated by their 'next' and 'previous' elements pointing back to the node itself and their reference count dropping to zero. This results in an infinite loop, leading to a soft lockup that triggers a system panic via the watchdog timer. Apply RCU primitives in the problematic code sections to resolve the issue. Where necessary, update the references to fib6_siblings to annotate or use the RCU
code sections to resolve the issue. Where necessary, update the references to fib6_siblings to annotate or use the RCU APIs. Include a test script that reproduces the issue. The script periodically updates the routing table while generating a heavy load of outgoing IPv6 traffic through multiple iperf3 clients. It consistently induces infinite soft lockups within a couple of minutes. Kernel log: 0 [ffffbd13003e8d30] machine_kexec at ffffffff8ceaf3eb 1 [ffffbd13003e8d90] __crash_kexec at ffffffff8d0120e3 2 [ffffbd13003e8e58] panic at ffffffff8cef65d4 3 [ffffbd13003e8ed8] watchdog_timer_fn at ffffffff8d05cb03 4 [ffffbd13003e8f08] __hrtimer_run_queues at ffffffff8cfec62f 5 [ffffbd13003e8f70] hr
chdog_timer_fn at ffffffff8d05cb03 4 [ffffbd13003e8f08] __hrtimer_run_queues at ffffffff8cfec62f 5 [ffffbd13003e8f70] hrtimer_interrupt at ffffffff8cfed756 6 [ffffbd13003e8fd0] __sysvec_apic_timer_interrupt at ffffffff8cea01af 7 [ffffbd13003e8ff0] sysvec_apic_timer_interrupt at ffffffff8df1b83d -- <IRQ stack> -- 8 [ffffbd13003d3708] asm_sysvec_apic_timer_interrupt at ffffffff8e000ecb [exception RIP: fib6_select_path+299] RIP: ffffffff8ddafe7b RSP: ffffbd13003d37b8 RFLAGS: 00000287 RAX: ffff975850b43600 RBX: ffff975850b40200 RCX: 0000000000000000 RDX: 000000003fffffff RSI: 0000000051d383e4 RDI: ffff975850b43618 RBP: ffffbd13003d3800 R8: 0000000000000000 R9: ffff975850b40200 R10: 0000000000000
000000051d383e4 RDI: ffff975850b43618 RBP: ffffbd13003d3800 R8: 0000000000000000 R9: ffff975850b40200 R10: 0000000000000000 R11: 0000000000000000 R12: ffffbd13003d3830 R13: ffff975850b436a8 R14: ffff975850b43600 R15: 0000000000000007 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 9 [ffffbd13003d3808] ip6_pol_route at ffffffff8ddb030c 10 [ffffbd13003d3888] ip6_pol_route_input at ffffffff8ddb068c 11 [ffffbd13003d3898] fib6_rule_lookup at ffffffff8ddf02b5 12 [ffffbd13003d3928] ip6_route_input at ffffffff8ddb0f47 13 [ffffbd13003d3a18] ip6_rcv_finish_core.constprop.0 at ffffffff8dd950d0 14 [ffffbd13003d3a30] ip6_list_rcv_finish.constprop.0 at ffffffff8dd96274 15 [ffffbd13003d3a98] ip6_sublist_rcv a
d950d0 14 [ffffbd13003d3a30] ip6_list_rcv_finish.constprop.0 at ffffffff8dd96274 15 [ffffbd13003d3a98] ip6_sublist_rcv at ffffffff8dd96474 16 [ffffbd13003d3af8] ipv6_list_rcv at ffffffff8dd96615 17 [ffffbd13003d3b60] __netif_receive_skb_list_core at ffffffff8dc16fec 18 [ffffbd13003d3be0] netif_receive_skb_list_internal at ffffffff8dc176b3 19 [ffffbd13003d3c50] napi_gro_receive at ffffffff8dc565b9 20 [ffffbd13003d3c80] ice_receive_skb at ffffffffc087e4f5 [ice] 21 [ffffbd13003d3c90] ice_clean_rx_irq at ffffffffc0881b80 [ice] 22 [ffffbd13003d3d20] ice_napi_poll at ffffffffc088232f [ice] 23 [ffffbd13003d3d80] __napi_poll at ffffffff8dc18000 24 [ffffbd13003d3db8] net_rx_action at ffffffff8dc18581
232f [ice] 23 [ffffbd13003d3d80] __napi_poll at ffffffff8dc18000 24 [ffffbd13003d3db8] net_rx_action at ffffffff8dc18581 25 [ffffbd13003d3e40] __do_softirq at ffffffff8df352e9 26 [ffffbd13003d3eb0] run_ksoftirqd at ffffffff8ceffe47 27 [ffffbd13003d3ec0] smpboot_thread_fn at ffffffff8cf36a30 28 [ffffbd13003d3ee8] kthread at ffffffff8cf2b39f 29 [ffffbd13003d3f28] ret_from_fork at ffffffff8ce5fa64 30 [ffffbd13003d3f50] ret_from_fork_asm at ffffffff8ce03cbb Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/d0ec61c9f3583b76aebdbb271f5c0d3fcccd48b2 - https://git.kernel.org/stable/c/52da02521ede55fb86546c3fffd9377b3261b91f - ht
d0ec61c9f3583b76aebdbb271f5c0d3fcccd48b2 - https://git.kernel.org/stable/c/52da02521ede55fb86546c3fffd9377b3261b91f - https://git.kernel.org/stable/c/11edcd026012ac18acee0f1514db3ed1b160fc6f - https://git.kernel.org/stable/c/34a949e7a0869dfa31a40416d2a56973fae1807b - https://git.kernel.org/stable/c/d9ccb18f83ea2bb654289b6ecf014fd267cc988b
CVE ID: CVE-2024-56704 State: PUBLISHED Published: 2024-12-28T09:46:25.766Z Last Updated: 2025-11-03T20:52:55.105Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: 9p/xen: fix release of IRQ Kernel logs indicate an IRQ was double-freed. Pass correct device ID during IRQ release. [Dominique: remove confusing variable reset to 0] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/692eb06703afc3e24d889d77e94a0e20229f6a4a - https://git.kernel.org/stable/c/d74b4b297097bd361b8a9abfde9b521ff464ea9c - https://git.kernel.org/stable/c/7f5a2ed5c1810661e6b03f5a4ebf17682cd
/stable/c/d74b4b297097bd361b8a9abfde9b521ff464ea9c - https://git.kernel.org/stable/c/7f5a2ed5c1810661e6b03f5a4ebf17682cdea850 - https://git.kernel.org/stable/c/4950408793b118cb8075bcee1f033b543fb719fa - https://git.kernel.org/stable/c/b9e26059664bd9ebc64a0e8f5216266fc9f84265 - https://git.kernel.org/stable/c/2bb3ee1bf237557daea1d58007d2e1d4a6502ccf - https://git.kernel.org/stable/c/d888f5f5d76b2722c267e6bdf51d445d60647b7b - https://git.kernel.org/stable/c/530bc9f03a102fac95b07cda513bfc16ff69e0ee - https://git.kernel.org/stable/c/e43c608f40c065b30964f0a806348062991b802d
CVE ID: CVE-2024-56705 State: PUBLISHED Published: 2024-12-28T09:46:26.548Z Last Updated: 2025-11-03T20:52:57.953Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: atomisp: Add check for rgby_data memory allocation failure In ia_css_3a_statistics_allocate(), there is no check on the allocation result of the rgby_data memory. If rgby_data is not successfully allocated, it may trigger the assert(host_stats->rgby_data) assertion in ia_css_s3a_hmem_decode(). Adding a check to fix this potential issue. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/51b8dc5163d2ff2bf04019f8bf7e3b
nal Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/51b8dc5163d2ff2bf04019f8bf7e3bd0e75bb654 - https://git.kernel.org/stable/c/0c24b82bc4d12c6a58ceacbf2598cd4df63abf9a - https://git.kernel.org/stable/c/4676e50444046b498555b849e6080a5c78cdda9b - https://git.kernel.org/stable/c/02a97d9d7ff605fa4a1f908d1bd3ad8573234b61 - https://git.kernel.org/stable/c/8066badaf7463194473fb4be19dbe50b11969aa0 - https://git.kernel.org/stable/c/74aa783682c4d78c69d87898e40c78df1fec204e - https://git.kernel.org/stable/c/0c25ab93f2878cab07d37ca5afd302283201e5af - https://git.kernel.org/stable/c/ed61c59139509f76d3592683c90dc3fdc6e23cd6