Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
(./include/trace/events/lock.h:24 (discriminator 2)) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? lock_acquire (kernel/locking/lockdep.c:5822) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) __mutex_lock (kernel/locking/mutex.c:587 kernel/locking/mutex.c:735) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? fib_sync_up (net/ipv4/fib_semanti
eam_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) ? fib_sync_up (net/ipv4/fib_semantics.c:2167) ? team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) team_device_event (drivers/net/team/team_core.c:2928 drivers/net/team/team_core.c:2951 drivers/net/team/team_core.c:2973) notifier_call_chain (kernel/notifier.c:85) call_netdevice_notifiers_info (net/core/dev.c:1996) __dev_notify_flags (net/core/dev.c:8993) ? __dev_change_flags (net/core/dev.c:8975) dev_change_flags (net/core/dev.c:9027) vlan_device_event (net/8021q/vlan.c:85 net/8021q/vlan.c:470) ? br_device_event (net/bridge/br.c:143) noti
re/dev.c:9027) vlan_device_event (net/8021q/vlan.c:85 net/8021q/vlan.c:470) ? br_device_event (net/bridge/br.c:143) notifier_call_chain (kernel/notifier.c:85) call_netdevice_notifiers_info (net/core/dev.c:1996) dev_open (net/core/dev.c:1519 net/core/dev.c:1505) team_add_slave (drivers/net/team/team_core.c:1219 drivers/net/team/team_core.c:1977) ? __pfx_team_add_slave (drivers/net/team/team_core.c:1972) do_set_master (net/core/rtnetlink.c:2917) do_setlink.isra.0 (net/core/rtnetlink.c:3117) Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20 - https://git.kernel.org/stable/c/62ff16158
: - https://git.kernel.org/stable/c/0a7794b9ca78c8e7d001c583bf05736169de3f20 - https://git.kernel.org/stable/c/62ff1615815d565448c37cb8a7a2a076492ec471 - https://git.kernel.org/stable/c/bd099a2fa9be983ba0e90a57a59484fe9d520ba8 - https://git.kernel.org/stable/c/adff6ac889e16d97abd1e4543f533221127e978a - https://git.kernel.org/stable/c/184a564e6000b41582f160a5be9a9b5aabe22ac1 - https://git.kernel.org/stable/c/1bb06f919fa5bec77ad9b6002525c3dcc5c1fd6c - https://git.kernel.org/stable/c/d9bce1310c0e2a55888e3e08c9f69d8377b3a377 - https://git.kernel.org/stable/c/3fff5da4ca2164bb4d0f1e6cd33f6eb8a0e73e50
CVE ID: CVE-2024-58072 State: PUBLISHED Published: 2025-03-06T15:54:11.665Z Last Updated: 2025-11-03T19:34:08.754Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: remove unused check_buddy_priv Commit 2461c7d60f9f ("rtlwifi: Update header file") introduced a global list of private data structures. Later on, commit 26634c4b1868 ("rtlwifi Modify existing bits to match vendor version 2013.02.07") started adding the private data to that list at probe time and added a hook, check_buddy_priv to find the private data from a similar device. However, that function was never used. Besides, though there is a lock for that li
e private data from a similar device. However, that function was never used. Besides, though there is a lock for that list, it is never used. And when the probe fails, the private data is never removed from the list. This would cause a second probe to access freed memory. Remove the unused hook, structures and members, which will prevent the potential race condition on the list and its corruption during a second probe when probe fails. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/f801e754efa21bd61b3cc15ec7565696165b272f - https://git.kernel.org/stable/c/1b9cbd8a9ae68b32099fbb03b2d5ffa0c5e0dcc9 - https://git.kernel.org/stable/c/8e2fcc68fbaab
https://git.kernel.org/stable/c/1b9cbd8a9ae68b32099fbb03b2d5ffa0c5e0dcc9 - https://git.kernel.org/stable/c/8e2fcc68fbaab3ad9f5671fee2be0956134b740a - https://git.kernel.org/stable/c/1e39b0486cdb496cdfba3bc89886150e46acf6f4 - https://git.kernel.org/stable/c/465d01ef6962b82b1f0ad1f3e58b398dbd35c1c1 - https://git.kernel.org/stable/c/543e3e9f2e9e47ded774c74e680f28a0ca362aee - https://git.kernel.org/stable/c/006e803af7408c3fc815b0654fc5ab43d34f0154 - https://git.kernel.org/stable/c/2fdac64c3c35858aa8ac5caa70b232e03456e120
CVE ID: CVE-2024-58073 State: PUBLISHED Published: 2025-03-06T15:54:12.374Z Last Updated: 2025-10-01T19:36:36.273Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: check dpu_plane_atomic_print_state() for valid sspp Similar to the r_pipe sspp protect, add a check to protect the pipe state prints to avoid NULL ptr dereference for cases when the state is dumped without a corresponding atomic_check() where the pipe->sspp is assigned. Patchwork: https://patchwork.freedesktop.org/patch/628404/ Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/008af2074e4b91d34440102501b710c23
Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/008af2074e4b91d34440102501b710c235a3b245 - https://git.kernel.org/stable/c/789384eb1437aed94155dc0eac8a8a6ba1baf578
CVE ID: CVE-2024-58074 State: PUBLISHED Published: 2025-03-06T16:04:30.170Z Last Updated: 2025-05-04T10:09:23.193Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/i915: Grab intel_display from the encoder to avoid potential oopsies Grab the intel_display from 'encoder' rather than 'state' in the encoder hooks to avoid the massive footgun that is intel_sanitize_encoder(), which passes NULL as the 'state' argument to encoder .disable() and .post_disable(). TODO: figure out how to actually fix intel_sanitize_encoder()... References: - https://git.kernel.org/stable/c/1885401569f24eb35c631bcc4e6543360dbe9292 - https://git.kernel.
ncoder()... References: - https://git.kernel.org/stable/c/1885401569f24eb35c631bcc4e6543360dbe9292 - https://git.kernel.org/stable/c/dc3806d9eb66d0105f8d55d462d4ef681d9eac59
CVE ID: CVE-2024-58075 State: PUBLISHED Published: 2025-03-06T16:04:30.864Z Last Updated: 2025-05-04T10:09:24.851Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - do not transfer req when tegra init fails The tegra_cmac_init or tegra_sha_init function may return an error when memory is exhausted. It should not transfer the request when they return an error. References: - https://git.kernel.org/stable/c/1dbc270f9df7f0ae1e591323431869059cee1b7d - https://git.kernel.org/stable/c/5eaa7c916e1ec4b122a1c3a8a20e692d9d9e174e - https://git.kernel.org/stable/c/15589bda46830695a3261518bb7627afac61f519
CVE ID: CVE-2024-58076 State: PUBLISHED Published: 2025-03-06T16:13:40.307Z Last Updated: 2025-11-03T19:34:10.126Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gcc-sm6350: Add missing parent_map for two clocks If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [ 3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934] _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] clk_core_determine_round_nolo
eq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] clk_core_determine_round_nolock+0x58/0xe4 [ 3.421414] clk_core_round_rate_nolock+0x48/0xfc [ 3.432974] clk_core_round_rate_nolock+0xd0/0xfc [ 3.444483] clk_core_set_rate_nolock+0x8c/0x300 [ 3.455886] clk_set_rate+0x38/0x14c Add the parent_map property for two clocks where it's missing and also un-inline the parent_data as well to keep the matching parent_map and parent_data together. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/175af15551ed5aa6af16ff97aff75cfffb42da21 - https://git.kernel.org/stable/c/39336edd14a59dc086fb19957
kernel.org/stable/c/175af15551ed5aa6af16ff97aff75cfffb42da21 - https://git.kernel.org/stable/c/39336edd14a59dc086fb19957655e0f340bb28e8 - https://git.kernel.org/stable/c/08b77ed7cfaac62bba51ac7a0487409ec9fcbc84 - https://git.kernel.org/stable/c/b6fe13566bf5676b1e3b72d2a06d875733e93ee6 - https://git.kernel.org/stable/c/3e567032233a240b903dc11c9f18eeb3faa10ffa - https://git.kernel.org/stable/c/96fe1a7ee477d701cfc98ab9d3c730c35d966861
CVE ID: CVE-2024-58077 State: PUBLISHED Published: 2025-03-06T16:13:41.159Z Last Updated: 2025-11-03T19:34:11.518Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback commit 1f5664351410 ("ASoC: lower "no backend DAIs enabled for ... Port" log severity") ignores -EINVAL error message on common soc_pcm_ret(). It is used from many functions, ignoring -EINVAL is over-kill. The reason why -EINVAL was ignored was it really should only be used upon invalid parameters coming from userspace and in that case we don't want to log an error since we do not want to give userspace a way
eters coming from userspace and in that case we don't want to log an error since we do not want to give userspace a way to do a denial-of-service attack on the syslog / diskspace. So don't use soc_pcm_ret() on .prepare callback is better idea. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/79b8c7c93beb4f5882c9ee5b9ba73354fa4bc9ee - https://git.kernel.org/stable/c/90778f31efdf44622065ebbe8d228284104bd26f - https://git.kernel.org/stable/c/8ec4e8c8e142933eaa8e1ed87168831069250e4e - https://git.kernel.org/stable/c/301c26a018acb94dd537a4418cefa0f654500c6f
CVE ID: CVE-2024-58078 State: PUBLISHED Published: 2025-03-06T16:13:41.909Z Last Updated: 2025-05-04T10:09:29.311Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors misc_minor_alloc was allocating id using ida for minor only in case of MISC_DYNAMIC_MINOR but misc_minor_free was always freeing ids using ida_free causing a mismatch and following warn: > > WARNING: CPU: 0 PID: 159 at lib/idr.c:525 ida_free+0x3e0/0x41f > > ida_free called for id=127 which is not allocated. > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ... > > [<60941eb4>] ida_free+0x3e0/0x41f > > [<60
7 which is not allocated. > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ... > > [<60941eb4>] ida_free+0x3e0/0x41f > > [<605ac993>] misc_minor_free+0x3e/0xbc > > [<605acb82>] misc_deregister+0x171/0x1b3 misc_minor_alloc is changed to allocate id from ida for all minors falling in the range of dynamic/ misc dynamic minors References: - https://git.kernel.org/stable/c/3df72111c39f7e4c5029c9ff720b56ec2e05b764 - https://git.kernel.org/stable/c/8b4120b3e060e137eaa8dc76a1c40401088336e5 - https://git.kernel.org/stable/c/6635332d246d7db89b90e145f2bf937406cecaf0 - https://git.kernel.org/stable/c/6d04d2b554b14ae6c428a9c60b6c85f1e5c89f68
CVE ID: CVE-2024-58079 State: PUBLISHED Published: 2025-03-06T16:13:42.640Z Last Updated: 2025-11-03T19:34:12.917Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix crash during unbind if gpio unit is in use We used the wrong device for the device managed functions. We used the usb device, when we should be using the interface device. If we unbind the driver from the usb interface, the cleanup functions are never called. In our case, the IRQ is never disabled. If an IRQ is triggered, it will try to access memory sections that are already free, causing an OOPS. We cannot use the function devm_request_threaded_i
try to access memory sections that are already free, causing an OOPS. We cannot use the function devm_request_threaded_irq here. The devm_* clean functions may be called after the main structure is released by uvc_delete. Luckily this bug has small impact, as it is only affected by devices with gpio units and the user has to unbind the device, a disconnect will not trigger this error. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/0fdd7cc593385e46e92e180b71e264fc9c195298 - https://git.kernel.org/stable/c/3c00e94d00ca079bef7906d6f39d1091bccfedd3 - https://git.kernel.org/stable/c/0b5e0445bc8384c18bd35cb9fe87f6258c6271d9 - https://git.kernel.org
06d6f39d1091bccfedd3 - https://git.kernel.org/stable/c/0b5e0445bc8384c18bd35cb9fe87f6258c6271d9 - https://git.kernel.org/stable/c/d2eac8b14ac690aa73052aa6d4ba69005715367e - https://git.kernel.org/stable/c/5d2e65cbe53d0141ed095cf31c2dcf3d8668c11d - https://git.kernel.org/stable/c/a9ea1a3d88b7947ce8cadb2afceee7a54872bbc5
CVE ID: CVE-2024-58080 State: PUBLISHED Published: 2025-03-06T16:13:43.414Z Last Updated: 2025-11-03T19:34:14.320Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: qcom: dispcc-sm6350: Add missing parent_map for a clock If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [ 3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934] _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] clk_core_determine_round_nolo
eq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] clk_core_determine_round_nolock+0x58/0xe4 [ 3.421414] clk_core_round_rate_nolock+0x48/0xfc [ 3.432974] clk_core_round_rate_nolock+0xd0/0xfc [ 3.444483] clk_core_set_rate_nolock+0x8c/0x300 [ 3.455886] clk_set_rate+0x38/0x14c Add the parent_map property for the clock where it's missing and also un-inline the parent_data as well to keep the matching parent_map and parent_data together. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3daca9050857220726732ad9d4a8512069386f46 - https://git.kernel.org/stable/c/3ad28517385e2821e8e43388d6
ernel.org/stable/c/3daca9050857220726732ad9d4a8512069386f46 - https://git.kernel.org/stable/c/3ad28517385e2821e8e43388d6a0b3e1ba0bc3ab - https://git.kernel.org/stable/c/2dba8d5d423fa5f6f3a687aa6e0da5808f69091b - https://git.kernel.org/stable/c/a1f15808adfd77268eac7fefce5378ad9fedbfba - https://git.kernel.org/stable/c/d4cdb196f182d2fbe336c968228be00d8c3fed05
CVE ID: CVE-2024-58081 State: PUBLISHED Published: 2025-03-06T16:13:44.176Z Last Updated: 2025-10-01T19:36:35.804Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: clk: mmp2: call pm_genpd_init() only after genpd.name is set Setting the genpd's struct device's name with dev_set_name() is happening within pm_genpd_init(). If it remains NULL, things can blow up later, such as when crafting the devfs hierarchy for the power domain: Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read ... Call trace: strlen from start_creating+0x90/0x138 start_creating from debugfs_create_dir+0x20/0x178 debugfs_creat
ad ... Call trace: strlen from start_creating+0x90/0x138 start_creating from debugfs_create_dir+0x20/0x178 debugfs_create_dir from genpd_debug_add.part.0+0x4c/0x144 genpd_debug_add.part.0 from genpd_debug_init+0x74/0x90 genpd_debug_init from do_one_initcall+0x5c/0x244 do_one_initcall from kernel_init_freeable+0x19c/0x1f4 kernel_init_freeable from kernel_init+0x1c/0x12c kernel_init from ret_from_fork+0x14/0x28 Bisecting tracks this crash back to commit 899f44531fe6 ("pmdomain: core: Add GENPD_FLAG_DEV_NAME_FW flag"), which exchanges use of genpd->name with dev_name(&genpd->dev) in genpd_debug_add.part(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/s
ev) in genpd_debug_add.part(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/eca01d5911fb34218d10a58d8d9534b758c8fd0a - https://git.kernel.org/stable/c/763517124e27b07fa300b486d7d13c5d563a215e - https://git.kernel.org/stable/c/e24b15d4704dcb73920c3d18a6157abd18df08c1
CVE ID: CVE-2024-58082 State: PUBLISHED Published: 2025-03-06T16:13:44.896Z Last Updated: 2025-05-04T10:09:39.779Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: nuvoton: Fix an error check in npcm_video_ece_init() When function of_find_device_by_node() fails, it returns NULL instead of an error code. So the corresponding error check logic should be modified to check whether the return value is NULL and set the error code to be returned as -ENODEV. References: - https://git.kernel.org/stable/c/bdd823b9d068284e1d998b962cfef29236365df3 - https://git.kernel.org/stable/c/c36b830754ae1dd1db41c27f57b29267878f9702 - https://git
068284e1d998b962cfef29236365df3 - https://git.kernel.org/stable/c/c36b830754ae1dd1db41c27f57b29267878f9702 - https://git.kernel.org/stable/c/c4b7779abc6633677e6edb79e2809f4f61fde157
CVE ID: CVE-2024-58083 State: PUBLISHED Published: 2025-03-06T16:13:45.631Z Last Updated: 2025-11-03T19:34:17.500Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() Explicitly verify the target vCPU is fully online _prior_ to clamping the index in kvm_get_vcpu(). If the index is "bad", the nospec clamping will generate '0', i.e. KVM will return vCPU0 instead of NULL. In practice, the bug is unlikely to cause problems, as it will only come into play if userspace or the guest is buggy or misbehaving, e.g. KVM may send interrupts to vCPU0 instead of dropping them on the f
userspace or the guest is buggy or misbehaving, e.g. KVM may send interrupts to vCPU0 instead of dropping them on the floor. However, returning vCPU0 when it shouldn't exist per online_vcpus is problematic now that KVM uses an xarray for the vCPUs array, as KVM needs to insert into the xarray before publishing the vCPU to userspace (see commit c5b077549136 ("KVM: Convert the kvm->vcpus array to a xarray")), i.e. before vCPU creation is guaranteed to succeed. As a result, incorrectly providing access to vCPU0 will trigger a use-after-free if vCPU0 is dereferenced and kvm_vm_ioctl_create_vcpu() bails out of vCPU creation due to an error and frees vCPU0. Commit afb2acb2e3a3 ("KVM: Fix vcpu_arr
_ioctl_create_vcpu() bails out of vCPU creation due to an error and frees vCPU0. Commit afb2acb2e3a3 ("KVM: Fix vcpu_array[0] races") papered over that issue, but in doing so introduced an unsolvable teardown conundrum. Preventing accesses to vCPU0 before it's fully online will allow reverting commit afb2acb2e3a3, without re-introducing the vcpu_array[0] UAF race. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5cce2ed69b00e022b5cdf0c49c82986abd2941a8 - https://git.kernel.org/stable/c/09d50ccf0b2d739db4a485b08afe7520a4402a63 - https://git.kernel.org/stable/c/7c4899239d0f70f88ac42665b3da51678d122480 - https://git.kernel
b4a485b08afe7520a4402a63 - https://git.kernel.org/stable/c/7c4899239d0f70f88ac42665b3da51678d122480 - https://git.kernel.org/stable/c/d817e510662fd1c9797952408d94806f97a5fffd - https://git.kernel.org/stable/c/125da53b3c0c9d7f58353aea0076e9efd6498ba7 - https://git.kernel.org/stable/c/f2f805ada63b536bc192458a7098388286568ad4 - https://git.kernel.org/stable/c/ca8da90ed1432ff3d000de4f1e2275d4e7d21b96 - https://git.kernel.org/stable/c/1e7381f3617d14b3c11da80ff5f8a93ab14cfc46
CVE ID: CVE-2024-58084 State: PUBLISHED Published: 2025-03-06T16:22:31.998Z Last Updated: 2025-10-01T19:36:35.655Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Fix missing read barrier in qcom_scm_get_tzmem_pool() Commit 2e4955167ec5 ("firmware: qcom: scm: Fix __scm and waitq completion variable initialization") introduced a write barrier in probe function to store global '__scm' variable. We all known barriers are paired (see memory-barriers.txt: "Note that write barriers should normally be paired with read or address-dependency barriers"), therefore accessing it from concurrent contexts requires read ba
y be paired with read or address-dependency barriers"), therefore accessing it from concurrent contexts requires read barrier. Previous commit added such barrier in qcom_scm_is_available(), so let's use that directly. Lack of this read barrier can result in fetching stale '__scm' variable value, NULL, and dereferencing it. Note that barrier in qcom_scm_is_available() satisfies here the control dependency. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/fee921e3c641f64185abee83f9a6e65f0b380682 - https://git.kernel.org/stable/c/e03db7c1255ebabba5e1a447754faeb138de15a2 - https://git.kernel.org/stable/c/b628510397b5cafa1f5d3e848a28affd1c635302
CVE ID: CVE-2024-58085 State: PUBLISHED Published: 2025-03-06T16:22:32.761Z Last Updated: 2025-11-03T19:34:20.277Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tomoyo: don't emit warning in tomoyo_write_control() syzbot is reporting too large allocation warning at tomoyo_write_control(), for one can write a very very long line without new line character. To fix this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE, for practically a valid line should be always shorter than 32KB where the "too small to fail" memory-allocation rule applies. One might try to write a valid line that is longer than 32KB, but s
"too small to fail" memory-allocation rule applies. One might try to write a valid line that is longer than 32KB, but such request will likely fail with -ENOMEM. Therefore, I feel that separately returning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant. There is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/c67efabddc73171c7771d3ffe4ffa1e503ee533e - https://git.kernel.org/stable/c/f6b37b3e12de638753bce79a2858070b9c4a4ad3 - https://git.kernel.org/stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1 - https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196
stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1 - https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f - https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a - https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25 - https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd - https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685
CVE ID: CVE-2024-58086 State: PUBLISHED Published: 2025-03-06T16:28:23.042Z Last Updated: 2025-11-03T19:34:21.647Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Stop active perfmon if it is being destroyed If the active performance monitor (`v3d->active_perfmon`) is being destroyed, stop it first. Currently, the active perfmon is not stopped during destruction, leaving the `v3d->active_perfmon` pointer stale. This can lead to undefined behavior and instability. This patch ensures that the active perfmon is stopped before being destroyed, aligning with the behavior introduced in commit 7d1fd3638ee3 ("drm/v3d: Stop the