Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
ogram Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/1491a01ef5a98149048b12e208f6ed8e86ad10b9 - https://git.kernel.org/stable/c/a7678a16c25b6ece1667ac681e3e783ff3de7a6f - https://git.kernel.org/stable/c/2fcffaaf529d5fe3fdc6c0ee65a6f266b74de782 - https://git.kernel.org/stable/c/b1e86f1ef8fa796f8935be392457639f3a907d91 - https://git.kernel.org/stable/c/582c1aeee0a9e73010cf1c4cef338709860deeb0
CVE ID: CVE-2024-38604 State: PUBLISHED Published: 2024-06-19T13:48:15.099Z Last Updated: 2025-05-04T09:15:06.734Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: block: refine the EOF check in blkdev_iomap_begin blkdev_iomap_begin rounds down the offset to the logical block size before stashing it in iomap->offset and checking that it still is inside the inode size. Check the i_size check to the raw pos value so that we don't try a zero size write if iter->pos is unaligned. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/910717920c8c3f9386277a44c44d448058
Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/910717920c8c3f9386277a44c44d448058a18084 - https://git.kernel.org/stable/c/72c54e063c32aeb38d43a2bd897821e6e5a1757d - https://git.kernel.org/stable/c/10b723bcba8986537a484aa94dbfc9093fd776a1 - https://git.kernel.org/stable/c/0c12028aec837f5a002009bbf68d179d506510e8
CVE ID: CVE-2024-38605 State: PUBLISHED Published: 2024-06-19T13:48:15.769Z Last Updated: 2025-05-04T09:15:07.886Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or n
the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep
s still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/d7ff29a429b56f04783152ad7bbd7233b740e434 - https://git.kernel.org/stable/c/e7e0ca200772bdb2fdc6d43d32d341e87a36f811 - https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e - h
/e7e0ca200772bdb2fdc6d43d32d341e87a36f811 - https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e - https://git.kernel.org/stable/c/e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92 - https://git.kernel.org/stable/c/c935e72139e6d523defd60fe875c01eb1f9ea5c5 - https://git.kernel.org/stable/c/6b8374ee2cabcf034faa34e69a855dc496a9ec12 - https://git.kernel.org/stable/c/39381fe7394e5eafac76e7e9367e7351138a29c1
CVE ID: CVE-2024-38606 State: PUBLISHED Published: 2024-06-19T13:48:16.428Z Last Updated: 2025-05-04T09:15:09.243Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: qat - validate slices count returned by FW The function adf_send_admin_tl_start() enables the telemetry (TL) feature on a QAT device by sending the ICP_QAT_FW_TL_START message to the firmware. This triggers the FW to start writing TL data to a DMA buffer in memory and returns an array containing the number of accelerators of each type (slices) supported by this HW. The pointer to this array is stored in the adf_tl_hw_data data structure called slice_cnt. The ar
supported by this HW. The pointer to this array is stored in the adf_tl_hw_data data structure called slice_cnt. The array slice_cnt is then used in the function tl_print_dev_data() to report in debugfs only statistics about the supported accelerators. An incorrect value of the elements in slice_cnt might lead to an out of bounds memory read. At the moment, there isn't an implementation of FW that returns a wrong value, but for robustness validate the slice count array returned by FW. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e57ed345e2e6043629fc74aa5be051415dcc4f77 - https://git.kernel.org/stable/c/9b284b915e2a
https://git.kernel.org/stable/c/e57ed345e2e6043629fc74aa5be051415dcc4f77 - https://git.kernel.org/stable/c/9b284b915e2a5e63ca133353f8c456eff4446f82 - https://git.kernel.org/stable/c/483fd65ce29317044d1d00757e3fd23503b6b04c
CVE ID: CVE-2024-38607 State: PUBLISHED Published: 2024-06-19T13:48:17.096Z Last Updated: 2025-05-04T09:15:10.577Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: macintosh/via-macii: Fix "BUG: sleeping function called from invalid context" The via-macii ADB driver calls request_irq() after disabling hard interrupts. But disabling interrupts isn't necessary here because the VIA shift register interrupt was masked during VIA1 initialization. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/e4ff8bcfb2841fe4e17e5901578b632adb89036d - https://git.kernel.org/sta
ent: References: - https://git.kernel.org/stable/c/e4ff8bcfb2841fe4e17e5901578b632adb89036d - https://git.kernel.org/stable/c/1e9c3f2caec548cfa7a65416ec4e6006e542f18e - https://git.kernel.org/stable/c/280619bbdeac186fb320fab3d61122d2a085def8 - https://git.kernel.org/stable/c/010d4cb19bb13f423e3e746b824f314a9bf3e9a9 - https://git.kernel.org/stable/c/787fb79efc15b3b86442ecf079b8148f173376d7 - https://git.kernel.org/stable/c/d43a8c7ec0841e0ff91a968770aeca83f0fd4c56 - https://git.kernel.org/stable/c/5900a88e897e6deb1bdce09ee34167a81c2da89d - https://git.kernel.org/stable/c/2907d409ce5946390f513976f0454888d37d1058 - https://git.kernel.org/stable/c/d301a71c76ee4c384b4e03cdc320a55f5cf1df05
CVE ID: CVE-2024-38608 State: PUBLISHED Published: 2024-06-19T13:56:10.614Z Last Updated: 2025-05-04T09:15:11.765Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix netif state handling mlx5e_suspend cleans resources only if netif_device_present() returns true. However, mlx5e_resume changes the state of netif, via mlx5e_nic_enable, only if reg_state == NETREG_REGISTERED. In the below case, the above leads to NULL-ptr Oops[1] and memory leaks: mlx5e_probe _mlx5e_resume mlx5e_attach_netdev mlx5e_nic_enable <-- netdev not reg, not calling netif_device_attach() register_netdev <-- failed for some reason. ERROR_FLOW: _ml
enable <-- netdev not reg, not calling netif_device_attach() register_netdev <-- failed for some reason. ERROR_FLOW: _mlx5e_suspend <-- netif_device_present return false, resources aren't freed :( Hence, clean resources in this case as well. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0010 [#1] SMP CPU: 2 PID: 9345 Comm: test-ovs-ct-gen Not tainted 6.5.0_for_upstream_min_debug_2023_09_05_16_01 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:0x0 Code: Unable to access opcode bytes at0xffffffffffffffd6. RSP: 0018:ffff888178aaf758 EFLAGS: 00010246 Call Trace: <TASK> ? __die+0x
e to access opcode bytes at0xffffffffffffffd6. RSP: 0018:ffff888178aaf758 EFLAGS: 00010246 Call Trace: <TASK> ? __die+0x20/0x60 ? page_fault_oops+0x14c/0x3c0 ? exc_page_fault+0x75/0x140 ? asm_exc_page_fault+0x22/0x30 notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] mlx5_core_uplink_netdev_event_replay+0x3e/0x60 [mlx5_core] mlx5_mdev_netdev_track+0x53/0x60 [mlx5_ib] mlx5_ib_roce_init+0xc3/0x340 [mlx5_ib] __mlx5_ib_add+0x34/0xd0 [mlx5_ib] mlx5r_probe+0xe1/0x210 [mlx5_ib] ? auxiliary_match_id+0x6a/0x90 auxiliary_bus_probe+0x38/0x80 ? driver_sysfs_add+0x51/0x80 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __dr
auxiliary_bus_probe+0x38/0x80 ? driver_sysfs_add+0x51/0x80 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x86/0xa0 device_add+0x637/0x840 __auxiliary_device_add+0x3b/0xa0 add_adev+0xc9/0x140 [mlx5_core] mlx5_rescan_drivers_locked+0x22a/0x310 [mlx5_core] mlx5_register_device+0x53/0xa0 [mlx5_core] mlx5_init_one_devl_locked+0x5c4/0x9c0 [mlx5_core] mlx5_init_one+0x3b/0x60 [mlx5_core] probe_one+0x44c/0x730 [mlx5_core] local_pci_probe+0x3e/0x90 pci_device_probe+0xbf/0x210 ? kernfs_create_link+0x5d/0xa0 ? sysfs_do_create_l
730 [mlx5_core] local_pci_probe+0x3e/0x90 pci_device_probe+0xbf/0x210 ? kernfs_create_link+0x5d/0xa0 ? sysfs_do_create_link_sd+0x60/0xc0 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 pci_bus_add_device+0x54/0x80 pci_iov_add_virtfn+0x2e6/0x320 sriov_enable+0x208/0x420 mlx5_core_sriov_configure+0x9e/0x200 [mlx5_core] sriov_numvfs_store+0xae/0x1a0 kernfs_fop_write_iter+0x10c/0x1a0 vfs_write+0x291/0x3c0 ksys_write+0x5f/0xe0 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 CR2: 0000000000000000 ---[ end trace 0000000000000
0xe0 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/f7e6cfb864a53af71c5cc904f1cc22215d68f5c6 - https://git.kernel.org/stable/c/3d5918477f94e4c2f064567875c475468e264644
CVE ID: CVE-2024-38609 State: PUBLISHED Published: 2024-06-19T13:56:11.416Z Last Updated: 2025-05-04T09:15:13.148Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: connac: check for null before dereferencing The wcid can be NULL. It should be checked for validity before dereferencing it to avoid crash. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/e469218765b2781fb968778bd13595acec181a0e - https://git.kernel.org/stable/c/cb47c7be0e93dd5acda078163799401ac3a78e10
CVE ID: CVE-2024-38610 State: PUBLISHED Published: 2024-06-19T13:56:12.083Z Last Updated: 2025-05-04T12:56:52.947Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map() Patch series "mm: follow_pte() improvements and acrn follow_pte() fixes". Patch #1 fixes a bunch of issues I spotted in the acrn driver. It compiles, that's all I know. I'll appreciate some review and testing from acrn folks. Patch #2+#3 improve follow_pte(), passing a VMA instead of the MM, adding more sanity checks, and improving the documentation. Gave it a quick test on x86-64 using VM_PAT that ends up u
, adding more sanity checks, and improving the documentation. Gave it a quick test on x86-64 using VM_PAT that ends up using follow_pte(). This patch (of 3): We currently miss handling various cases, resulting in a dangerous follow_pte() (previously follow_pfn()) usage. (1) We're not checking PTE write permissions. Maybe we should simply always require pte_write() like we do for pin_user_pages_fast(FOLL_WRITE)? Hard to tell, so let's check for ACRN_MEM_ACCESS_WRITE for now. (2) We're not rejecting refcounted pages. As we are not using MMU notifiers, messing with refcounted pages is dangerous and can result in use-after-free. Let's make sure to reject them. (3) We are only looking at the firs
pages is dangerous and can result in use-after-free. Let's make sure to reject them. (3) We are only looking at the first PTE of a bigger range. We only lookup a single PTE, but memmap->len may span a larger area. Let's loop over all involved PTEs and make sure the PFN range is actually contiguous. Reject everything else: it couldn't have worked either way, and rather made use access PFNs we shouldn't be accessing. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5c6705aa47b5b78d7ad36fea832bb69caa5bf49a - https://git.kernel.org/stable/c/afeb0e69627695f759fc73c39c1640dbf8649b32 - https://git.kernel.org/stable/c/e873f36ec
a - https://git.kernel.org/stable/c/afeb0e69627695f759fc73c39c1640dbf8649b32 - https://git.kernel.org/stable/c/e873f36ec890bece26ecce850e969917bceebbb6 - https://git.kernel.org/stable/c/4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4 - https://git.kernel.org/stable/c/2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb - https://git.kernel.org/stable/c/3d6586008f7b638f91f3332602592caa8b00b559
CVE ID: CVE-2024-38611 State: PUBLISHED Published: 2024-06-19T13:56:12.742Z Last Updated: 2025-11-03T19:30:17.590Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: i2c: et8ek8: Don't strip remove function when driver is builtin Using __exit for the remove function results in the remove callback being discarded with CONFIG_VIDEO_ET8EK8=y. When such a device gets unbound (e.g. using sysfs or hotplug), the driver is just removed without the cleanup being performed. This results in resource leaks. Fix it by compiling in the remove callback unconditionally. This also fixes a W=1 modpost warning: WARNING: modpost: drivers/media/
ompiling in the remove callback unconditionally. This also fixes a W=1 modpost warning: WARNING: modpost: drivers/media/i2c/et8ek8/et8ek8: section mismatch in reference: et8ek8_i2c_driver+0x10 (section: .data) -> et8ek8_remove (section: .exit.text) Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/963523600d9f1e36bc35ba774c2493d6baa4dd8f - https://git.kernel.org/stable/c/ece3fc1c10197052044048bea4f13cfdcf25b416 - https://git.kernel.org/stable/c/04d1086a62ac492ebb6bb0c94c1c8cb55f5d1f36 - https://git.kernel.org/stable/c/c1a3803e5bb91c13e9ad582003e4288f67f06cd9 - https://git.kernel.org/stable/c/43fff07e4b1956d0e5cf23717507e
el.org/stable/c/c1a3803e5bb91c13e9ad582003e4288f67f06cd9 - https://git.kernel.org/stable/c/43fff07e4b1956d0e5cf23717507e438278ea3d9 - https://git.kernel.org/stable/c/904db2ba44ae60641b6378c5013254d09acf5e80 - https://git.kernel.org/stable/c/545b215736c5c4b354e182d99c578a472ac9bfce
CVE ID: CVE-2024-38612 State: PUBLISHED Published: 2024-06-19T13:56:13.415Z Last Updated: 2025-11-04T17:21:46.235Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this e
possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/10610575a3ac2a702bf5c57aa931beaf847949c7 - https://git.kernel.org/stable/c/646cd236c55e2cb5f146fc41bbe4034c4af5b2a4 - https://git.kernel.org/stable/c/00e6335329f23ac6cf3105931691674e28bc598c - https://git.kernel.org/stable/c/1a63730fb315bb1bab97edd69ff58ad45e04bb01 - https://git.kernel.org/stable/c/e77a3ec7ada84543e75722a1283785a6544de925 - https://git.kernel.org/stable/c/3398a40dccb88d3a7eef378247a023a78472db66 - https://git.kernel.org/stable
785a6544de925 - https://git.kernel.org/stable/c/3398a40dccb88d3a7eef378247a023a78472db66 - https://git.kernel.org/stable/c/85a70ff1e572160f1eeb096ed48d09a1c9d4d89a - https://git.kernel.org/stable/c/c04d6a914e890ccea4a9d11233009a2ee7978bf4 - https://git.kernel.org/stable/c/160e9d2752181fcf18c662e74022d77d3164cd45
CVE ID: CVE-2024-38613 State: PUBLISHED Published: 2024-06-19T13:56:14.083Z Last Updated: 2025-05-04T09:15:18.601Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: m68k: Fix spinlock race in kernel thread creation Context switching does take care to retain the correct lock owner across the switch from 'prev' to 'next' tasks. This does rely on interrupts remaining disabled for the entire duration of the switch. This condition is guaranteed for normal process creation and context switching between already running processes, because both 'prev' and 'next' already have interrupts disabled in their saved copies of the status register.
processes, because both 'prev' and 'next' already have interrupts disabled in their saved copies of the status register. The situation is different for newly created kernel threads. The status register is set to PS_S in copy_thread(), which does leave the IPL at 0. Upon restoring the 'next' thread's status register in switch_to() aka resume(), interrupts then become enabled prematurely. resume() then returns via ret_from_kernel_thread() and schedule_tail() where run queue lock is released (see finish_task_switch() and finish_lock_switch()). A timer interrupt calling scheduler_tick() before the lock is released in finish_task_switch() will find the lock already taken, with the current task as
er_tick() before the lock is released in finish_task_switch() will find the lock already taken, with the current task as lock owner. This causes a spinlock recursion warning as reported by Guenter Roeck. As far as I can ascertain, this race has been opened in commit 533e6903bea0 ("m68k: split ret_from_fork(), simplify kernel_thread()") but I haven't done a detailed study of kernel history so it may well predate that commit. Interrupts cannot be disabled in the saved status register copy for kernel threads (init will complain about interrupts disabled when finally starting user space). Disable interrupts temporarily when switching the tasks' register sets in resume(). Note that a simple oriw
ser space). Disable interrupts temporarily when switching the tasks' register sets in resume(). Note that a simple oriw 0x700,%sr after restoring sr is not enough here - this leaves enough of a race for the 'spinlock recursion' warning to still be observed. Tested on ARAnyM and qemu (Quadra 800 emulation). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/2a8d1d95302c7d52c6ac8fa5cb4a6948ae0d3a14 - https://git.kernel.org/stable/c/5213cc01d0464c011fdc09f318705603ed3a746b - https://git.kernel.org/stable/c/4eeffecc8e3cce25bb559502c2fd94a948bcde82 - https://git.kernel.org/stable/c/77b2b67a0f8bce260c53907e5749d61466d90c87 - ht
4eeffecc8e3cce25bb559502c2fd94a948bcde82 - https://git.kernel.org/stable/c/77b2b67a0f8bce260c53907e5749d61466d90c87 - https://git.kernel.org/stable/c/0d9ae1253535f6e85a016e09c25ecbe6f7f59ef0 - https://git.kernel.org/stable/c/f3baf0f4f92af32943ebf27b960e0552c6c082fd - https://git.kernel.org/stable/c/f1d4274a84c069be0f6098ab10c3443fc1f7134c - https://git.kernel.org/stable/c/95f00caf767b5968c2c51083957b38be4748a78a - https://git.kernel.org/stable/c/da89ce46f02470ef08f0f580755d14d547da59ed
CVE ID: CVE-2024-38614 State: PUBLISHED Published: 2024-06-19T13:56:14.753Z Last Updated: 2025-05-04T09:15:19.930Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: openrisc: traps: Don't send signals to kernel mode threads OpenRISC exception handling sends signals to user processes on floating point exceptions and trap instructions (for debugging) among others. There is a bug where the trap handling logic may send signals to kernel threads, we should not send these signals to kernel threads, if that happens we treat it as an error. This patch adds conditions to die if the kernel receives these exceptions in kernel mode code. Addi
reat it as an error. This patch adds conditions to die if the kernel receives these exceptions in kernel mode code. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c0ed9a711e3392d73e857faa031d8d349c0d70db - https://git.kernel.org/stable/c/075c0405b0d7d9fc490609e988a3af0069596538 - https://git.kernel.org/stable/c/cea9d0015c140af39477dd5eeb9b20233a45daa9 - https://git.kernel.org/stable/c/c88cfb5cea5f8f9868ef02cc9ce9183a26dcf20f
CVE ID: CVE-2024-38615 State: PUBLISHED Published: 2024-06-19T13:56:15.422Z Last Updated: 2025-05-04T09:15:21.129Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit() callback is optional The exit() callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freq_table pointer even if the exit() callback isn't present. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/2d730b465e377396d2a09a53524b96b111f7ccb6 - https://git.kernel.org/stable/c/dfc56ff5ec9904c008e9376d90a6d7e2d2bec4d3 - https://git.kernel
d2a09a53524b96b111f7ccb6 - https://git.kernel.org/stable/c/dfc56ff5ec9904c008e9376d90a6d7e2d2bec4d3 - https://git.kernel.org/stable/c/35db5e76d5e9f752476df5fa0b9018a2398b0378 - https://git.kernel.org/stable/c/8bc9546805e572ad101681437a49939f28777273 - https://git.kernel.org/stable/c/3e99f060cfd2e36504d62c9132b453ade5027e1c - https://git.kernel.org/stable/c/ae37ebca325097d773d7bb6ec069123b30772872 - https://git.kernel.org/stable/c/a8204d1b6ff762d2171d365c2c8560285d0a233d - https://git.kernel.org/stable/c/b8f85833c05730d631576008daaa34096bc7f3ce
CVE ID: CVE-2024-38616 State: PUBLISHED Published: 2024-06-19T13:56:16.086Z Last Updated: 2025-05-04T09:15:22.437Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: re-fix fortified-memset warning The carl9170_tx_release() function sometimes triggers a fortified-memset warning in my randconfig builds: In file included from include/linux/string.h:254, from drivers/net/wireless/ath/carl9170/tx.c:40: In function 'fortify_memset_chk', inlined from 'carl9170_tx_release' at drivers/net/wireless/ath/carl9170/tx.c:283:2, inlined from 'kref_put' at include/linux/kref.h:65:3, inlined from 'carl9170_tx_put_skb' at drivers/net