Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
We extend the __ex_table (which is out of the execution path) by one 32-word. In this word we tell the compiler to insert the assembler instruction "or %r0,%r0,%reg", where %reg references the register which the compiler choosed for the error return code. In case of an access failure, the fault handler finds the __ex_table entry and can examine the opcode. The used register is encoded in the lowest 5 bits, and the fault handler can then store -EFAULT into this register. Since we extend the __ex_table to 3 words we can't use the BUILDTIME_TABLE_SORT config option any longer. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stabl
. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/23027309b099ffc4efca5477009a11dccbdae592 - https://git.kernel.org/stable/c/fa69a8063f8b27f3c7434a0d4f464a76a62f24d2 - https://git.kernel.org/stable/c/ce31d79aa1f13a2345791f84935281a2c194e003 - https://git.kernel.org/stable/c/8b1d72395635af45410b66cc4c4ab37a12c4a831
CVE ID: CVE-2024-26707 State: PUBLISHED Published: 2024-04-03T14:55:10.262Z Last Updated: 2025-05-04T08:54:31.739Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame() Syzkaller reported [1] hitting a warning after failing to allocate resources for skb in hsr_init_skb(). Since a WARN_ONCE() call will not help much in this case, it might be prudent to switch to netdev_warn_once(). At the very least it will suppress syzkaller reports such as [1]. Just in case, use netdev_warn_once() in send_prp_supervision_frame() for similar reasons. [1] HSR: Could not send supervision frame
e, use netdev_warn_once() in send_prp_supervision_frame() for similar reasons. [1] HSR: Could not send supervision frame WARNING: CPU: 1 PID: 85 at net/hsr/hsr_device.c:294 send_hsr_supervision_frame+0x60a/0x810 net/hsr/hsr_device.c:294 RIP: 0010:send_hsr_supervision_frame+0x60a/0x810 net/hsr/hsr_device.c:294 ... Call Trace: <IRQ> hsr_announce+0x114/0x370 net/hsr/hsr_device.c:382 call_timer_fn+0x193/0x590 kernel/time/timer.c:1700 expire_timers kernel/time/timer.c:1751 [inline] __run_timers+0x764/0xb20 kernel/time/timer.c:2022 run_timer_softirq+0x58/0xd0 kernel/time/timer.c:2035 __do_softirq+0x21a/0x8de kernel/softirq.c:553 invoke_softirq kernel/softirq.c:427 [inline] __irq_exit_rcu kernel/so
2035 __do_softirq+0x21a/0x8de kernel/softirq.c:553 invoke_softirq kernel/softirq.c:427 [inline] __irq_exit_rcu kernel/softirq.c:632 [inline] irq_exit_rcu+0xb7/0x120 kernel/softirq.c:644 sysvec_apic_timer_interrupt+0x95/0xb0 arch/x86/kernel/apic/apic.c:1076 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:649 ... This issue is also found in older kernels (at least up to 5.10). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0d8011a878fdf96123bc0d6a12e2fe7ced5fddfb - https://git.kernel.org/stable/c/de769423b2f053182a41317c4db5a927e90622a0 - https://git.kernel.org/stable/c/56440799fc
- https://git.kernel.org/stable/c/de769423b2f053182a41317c4db5a927e90622a0 - https://git.kernel.org/stable/c/56440799fc4621c279df16176f83a995d056023a - https://git.kernel.org/stable/c/923dea2a7ea9e1ef5ac4031fba461c1cc92e32b8 - https://git.kernel.org/stable/c/547545e50c913861219947ce490c68a1776b9b51 - https://git.kernel.org/stable/c/37e8c97e539015637cb920d3e6f1e404f707a06e
CVE ID: CVE-2024-26708 State: PUBLISHED Published: 2024-04-03T14:55:11.054Z Last Updated: 2025-05-04T08:54:33.265Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mptcp: really cope with fastopen race Fastopen and PM-trigger subflow shutdown can race, as reported by syzkaller. In my first attempt to close such race, I missed the fact that the subflow status can change again before the subflow_state_change callback is invoked. Address the issue additionally copying with all the states directly reachable from TCP_FIN_WAIT1. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel
_FIN_WAIT1. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/4bfe217e075d04e63c092df9d40c608e598c2ef2 - https://git.kernel.org/stable/c/e158fb9679d15a2317ec13b4f6301bd26265df2f - https://git.kernel.org/stable/c/337cebbd850f94147cee05252778f8f78b8c337f
CVE ID: CVE-2024-26709 State: PUBLISHED Published: 2024-04-03T14:55:11.868Z Last Updated: 2025-05-04T08:54:34.702Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/iommu: Fix the missing iommu_group_put() during platform domain attach The function spapr_tce_platform_iommu_attach_dev() is missing to call iommu_group_put() when the domain is already set. This refcount leak shows up with BUG_ON() during DLPAR remove operation as: KernelBug: Kernel bug in state 'None': kernel BUG at arch/powerpc/platforms/pseries/iommu.c:100! Oops: Exception in kernel mode, sig: 5 [#1] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=8192 NUMA pSeries
eries/iommu.c:100! Oops: Exception in kernel mode, sig: 5 [#1] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=8192 NUMA pSeries <snip> Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_016) hv:phyp pSeries NIP: c0000000000ff4d4 LR: c0000000000ff4cc CTR: 0000000000000000 REGS: c0000013aed5f840 TRAP: 0700 Tainted: G I (6.8.0-rc3-autotest-g99bd3cb0d12e) MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 44002402 XER: 20040000 CFAR: c000000000a0d170 IRQMASK: 0 ... NIP iommu_reconfig_notifier+0x94/0x200 LR iommu_reconfig_notifier+0x8c/0x200 Call Trace: iommu_reconfig_notifier+0x8c/0x200 (unreliable) notifier_call_chain+0xb8/0x19c blocking_notifier_call_chain+0x64/0x98 of
iommu_reconfig_notifier+0x8c/0x200 (unreliable) notifier_call_chain+0xb8/0x19c blocking_notifier_call_chain+0x64/0x98 of_reconfig_notify+0x44/0xdc of_detach_node+0x78/0xb0 ofdt_write.part.0+0x86c/0xbb8 proc_reg_write+0xf4/0x150 vfs_write+0xf8/0x488 ksys_write+0x84/0x140 system_call_exception+0x138/0x330 system_call_vectored_common+0x15c/0x2ec The patch adds the missing iommu_group_put() call. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c90fdea9cac9eb419fc266e75d625cb60c8f7f6c - https://git.kernel.org/stable/c/0846dd77c8349ec92ca0079c9c71d130f34cb192
CVE ID: CVE-2024-26710 State: PUBLISHED Published: 2024-04-03T14:55:12.583Z Last Updated: 2025-06-19T12:39:13.999Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/kasan: Limit KASAN thread size increase to 32KB KASAN is seen to increase stack usage, to the point that it was reported to lead to stack overflow on some 32-bit machines (see link). To avoid overflows the stack size was doubled for KASAN builds in commit 3e8635fb2e07 ("powerpc/kasan: Force thread size increase with KASAN"). However with a 32KB stack size to begin with, the doubling leads to a 64KB stack, which causes build errors: arch/powerpc/kernel/switch.S:
B stack size to begin with, the doubling leads to a 64KB stack, which causes build errors: arch/powerpc/kernel/switch.S:249: Error: operand out of range (0x000000000000fe50 is not between 0xffffffffffff8000 and 0x0000000000007fff) Although the asm could be reworked, in practice a 32KB stack seems sufficient even for KASAN builds - the additional usage seems to be in the 2-3KB range for a 64-bit KASAN build. So only increase the stack for KASAN if the stack size is < 32KB. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/4cc31fa07445879a13750cb061bb8c2654975fcb - https://git.kernel.org/stable/c/b29b16bd836a838b7690f80e37
ernel.org/stable/c/4cc31fa07445879a13750cb061bb8c2654975fcb - https://git.kernel.org/stable/c/b29b16bd836a838b7690f80e37f8376414c74cbe - https://git.kernel.org/stable/c/f1acb109505d983779bbb7e20a1ee6244d2b5736
CVE ID: CVE-2024-26711 State: PUBLISHED Published: 2024-04-03T14:55:13.488Z Last Updated: 2025-05-04T08:54:37.099Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad4130: zero-initialize clock init data The clk_init_data struct does not have all its members initialized, causing issues when trying to expose the internal clock on the CLK pin. Fix this by zero-initializing the clk_init_data struct. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0e0dab37750926d4fb0144edb1c1ea0612fea273 - https://git.kernel.org/stable/c/02876e2df02f8b17a593d77a0a7879
l.org/stable/c/0e0dab37750926d4fb0144edb1c1ea0612fea273 - https://git.kernel.org/stable/c/02876e2df02f8b17a593d77a0a7879a8109b27e1 - https://git.kernel.org/stable/c/a22b0a2be69a36511cb5b37d948b651ddf7debf3
CVE ID: CVE-2024-26712 State: PUBLISHED Published: 2024-04-03T14:55:14.149Z Last Updated: 2025-05-07T20:00:37.857Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/kasan: Fix addr error caused by page alignment In kasan_init_region, when k_start is not page aligned, at the begin of for loop, k_cur = k_start & PAGE_MASK is less than k_start, and then `va = block + k_cur - k_start` is less than block, the addr va is invalid, because the memory address space from va to block is not alloced by memblock_alloc, which will not be reserved by memblock_reserve later, it will be used by other places. As a result, memory overwriting
, which will not be reserved by memblock_reserve later, it will be used by other places. As a result, memory overwriting occurs. for example: int __init __weak kasan_init_region(void *start, size_t size) { [...] /* if say block(dcd97000) k_start(feef7400) k_end(feeff3fe) */ block = memblock_alloc(k_end - k_start, PAGE_SIZE); [...] for (k_cur = k_start & PAGE_MASK; k_cur < k_end; k_cur += PAGE_SIZE) { /* at the begin of for loop * block(dcd97000) va(dcd96c00) k_cur(feef7000) k_start(feef7400) * va(dcd96c00) is less than block(dcd97000), va is invalid */ void *va = block + k_cur - k_start; [...] } [...] } Therefore, page alignment is performed on k_start before memblock_alloc() to ensure the v
cur - k_start; [...] } [...] } Therefore, page alignment is performed on k_start before memblock_alloc() to ensure the validity of the VA address. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/230e89b5ad0a33f530a2a976b3e5e4385cb27882 - https://git.kernel.org/stable/c/2738e0aa2fb24a7ab9c878d912dc2b239738c6c6 - https://git.kernel.org/stable/c/0c09912dd8387e228afcc5e34ac5d79b1e3a1058 - https://git.kernel.org/stable/c/0516c06b19dc64807c10e01bb99b552bdf2d7dbe - https://git.kernel.org/stable/c/70ef2ba1f4286b2b73675aeb424b590c92d57b25 - https://git.kernel.org/stable/c/4a7aee96200ad281a5cc4cf5c7a2e2a49d2b97b0
CVE ID: CVE-2024-26713 State: REJECTED Published: 2024-04-03T14:55:14.857Z Last Updated: 2024-12-19T11:14:14.696Z Description: No description available.
CVE ID: CVE-2024-26714 State: PUBLISHED Published: 2024-04-03T14:55:15.662Z Last Updated: 2025-05-04T08:54:39.611Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: interconnect: qcom: sc8180x: Mark CO0 BCM keepalive The CO0 BCM needs to be up at all times, otherwise some hardware (like the UFS controller) loses its connection to the rest of the SoC, resulting in a hang of the platform, accompanied by a spectacular logspam. Mark it as keepalive to prevent such cases. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6616d3c4f8284a7b3ef978c916566bd240cea1c7 - h
ner: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6616d3c4f8284a7b3ef978c916566bd240cea1c7 - https://git.kernel.org/stable/c/d8e36ff40cf9dadb135f3a97341c02c9a7afcc43 - https://git.kernel.org/stable/c/7a3a70dd08e4b7dffc2f86f2c68fc3812804b9d0 - https://git.kernel.org/stable/c/85e985a4f46e462a37f1875cb74ed380e7c0c2e0
CVE ID: CVE-2024-26715 State: PUBLISHED Published: 2024-04-03T14:55:16.395Z Last Updated: 2025-05-04T12:54:35.041Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend In current scenario if Plug-out and Plug-In performed continuously there could be a chance while checking for dwc->gadget_driver in dwc3_gadget_suspend, a NULL pointer dereference may occur. Call Stack: CPU1: CPU2: gadget_unbind_driver dwc3_suspend_common dwc3_gadget_stop dwc3_gadget_suspend dwc3_disconnect_gadget CPU1 basically clears the variable and CPU2 checks the variable. Consider CPU1 is runn
et_suspend dwc3_disconnect_gadget CPU1 basically clears the variable and CPU2 checks the variable. Consider CPU1 is running and right before gadget_driver is cleared and in parallel CPU2 executes dwc3_gadget_suspend where it finds dwc->gadget_driver which is not NULL and resumes execution and then CPU1 completes execution. CPU2 executes dwc3_disconnect_gadget where it checks dwc->gadget_driver is already NULL because of which the NULL pointer deference occur. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/88936ceab6b426f1312327e9ef849c215c6007a7 - https://git.kernel.org/stable/c/57e2e42ccd3cd6183228269715ed032f4453675
ble/c/88936ceab6b426f1312327e9ef849c215c6007a7 - https://git.kernel.org/stable/c/57e2e42ccd3cd6183228269715ed032f44536751 - https://git.kernel.org/stable/c/c7ebd8149ee519d27232e6e4940e9c02071b568b - https://git.kernel.org/stable/c/36695d5eeeefe5a64b47d0336e7c8fc144e78182 - https://git.kernel.org/stable/c/61a348857e869432e6a920ad8ea9132e8d44c316
CVE ID: CVE-2024-26716 State: PUBLISHED Published: 2024-04-03T14:55:17.305Z Last Updated: 2025-05-04T08:54:41.873Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: core: Prevent null pointer dereference in update_port_device_state Currently, the function update_port_device_state gets the usb_hub from udev->parent by calling usb_hub_to_struct_hub. However, in case the actconfig or the maxchild is 0, the usb_hub would be NULL and upon further accessing to get port_dev would result in null pointer dereference. Fix this by introducing an if check after the usb_hub is populated. Additional Analyst Notes: - CISA ADP Vulnrichment:
Fix this by introducing an if check after the usb_hub is populated. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/ed85777c640cf9e6920bb1b60ed8cd48e1f4d873 - https://git.kernel.org/stable/c/465b545d1d7ef282192ddd4439b08279bdb13f6f - https://git.kernel.org/stable/c/12783c0b9e2c7915a50d5ec829630ff2da50472c
CVE ID: CVE-2024-26717 State: PUBLISHED Published: 2024-04-03T14:55:18.063Z Last Updated: 2025-05-04T08:54:43.023Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid-of: fix NULL-deref on failed power up A while back the I2C HID implementation was split in an ACPI and OF part, but the new OF driver never initialises the client pointer which is dereferenced on power-up failures. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/62f5d219edbd174829aa18d4b3d97cd5fefbb783 - https://git.kernel.org/stable/c/d7d7a0e3b6f5adc45f23667cbb919e99093a5b5c - https
5d219edbd174829aa18d4b3d97cd5fefbb783 - https://git.kernel.org/stable/c/d7d7a0e3b6f5adc45f23667cbb919e99093a5b5c - https://git.kernel.org/stable/c/4cad91344a62536a2949873bad6365fbb6232776 - https://git.kernel.org/stable/c/e28d6b63aeecbda450935fb58db0e682ea8212d3 - https://git.kernel.org/stable/c/00aab7dcb2267f2aef59447602f34501efe1a07f
CVE ID: CVE-2024-26718 State: PUBLISHED Published: 2024-04-03T14:55:18.756Z Last Updated: 2025-05-04T08:54:44.383Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dm-crypt, dm-verity: disable tasklets Tasklets have an inherent problem with memory corruption. The function tasklet_action_common calls tasklet_trylock, then it calls the tasklet callback and then it calls tasklet_unlock. If the tasklet callback frees the structure that contains the tasklet or if it calls some code that may free it, tasklet_unlock will write into free memory. The commits 8e14f610159d and d9a02e016aaf try to fix it for dm-crypt, but it is not a suffici
ll write into free memory. The commits 8e14f610159d and d9a02e016aaf try to fix it for dm-crypt, but it is not a sufficient fix and the data corruption can still happen [1]. There is no fix for dm-verity and dm-verity will write into free memory with every tasklet-processed bio. There will be atomic workqueues implemented in the kernel 6.9 [2]. They will have better interface and they will not suffer from the memory corruption problem. But we need something that stops the memory corruption now and that can be backported to the stable kernels. So, I'm proposing this commit that disables tasklets in both dm-crypt and dm-verity. This commit doesn't remove the tasklet support, because the taskle
hat disables tasklets in both dm-crypt and dm-verity. This commit doesn't remove the tasklet support, because the tasklet code will be reused when atomic workqueues will be implemented. [1] https://lore.kernel.org/all/d390d7ee-f142-44d3-822a-87949e14608b@suse.de/T/ [2] https://lore.kernel.org/lkml/20240130091300.2968534-1-tj@kernel.org/ Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b825e0f9d68c178072bffd32dd34c39e3d2d597a - https://git.kernel.org/stable/c/30884a44e0cedc3dfda8c22432f3ba4078ec2d94 - https://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc - https://git.kernel.org/stable/c/0c45a20cbe68bc
ttps://git.kernel.org/stable/c/5735a2671ffb70ea29ca83969fe01316ee2ed6fc - https://git.kernel.org/stable/c/0c45a20cbe68bc4d681734f5c03891124a274257 - https://git.kernel.org/stable/c/0a9bab391e336489169b95cb0d4553d921302189
CVE ID: CVE-2024-26719 State: PUBLISHED Published: 2024-04-03T14:55:19.556Z Last Updated: 2025-05-04T08:54:46.361Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nouveau: offload fence uevents work to workqueue This should break the deadlock between the fctx lock and the irq lock. This offloads the processing off the work from the irq into a workqueue. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/cc0037fa592d56e4abb9c7d1c52c4d2dc25cd906 - https://git.kernel.org/stable/c/985d053f7633d8b539ab1531738d538efac678a9 - https://git.kernel.org/stable/c/39126abc
06 - https://git.kernel.org/stable/c/985d053f7633d8b539ab1531738d538efac678a9 - https://git.kernel.org/stable/c/39126abc5e20611579602f03b66627d7cd1422f0
CVE ID: CVE-2024-26720 State: REJECTED Published: 2024-04-03T14:55:20.286Z Last Updated: 2024-12-19T11:15:27.766Z Description: No description available.
CVE ID: CVE-2024-26721 State: PUBLISHED Published: 2024-04-03T14:55:20.995Z Last Updated: 2025-05-04T08:54:47.727Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/i915/dsc: Fix the macro that calculates DSCC_/DSCA_ PPS reg address Commit bd077259d0a9 ("drm/i915/vdsc: Add function to read any PPS register") defines a new macro to calculate the DSC PPS register addresses with PPS number as an input. This macro correctly calculates the addresses till PPS 11 since the addresses increment by 4. So in that case the following macro works correctly to give correct register address: _MMIO(_DSCA_PPS_0 + (pps) * 4) However after PPS 11
he following macro works correctly to give correct register address: _MMIO(_DSCA_PPS_0 + (pps) * 4) However after PPS 11, the register address for PPS 12 increments by 12 because of RC Buffer memory allocation in between. Because of this discontinuity in the address space, the macro calculates wrong addresses for PPS 12 - 16 resulting into incorrect DSC PPS parameter value read/writes causing DSC corruption. This fixes it by correcting this macro to add the offset of 12 for PPS >=12. v3: Add correct paranthesis for pps argument (Jani Nikula) (cherry picked from commit 6074be620c31dc2ae11af96a1a5ea95580976fb5) Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: Referen
e620c31dc2ae11af96a1a5ea95580976fb5) Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/ff5999fb03f467e1e7159f0ddb199c787f7512b9 - https://git.kernel.org/stable/c/962ac2dce56bb3aad1f82a4bbe3ada57a020287c
CVE ID: CVE-2024-26722 State: PUBLISHED Published: 2024-04-03T14:55:21.709Z Last Updated: 2025-05-04T08:54:54.183Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work() There is a path in rt5645_jack_detect_work(), where rt5645->jd_mutex is left locked forever. That may lead to deadlock when rt5645_jack_detect_work() is called for the second time. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3dd2d99e2352903d0e0b8769e6c9b8293c7454b2 - https
- CVE Program Container: References: - https://git.kernel.org/stable/c/3dd2d99e2352903d0e0b8769e6c9b8293c7454b2 - https://git.kernel.org/stable/c/422d5243b9f780abd3d39da2b746e3915677b07d - https://git.kernel.org/stable/c/4a98bc739d0753a5810ce5630943cd7614c7717e - https://git.kernel.org/stable/c/d14b8e2005f36319df9412d42037416d64827f6b - https://git.kernel.org/stable/c/1f0d7792e9023e8658e901b7b76a555f6aa052ec - https://git.kernel.org/stable/c/050ad2ca0ac169dd9e552075d2c6af1bbb46534c - https://git.kernel.org/stable/c/ed5b8b735369b40d6c1f8ef3e62d369f74b4c491 - https://git.kernel.org/stable/c/6ef5d5b92f7117b324efaac72b3db27ae8bb3082
CVE ID: CVE-2024-26723 State: PUBLISHED Published: 2024-04-03T14:55:22.529Z Last Updated: 2025-05-04T08:54:55.658Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: lan966x: Fix crash when adding interface under a lag There is a crash when adding one of the lan966x interfaces under a lag interface. The issue can be reproduced like this: ip link add name bond0 type bond miimon 100 mode balance-xor ip link set dev eth0 master bond0 The reason is because when adding a interface under the lag it would go through all the ports and try to figure out which other ports are under that lag interface. And the issue is that lan966x can have p
the ports and try to figure out which other ports are under that lag interface. And the issue is that lan966x can have ports that are NULL pointer as they are not probed. So then iterating over these ports it would just crash as they are NULL pointers. The fix consists in actually checking for NULL pointers before accessing something from the ports. Like we do in other places. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/b9357489c46c7a43999964628db8b47d3a1f8672 - https://git.kernel.org/stable/c/48fae67d837488c87379f0c9f27df7391718477c - https://git.kernel.org/stable/c/2a492f01228b7d091dfe38974ef40dccf8f9f2f1 - https
ae67d837488c87379f0c9f27df7391718477c - https://git.kernel.org/stable/c/2a492f01228b7d091dfe38974ef40dccf8f9f2f1 - https://git.kernel.org/stable/c/15faa1f67ab405d47789d4702f587ec7df7ef03e