Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
78bc47beb3b6dff45624304 - https://git.kernel.org/stable/c/aa2d3d678895c8eedd003f1473f87d3f06fe6ec7 - https://git.kernel.org/stable/c/81bdd60a3d1d3b05e6cc6674845afb1694dd3a0e
CVE ID: CVE-2024-38569 State: PUBLISHED Published: 2024-06-19T13:35:35.588Z Last Updated: 2025-05-04T09:14:19.091Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi_pcie: Fix out-of-bound access when valid event group The perf tool allows users to create event groups through following cmd [1], but the driver does not check whether the array index is out of bounds when writing data to the event_group array. If the number of events in an event_group is greater than HISI_PCIE_MAX_COUNTERS, the memory write overflow of event_group array occurs. Add array index check to fix the possible array out of bounds violation,
ory write overflow of event_group array occurs. Add array index check to fix the possible array out of bounds violation, and return directly when write new events are written to array bounds. There are 9 different events in an event_group. [1] perf stat -e '{pmu/event1/, ... ,pmu/event9/}' Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3d1face00ebb7996842aee4214d7d0fb0c77b1e9 - https://git.kernel.org/stable/c/8e9aab2492178f25372f1820bfd9289fbd74efd0 - https://git.kernel.org/stable/c/567d34626c22b36579ec0abfdf5eda2949044220 - https://git.kernel.org/stable/c/ff48247144d13a3a0817127703724256008efa78 - https://git.kernel.
9ec0abfdf5eda2949044220 - https://git.kernel.org/stable/c/ff48247144d13a3a0817127703724256008efa78 - https://git.kernel.org/stable/c/77fce82678ea5fd51442e62febec2004f79e041b
CVE ID: CVE-2024-38570 State: PUBLISHED Published: 2024-06-19T13:35:36.274Z Last Updated: 2025-05-04T09:14:20.334Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix potential glock use-after-free on unmount When a DLM lockspace is released and there ares still locks in that lockspace, DLM will unlock those locks automatically. Commit fb6791d100d1b started exploiting this behavior to speed up filesystem unmount: gfs2 would simply free glocks it didn't want to unlock and then release the lockspace. This didn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until unt
idn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until until a lock is unlocked or its lockspace is released. To prevent those callbacks from accessing deallocated objects, put the glocks that should not be unlocked on the sd_dead_glocks list, release the lockspace, and only then free those glocks. As an additional measure, ignore unexpected ast and bast callbacks if the receiving glock is dead. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0636b34b44589b142700ac137b5f69802cfe2e37 - https://git.kernel.org/stable/c/e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0 -
/c/0636b34b44589b142700ac137b5f69802cfe2e37 - https://git.kernel.org/stable/c/e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0 - https://git.kernel.org/stable/c/501cd8fabf621d10bd4893e37f6ce6c20523c8ca - https://git.kernel.org/stable/c/d98779e687726d8f8860f1c54b5687eec5f63a73
CVE ID: CVE-2024-38571 State: PUBLISHED Published: 2024-06-19T13:35:36.981Z Last Updated: 2025-05-04T09:14:21.937Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: thermal/drivers/tsens: Fix null pointer dereference compute_intercept_slope() is called from calibrate_8960() (in tsens-8960.c) as compute_intercept_slope(priv, p1, NULL, ONE_PT_CALIB) which lead to null pointer dereference (if DEBUG or DYNAMIC_DEBUG set). Fix this bug by adding null pointer check. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kerne
with SVACE. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/27600e0c5272a262b0903e35ae1df37d33c5c1ad - https://git.kernel.org/stable/c/11c731386ed82053c2759b6fea1a82ae946e5e0f - https://git.kernel.org/stable/c/2d5ca6e4a2872e92a32fdfd87e04dd7d3ced7278 - https://git.kernel.org/stable/c/06d17744b77bc6cb29a6c785f4fad8c4163ee653 - https://git.kernel.org/stable/c/fcf5f1b5f308f2eb422f6aca55d295b25890906b - https://git.kernel.org/stable/c/d998ddc86a27c92140b9f7984ff41e3d1d07a48f
CVE ID: CVE-2024-38572 State: PUBLISHED Published: 2024-06-19T13:35:37.666Z Last Updated: 2025-05-04T09:14:23.115Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix out-of-bound access of qmi_invoke_handler() Currently, there is no terminator entry for ath12k_qmi_msg_handlers hence facing below KASAN warning, ================================================================== BUG: KASAN: global-out-of-bounds in qmi_invoke_handler+0xa4/0x148 Read of size 8 at addr ffffffd00a6428d8 by task kworker/u8:2/1273 CPU: 0 PID: 1273 Comm: kworker/u8:2 Not tainted 5.4.213 #0 Workqueue: qmi_msg_handler qmi_data_ready_work Call
u8:2/1273 CPU: 0 PID: 1273 Comm: kworker/u8:2 Not tainted 5.4.213 #0 Workqueue: qmi_msg_handler qmi_data_ready_work Call trace: dump_backtrace+0x0/0x20c show_stack+0x14/0x1c dump_stack+0xe0/0x138 print_address_description.isra.5+0x30/0x330 __kasan_report+0x16c/0x1bc kasan_report+0xc/0x14 __asan_load8+0xa8/0xb0 qmi_invoke_handler+0xa4/0x148 qmi_handle_message+0x18c/0x1bc qmi_data_ready_work+0x4ec/0x528 process_one_work+0x2c0/0x440 worker_thread+0x324/0x4b8 kthread+0x210/0x228 ret_from_fork+0x10/0x18 The address belongs to the variable: ath12k_mac_mon_status_filter_default+0x4bd8/0xfffffffffffe2300 [ath12k] [...] ================================================================== Add a dummy te
4bd8/0xfffffffffffe2300 [ath12k] [...] ================================================================== Add a dummy terminator entry at the end to assist the qmi_invoke_handler() in traversing up to the terminator entry without accessing an out-of-boundary index. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1 Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/95575de7dede7b1ed3b9718dab9dda97914ea775 - https://git.kernel.org/stable/c/b48d40f5840c505b7af700594aa8379eec28e925 - https://git.kernel.org/stable/c/a1abdb63628b04855a929850772de97435ed1555 - https://git.kernel.org/stable/c/e1bdff48a1bb4a4a
ps://git.kernel.org/stable/c/a1abdb63628b04855a929850772de97435ed1555 - https://git.kernel.org/stable/c/e1bdff48a1bb4a4ac660c19c55a820968c48b3f2
CVE ID: CVE-2024-38573 State: PUBLISHED Published: 2024-06-19T13:35:38.334Z Last Updated: 2025-05-04T09:14:24.803Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cppc_cpufreq: Fix possible null pointer dereference cppc_cpufreq_get_rate() and hisi_cppc_cpufreq_get_rate() can be called from different places with various parameters. So cpufreq_cpu_get() can return null as 'policy' in some circumstances. Fix this bug by adding null return check. 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/9
itional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/9a185cc5a79ba408e1c73375706630662304f618 - https://git.kernel.org/stable/c/769c4f355b7962895205b86ad35617873feef9a5 - https://git.kernel.org/stable/c/f84b9b25d045e67a7eee5e73f21278c8ab06713c - https://git.kernel.org/stable/c/b18daa4ec727c0266de5bfc78e818d168cc4aedf - https://git.kernel.org/stable/c/dfec15222529d22b15e5b0d63572a9e39570cab4 - https://git.kernel.org/stable/c/cf7de25878a1f4508c69dc9f6819c21ba177dbfe
CVE ID: CVE-2024-38574 State: PUBLISHED Published: 2024-06-19T13:35:39.015Z Last Updated: 2025-05-04T09:14:25.968Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: libbpf: Prevent null-pointer dereference when prog to load has no BTF In bpf_objec_load_prog(), there's no guarantee that obj->btf is non-NULL when passing it to btf__fd(), and this function does not perform any check before dereferencing its argument (as bpf_object__btf_fd() used to do). As a consequence, we get segmentation fault errors in bpftool (for example) when trying to load programs that come without BTF information. v2: Keep btf__fd() in the fix instead of re
for example) when trying to load programs that come without BTF information. v2: Keep btf__fd() in the fix instead of reverting to bpf_object__btf_fd(). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/ef80b59acfa4dee4b5eaccb15572b69248831104 - https://git.kernel.org/stable/c/1fd91360a75833b7110af9834ae26c977e1273e0 - https://git.kernel.org/stable/c/9bf48fa19a4b1d186e08b20bf7e5de26a15644fb
CVE ID: CVE-2024-38575 State: PUBLISHED Published: 2024-06-19T13:37:34.476Z Last Updated: 2025-05-04T12:56:47.063Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: pcie: handle randbuf allocation failure The kzalloc() in brcmf_pcie_download_fw_nvram() will return null if the physical memory has run out. As a result, if we use get_random_bytes() to generate random bytes in the randbuf, the null pointer dereference bug will happen. In order to prevent allocation failure, this patch adds a separate function using buffer on kernel stack to generate random bytes in the randbuf, which could prevent the kernel stack from
function using buffer on kernel stack to generate random bytes in the randbuf, which could prevent the kernel stack from overflow. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/0eb2c0528e232b3c32cde9d5e1c9f80ba2996e49 - https://git.kernel.org/stable/c/c37466406f075476c2702ecc01917928af871f3b - https://git.kernel.org/stable/c/7c15eb344b0d4d3468c9b2a7591ad2b859b29b88 - https://git.kernel.org/stable/c/3729ca9e48d19a03ae049e2bde510e161c2f3720 - https://git.kernel.org/stable/c/316f790ebcf94bdf59f794b7cdea4068dc676d4c
CVE ID: CVE-2024-38576 State: PUBLISHED Published: 2024-06-19T13:37:35.142Z Last Updated: 2025-05-04T09:14:28.625Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: rcu: Fix buffer overflow in print_cpu_stall_info() The rcuc-starvation output from print_cpu_stall_info() might overflow the buffer if there is a huge difference in jiffies difference. The situation might seem improbable, but computers sometimes get very confused about time, which can result in full-sized integers, and, in this case, buffer overflow. Also, the unsigned jiffies difference is printed using %ld, which is normally for signed integers. This is intentional f
Also, the unsigned jiffies difference is printed using %ld, which is normally for signed integers. This is intentional for debugging purposes, but it is not obvious from the code. This commit therefore changes sprintf() to snprintf() and adds a clarifying comment about intention of %ld format. 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/e2228ed3fe7aa838fba87c79a76fb1ad9ea47138 - https://git.kernel.org/stable/c/afb39909bfb5c08111f99e21bf5be7505f59ff1c - https://git.kernel.org/stable/c/9351e1338539cb7f319ffc1210fa9b2aa27384b5 - https://git.kernel.org/s
21bf5be7505f59ff1c - https://git.kernel.org/stable/c/9351e1338539cb7f319ffc1210fa9b2aa27384b5 - https://git.kernel.org/stable/c/4c3e2ef4d8ddd313c8ce3ac30505940bea8d6257 - https://git.kernel.org/stable/c/3758f7d9917bd7ef0482c4184c0ad673b4c4e069
CVE ID: CVE-2024-38577 State: PUBLISHED Published: 2024-06-19T13:37:35.797Z Last Updated: 2025-11-03T21:55:49.034Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow There is a possibility of buffer overflow in show_rcu_tasks_trace_gp_kthread() if counters, passed to sprintf() are huge. Counter numbers, needed for this are unrealistically high, but buffer overflow is still possible. Use snprintf() with buffer size instead of sprintf(). Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrich
erification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/17c43211d45f13d1badea3942b76bf16bcc49281 - https://git.kernel.org/stable/c/af7b560c88fb420099e29890aa682b8a3efc8784 - https://git.kernel.org/stable/c/08186d0c5fb64a1cc4b43e009314ee6b173ed222 - https://git.kernel.org/stable/c/32d988f48ed287e676a29a15ac30701c35849aec - https://git.kernel.org/stable/c/6593d857ce5b5b802fb73d8091ac9c84b92c1697 - https://git.kernel.org/stable/c/1a240e138071b25944ded0f5b3e357aa99fabcb7 - https://git.kernel.org/stable/c/cc5645fddb0ce28492b15520306d092730dffa48
CVE ID: CVE-2024-38578 State: PUBLISHED Published: 2024-06-19T13:37:36.487Z Last Updated: 2025-11-04T17:21:32.595Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ecryptfs: Fix buffer size for tag 66 packet The 'TAG 66 Packet Format' description is missing the cipher code and checksum fields that are packed into the message packet. As a result, the buffer allocated for the packet is 3 bytes too small and write_tag_66_packet() will write up to 3 bytes past the end of the buffer. Fix this by increasing the size of the allocation so the whole packet will always fit in the buffer. This fixes the below kasan slab-out-of-bounds bug: B
f the allocation so the whole packet will always fit in the buffer. This fixes the below kasan slab-out-of-bounds bug: BUG: KASAN: slab-out-of-bounds in ecryptfs_generate_key_packet_set+0x7d6/0xde0 Write of size 1 at addr ffff88800afbb2a5 by task touch/181 CPU: 0 PID: 181 Comm: touch Not tainted 6.6.13-gnu #1 4c9534092be820851bb687b82d1f92a426598dc6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2/GNU Guix 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x4c/0x70 print_report+0xc5/0x610 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 ? kasan_complete_mode_report_info+0x44/0x210 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 kasan_report+0xc2/0x110 ? ecryptfs_generate_key_packet
rt_info+0x44/0x210 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 kasan_report+0xc2/0x110 ? ecryptfs_generate_key_packet_set+0x7d6/0xde0 __asan_store1+0x62/0x80 ecryptfs_generate_key_packet_set+0x7d6/0xde0 ? __pfx_ecryptfs_generate_key_packet_set+0x10/0x10 ? __alloc_pages+0x2e2/0x540 ? __pfx_ovl_open+0x10/0x10 [overlay 30837f11141636a8e1793533a02e6e2e885dad1d] ? dentry_open+0x8f/0xd0 ecryptfs_write_metadata+0x30a/0x550 ? __pfx_ecryptfs_write_metadata+0x10/0x10 ? ecryptfs_get_lower_file+0x6b/0x190 ecryptfs_initialize_file+0x77/0x150 ecryptfs_create+0x1c2/0x2f0 path_openat+0x17cf/0x1ba0 ? __pfx_path_openat+0x10/0x10 do_filp_open+0x15e/0x290 ? __pfx_do_filp_open+0x10/0x10 ? __kasan_check_write+
17cf/0x1ba0 ? __pfx_path_openat+0x10/0x10 do_filp_open+0x15e/0x290 ? __pfx_do_filp_open+0x10/0x10 ? __kasan_check_write+0x18/0x30 ? _raw_spin_lock+0x86/0xf0 ? __pfx__raw_spin_lock+0x10/0x10 ? __kasan_check_write+0x18/0x30 ? alloc_fd+0xf4/0x330 do_sys_openat2+0x122/0x160 ? __pfx_do_sys_openat2+0x10/0x10 __x64_sys_openat+0xef/0x170 ? __pfx___x64_sys_openat+0x10/0x10 do_syscall_64+0x60/0xd0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 RIP: 0033:0x7f00a703fd67 Code: 25 00 00 41 00 3d 00 00 41 00 74 37 64 8b 04 25 18 00 00 00 85 c0 75 5b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 85 00 00 00 48 83 c4 68 5d 41 5c c3 0f 1f RSP: 002b:00007ffc088e30b0 EFLAGS: 00000246
00 0f 05 <48> 3d 00 f0 ff ff 0f 87 85 00 00 00 48 83 c4 68 5d 41 5c c3 0f 1f RSP: 002b:00007ffc088e30b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007ffc088e3368 RCX: 00007f00a703fd67 RDX: 0000000000000941 RSI: 00007ffc088e48d7 RDI: 00000000ffffff9c RBP: 00007ffc088e48d7 R08: 0000000000000001 R09: 0000000000000000 R10: 00000000000001b6 R11: 0000000000000246 R12: 0000000000000941 R13: 0000000000000000 R14: 00007ffc088e48d7 R15: 00007f00a7180040 </TASK> Allocated by task 181: kasan_save_stack+0x2f/0x60 kasan_set_track+0x29/0x40 kasan_save_alloc_info+0x25/0x40 __kasan_kmalloc+0xc5/0xd0 __kmalloc+0x66/0x160 ecryptfs_generate_key_packet_set+0x6d2/0xde0 ecryptfs_write
nfo+0x25/0x40 __kasan_kmalloc+0xc5/0xd0 __kmalloc+0x66/0x160 ecryptfs_generate_key_packet_set+0x6d2/0xde0 ecryptfs_write_metadata+0x30a/0x550 ecryptfs_initialize_file+0x77/0x150 ecryptfs_create+0x1c2/0x2f0 path_openat+0x17cf/0x1ba0 do_filp_open+0x15e/0x290 do_sys_openat2+0x122/0x160 __x64_sys_openat+0xef/0x170 do_syscall_64+0x60/0xd0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/1c125b9287e58f364d82174efb167414b92b11f1 - https://git.kernel.org/stable/c/235b85981051cd68fc215fd32a81c6f116bfc4df - https://git.kernel.org/stable/c/edbfc42ab080e78c6907d40a42c9d10b69e445c1 - https://
981051cd68fc215fd32a81c6f116bfc4df - https://git.kernel.org/stable/c/edbfc42ab080e78c6907d40a42c9d10b69e445c1 - https://git.kernel.org/stable/c/12db25a54ce6bb22b0af28010fff53ef9cb3fe93 - https://git.kernel.org/stable/c/0d0f8ba042af16519f1ef7dd10463a33b21b677c - https://git.kernel.org/stable/c/2ed750b7ae1b5dc72896d7dd114c419afd3d1910 - https://git.kernel.org/stable/c/a20f09452e2f58f761d11ad7b96b5c894c91030e - https://git.kernel.org/stable/c/f6008487f1eeb8693f8d2a36a89c87d9122ddf74 - https://git.kernel.org/stable/c/85a6a1aff08ec9f5b929d345d066e2830e8818e5
CVE ID: CVE-2024-38579 State: PUBLISHED Published: 2024-06-19T13:37:37.154Z Last Updated: 2025-11-04T17:21:33.961Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: bcm - Fix pointer arithmetic In spu2_dump_omd() value of ptr is increased by ciph_key_len instead of hash_iv_len which could lead to going beyond the buffer boundaries. Fix this bug by changing ciph_key_len to hash_iv_len. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c256b616067bfd6d274c679c06986b78d2402434 - https://git
A ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c256b616067bfd6d274c679c06986b78d2402434 - https://git.kernel.org/stable/c/e719c8991c161977a67197775067ab456b518c7b - https://git.kernel.org/stable/c/ebed0d666fa709bae9e8cafa8ec6e7ebd1d318c6 - https://git.kernel.org/stable/c/c69a1e4b419c2c466dd8c5602bdebadc353973dd - https://git.kernel.org/stable/c/49833a8da6407e7e9b532cc4054fdbcaf78f5fdd - https://git.kernel.org/stable/c/d0f14ae223c2421b334c1f1a9e48f1e809aee3a0 - https://git.kernel.org/stable/c/c0082ee420639a97e40cae66778b02b341b005e5 - https://git.kernel.org/stable/c/3b7a40740f04e2f27114dfd6225c5e721dda9d57 - https://git.kernel.org/stable/c/2b3460cbf454c6b03d7429e9ffc4fe0932
g/stable/c/3b7a40740f04e2f27114dfd6225c5e721dda9d57 - https://git.kernel.org/stable/c/2b3460cbf454c6b03d7429e9ffc4fe09322eb1a9
CVE ID: CVE-2024-38580 State: PUBLISHED Published: 2024-06-19T13:37:37.840Z Last Updated: 2025-05-04T09:14:33.781Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: epoll: be better about file lifetimes epoll can call out to vfs_poll() with a file pointer that may race with the last 'fput()'. That would make f_count go down to zero, and while the ep->mtx locking means that the resulting file pointer tear-down will be blocked until the poll returns, it means that f_count is already dead, and any use of it won't actually get a reference to the file any more: it's dead regardless. Make sure we have a valid ref on the file pointer bef
tually get a reference to the file any more: it's dead regardless. Make sure we have a valid ref on the file pointer before we call down to vfs_poll() from the epoll routines. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/cbfd1088e24ec4c1199756a37cb8e4cd0a4b016e - https://git.kernel.org/stable/c/559214eb4e5c3d05e69428af2fae2691ba1eb784 - https://git.kernel.org/stable/c/4f65f4defe4e23659275ce5153541cd4f76ce2d2 - https://git.kernel.org/stable/c/16e3182f6322575eb7c12e728ad3c7986a189d5d - https://git.kernel.org/stable/c/4efaa5acf0a1d2b5947f98abb3acf8bfd966422b
CVE ID: CVE-2024-38581 State: PUBLISHED Published: 2024-06-19T13:37:38.509Z Last Updated: 2025-05-21T09:12:42.039Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/mes: fix use-after-free issue Delete fence fallback timer to fix the ramdom use-after-free issue. v2: move to amdgpu_mes.c Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/70b1bf6d9edc8692d241f59a65f073aec6d501de - https://git.kernel.org/stable/c/39cfce75168c11421d70b8c0c65f6133edccb82a - https://git.kernel.org/stable/c/0f98c144c15c8fc0f3176c994bd4e727ef718a5c - https://git.kernel.org/s
c0c65f6133edccb82a - https://git.kernel.org/stable/c/0f98c144c15c8fc0f3176c994bd4e727ef718a5c - https://git.kernel.org/stable/c/948255282074d9367e01908b3f5dcf8c10fc9c3d
CVE ID: CVE-2024-38582 State: PUBLISHED Published: 2024-06-19T13:37:39.163Z Last Updated: 2025-11-04T17:21:35.321Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential hang in nilfs_detach_log_writer() Syzbot has reported a potential hang in nilfs_detach_log_writer() called during nilfs2 unmount. Analysis revealed that this is because nilfs_segctor_sync(), which synchronizes with the log writer thread, can be called after nilfs_segctor_destroy() terminates that thread, as shown in the call trace below: nilfs_detach_log_writer nilfs_segctor_destroy nilfs_segctor_kill_thread --> Shut down log writer thread flush_w
e below: nilfs_detach_log_writer nilfs_segctor_destroy nilfs_segctor_kill_thread --> Shut down log writer thread flush_work nilfs_iput_work_func nilfs_dispose_list iput nilfs_evict_inode nilfs_transaction_commit nilfs_construct_segment (if inode needs sync) nilfs_segctor_sync --> Attempt to synchronize with log writer thread *** DEADLOCK *** Fix this issue by changing nilfs_segctor_sync() so that the log writer thread returns normally without synchronizing after it terminates, and by forcing tasks that are already waiting to complete once after the thread terminates. The skipped inode metadata flushout will then be processed together in the subsequent cleanup work in nilfs_segctor_destroy().
ipped inode metadata flushout will then be processed together in the subsequent cleanup work in nilfs_segctor_destroy(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/911d38be151921a5d152bb55e81fd752384c6830 - https://git.kernel.org/stable/c/bc9cee50a4a4ca23bdc49f75ea8242d8a2193b3b - https://git.kernel.org/stable/c/eff7cdf890b02596b8d73e910bdbdd489175dbdb - https://git.kernel.org/stable/c/06afce714d87c7cd1dcfccbcd800c5c5d2cf1cfd - https://git.kernel.org/stable/c/1c3844c5f4eac043954ebf6403fa9fd1f0e9c1c0 - https://git.kernel.org/stable/c/a8799662fed1f8747edae87a1937549288baca6a - https://git.kernel.org/stable/c/6e5c8e8