Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
NULL; This means that writes are not checked when the register containing the size of the passed buffer has not a fixed size. Through this bug, a BPF program can write to a map which is marked as read-only, for example, .rodata global maps. The problem is that MEM_UNINIT's initial meaning that "the passed buffer to the BPF helper does not need to be initialized" which was added back in commit 435faee1aae9 ("bpf, verifier: add ARG_PTR_TO_RAW_STACK type") got overloaded over time with "the passed buffer is being written to". The problem however is that checks such as the above which were added later via 06c1c049721a ("bpf: allow helpers access to variable memory") set meta to NULL in order fo
ve which were added later via 06c1c049721a ("bpf: allow helpers access to variable memory") set meta to NULL in order force the user to always initialize the passed buffer to the helper. Due to the current double meaning of MEM_UNINIT, this bypasses verifier write checks to the memory (not boundary checks though) and only assumes the latter memory is read instead. Fix this by reverting MEM_UNINIT back to its original meaning, and having MEM_WRITE as an annotation to BPF helpers in order to then trigger the BPF verifier checks for writing to memory. Some notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO} we can access fn->arg_type[arg - 1] since it must contain a preceding
r_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO} we can access fn->arg_type[arg - 1] since it must contain a preceding ARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed altogether since we do check both BPF_READ and BPF_WRITE. Same for the equivalent check_kfunc_mem_size_reg(). Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/43f4df339a4d375bedcad29a61ae6f0ee7a048f8 - https://git.kernel.org/stable/c/48068ccaea957469f1adf78dfd2c1c9a7e18f0fe - https://git.kernel.org/stable/c/54bc31682660810af1bed7ca7a19f182df8d3df8 - https://git.kernel.org/stable/c/8ea607330a39184f51737c6ae706db7fdca7628e
CVE ID: CVE-2024-50165 State: PUBLISHED Published: 2024-11-07T09:31:41.923Z Last Updated: 2025-10-01T20:27:11.791Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bpf: Preserve param->string when parsing mount options In bpf_parse_param(), keep the value of param->string intact so it can be freed later. Otherwise, the kmalloc area pointed to by param->string will be leaked as shown below: unreferenced object 0xffff888118c46d20 (size 8): comm "new_name", pid 12109, jiffies 4295580214 hex dump (first 8 bytes): 61 6e 79 00 38 c9 5c 7e any.8.\~ backtrace (crc e1b7f876): [<00000000c6848ac7>] kmemleak_alloc+0x4b/0x80 [<00000000de9f7d0
6e 79 00 38 c9 5c 7e any.8.\~ backtrace (crc e1b7f876): [<00000000c6848ac7>] kmemleak_alloc+0x4b/0x80 [<00000000de9f7d00>] __kmalloc_node_track_caller_noprof+0x36e/0x4a0 [<000000003e29b886>] memdup_user+0x32/0xa0 [<0000000007248326>] strndup_user+0x46/0x60 [<0000000035b3dd29>] __x64_sys_fsconfig+0x368/0x3d0 [<0000000018657927>] x64_sys_call+0xff/0x9f0 [<00000000c0cabc95>] do_syscall_64+0x3b/0xc0 [<000000002f331597>] entry_SYSCALL_64_after_hwframe+0x4b/0x53 Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5d7a0a426540319327309035509cb768a2f5c2c4 - https://git.kernel.org/stable/c/1f97c03f43fadc407de5b5cb01c07755053e1c22
CVE ID: CVE-2024-50166 State: PUBLISHED Published: 2024-11-07T09:31:42.793Z Last Updated: 2025-10-01T20:27:11.645Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fsl/fman: Fix refcount handling of fman-related devices In mac_probe() there are multiple calls to of_find_device_by_node(), fman_bind() and fman_port_bind() which takes references to of_dev->dev. Not all references taken by these calls are released later on error path in mac_probe() and in mac_remove() which lead to reference leaks. Add references release. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5ed4334fc9512f93
lease. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/5ed4334fc9512f934fe2ae9c4cf7f8142e451b8b - https://git.kernel.org/stable/c/3c2a3619d565fe16bf59b0a047bab103a2ee4490 - https://git.kernel.org/stable/c/1dec67e0d9fbb087c2ab17bf1bd17208231c3bb1
CVE ID: CVE-2024-50167 State: PUBLISHED Published: 2024-11-07T09:31:43.782Z Last Updated: 2025-11-03T22:26:22.074Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: be2net: fix potential memory leak in be_xmit() The be_xmit() returns NETDEV_TX_OK without freeing skb in case of be_xmit_enqueue() fails, add dev_kfree_skb_any() to fix it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/941026023c256939943a47d1c66671526befbb26 - https://git.kernel.org/stable/c/6b7ce8ee01c33c380aaa5077ff25215492e7eb0e - https://git.kernel.org/stable/c/77bc881d370e850b7f3cd2b5eae6
nel.org/stable/c/6b7ce8ee01c33c380aaa5077ff25215492e7eb0e - https://git.kernel.org/stable/c/77bc881d370e850b7f3cd2b5eae67d596b40efbc - https://git.kernel.org/stable/c/919ab6e2370289a2748780f44a43333cd3878aa7 - https://git.kernel.org/stable/c/4c5f170ef4f85731a4d43ad9a6ac51106c0946be - https://git.kernel.org/stable/c/641c1beed52bf3c6deb0193fe4d38ec9ff75d2ae - https://git.kernel.org/stable/c/e86a79b804e26e3b7f1e415b22a085c0bb7ea3d3 - https://git.kernel.org/stable/c/e4dd8bfe0f6a23acd305f9b892c00899089bd621
CVE ID: CVE-2024-50168 State: PUBLISHED Published: 2024-11-07T09:31:44.843Z Last Updated: 2025-11-03T22:26:23.619Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net/sun3_82586: fix potential memory leak in sun3_82586_send_packet() The sun3_82586_send_packet() returns NETDEV_TX_OK without freeing skb in case of skb->len being too long, add dev_kfree_skb() to fix it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/137010d26dc5cd47cd62fef77cbe952d31951b7a - https://git.kernel.org/stable/c/8d5b20fbc548650019afa96822b6a33ea4ec8aa5 - https://git.kernel.org/sta
7cbe952d31951b7a - https://git.kernel.org/stable/c/8d5b20fbc548650019afa96822b6a33ea4ec8aa5 - https://git.kernel.org/stable/c/db755e55349045375c5c7036e8650afb3ff419d8 - https://git.kernel.org/stable/c/9c6ce55e6f0bd1541f112833006b4052614c7d94 - https://git.kernel.org/stable/c/1a17a4ac2d57102497fac53b53c666dba6a0c20d - https://git.kernel.org/stable/c/6dc937a3086e344f965ca5c459f8f3eb6b68d890 - https://git.kernel.org/stable/c/84f2bac74000dbb7a177d9b98a17031ec8d07ec5 - https://git.kernel.org/stable/c/2cb3f56e827abb22c4168ad0c1bbbf401bb2f3b8
CVE ID: CVE-2024-50169 State: PUBLISHED Published: 2024-11-07T09:31:45.804Z Last Updated: 2025-10-01T20:27:11.243Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: vsock: Update rx_bytes on read_skb() Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb(). While here, also inform the peer that we've freed up space and it has more credit. Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU
to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589 Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/66cd51de31c682a311c2fa25c580b7ea45859dd9 - https://git.kernel.org/stable/c/e5ca2b98090b4bb1c393088c724af6c37812a829 - https://git.kernel.org/stable/c/3543152f2d330141d9394d28855cb90b860091d2
CVE ID: CVE-2024-50170 State: PUBLISHED Published: 2024-11-07T09:31:46.722Z Last Updated: 2025-10-01T20:27:11.113Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: bcmasp: fix potential memory leak in bcmasp_xmit() The bcmasp_xmit() returns NETDEV_TX_OK without freeing skb in case of mapping fails, add dev_kfree_skb() to fix it. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/7218de0778aefbbbcfe474a55f88bbf6f244627d - https://git.kernel.org/stable/c/f689f20d3e09f2d4d0a2c575a9859115a33e68bd - https://git.kernel.org/stable/c/fed07d3eb8a8d9fcc0e455175a89bc6445d6faed
CVE ID: CVE-2024-50171 State: PUBLISHED Published: 2024-11-07T09:31:47.585Z Last Updated: 2025-11-03T22:26:25.100Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: systemport: fix potential memory leak in bcm_sysport_xmit() The bcm_sysport_xmit() returns NETDEV_TX_OK without freeing skb in case of dma_map_single() fails, add dev_kfree_skb() to fix it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8e81ce7d0166a2249deb6d5e42f28a8b8c9ea72f - https://git.kernel.org/stable/c/31701ef0c4547973991ff63596c927f841dfd133 - https://git.kernel.org/stable/c/b63211
a72f - https://git.kernel.org/stable/c/31701ef0c4547973991ff63596c927f841dfd133 - https://git.kernel.org/stable/c/b6321146773dcbbc372a54dbada67e0b50e0a25c - https://git.kernel.org/stable/c/5febfc545389805ce83d37f9f4317055b26dd7d7 - https://git.kernel.org/stable/c/533d2f30aef272dade17870a509521c3afc38a03 - https://git.kernel.org/stable/c/4b70478b984af3c9d0279c121df5ff94e2533dbd - https://git.kernel.org/stable/c/7d5030a819c3589cf9948b1eee397b626ec590f5 - https://git.kernel.org/stable/c/c401ed1c709948e57945485088413e1bb5e94bd1
CVE ID: CVE-2024-50172 State: PUBLISHED Published: 2024-11-07T09:31:48.430Z Last Updated: 2025-10-01T20:27:10.871Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Fix a possible memory leak In bnxt_re_setup_chip_ctx() when bnxt_qplib_map_db_bar() fails driver is not freeing the memory allocated for "rdev->chip_ctx". Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/73e04a6114e08b5eb10e589e12b680955accb376 - https://git.kernel.org/stable/c/595fa9b17201028d35f92d450fc0ecda873fe469 - https://git.kernel.org/stable/c/3fc5410f225d1651580a4aeb7c72f55e28673b53
CVE ID: CVE-2024-50173 State: PUBLISHED Published: 2024-11-08T05:23:55.847Z Last Updated: 2025-10-01T20:27:10.747Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix access to uninitialized variable in tick_ctx_cleanup() The group variable can't be used to retrieve ptdev in our second loop, because it points to the previously iterated list_head, not a valid group. Get the ptdev object from the scheduler instead. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/ac2ca5e5148a0d4d78ac01c2d8348d0757c7367f - https://git.kernel.org/stable/c/3bde05794497d5f426d4ea2ecb9868bf77
g/stable/c/ac2ca5e5148a0d4d78ac01c2d8348d0757c7367f - https://git.kernel.org/stable/c/3bde05794497d5f426d4ea2ecb9868bf7721fb24 - https://git.kernel.org/stable/c/282864cc5d3f144af0cdea1868ee2dc2c5110f0d
CVE ID: CVE-2024-50174 State: PUBLISHED Published: 2024-11-08T05:23:56.752Z Last Updated: 2025-10-01T20:27:10.632Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix race when converting group handle to group object XArray provides it's own internal lock which protects the internal array when entries are being simultaneously added and removed. However there is still a race between retrieving the pointer from the XArray and incrementing the reference count. To avoid this race simply hold the internal XArray lock when incrementing the reference count, this ensures there cannot be a racing call to xa_erase(). Addition
al XArray lock when incrementing the reference count, this ensures there cannot be a racing call to xa_erase(). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/8a585d553c11965332d7a2d74e79ef92a42bfc87 - https://git.kernel.org/stable/c/44742138d151c3a945460ae7beff8ae45ac0bf58 - https://git.kernel.org/stable/c/cac075706f298948898b1f63e81709df42afa75d
CVE ID: CVE-2024-50175 State: PUBLISHED Published: 2024-11-08T05:23:57.808Z Last Updated: 2025-10-01T20:27:10.500Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: Remove use_count guard in stop_streaming The use_count check was introduced so that multiple concurrent Raw Data Interfaces RDIs could be driven by different virtual channels VCs on the CSIPHY input driving the video pipeline. This is an invalid use of use_count though as use_count pertains to the number of times a video entity has been opened by user-space not the number of active streams. If use_count and stream-on count don't agree then stop_stre
been opened by user-space not the number of active streams. If use_count and stream-on count don't agree then stop_streaming() will break as is currently the case and has become apparent when using CAMSS with libcamera's released softisp 0.3. The use of use_count like this is a bit hacky and right now breaks regular usage of CAMSS for a single stream case. Stopping qcam results in the splat below, and then it cannot be started again and any attempts to do so fails with -EBUSY. [ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] ... [ 1265.510630] Call trace: [ 1265.510636] __vb2_queue_cancel+0x230/
_vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] ... [ 1265.510630] Call trace: [ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] [ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common] [ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2] [ 1265.510673] v4l_streamoff+0x24/0x30 [videodev] [ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev] [ 1265.510732] video_usercopy+0x304/0x8c4 [videodev] [ 1265.510757] video_ioctl2+0x18/0x34 [videodev] [ 1265.510782] v4l2_ioctl+0x40/0x60 [videodev] ... [ 1265.510944] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 0 in active state [ 1265.511175] videobuf2_common: driver bug: stop_streaming operat
reaming operation is leaving buffer 0 in active state [ 1265.511175] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 1 in active state [ 1265.511398] videobuf2_common: driver bug: stop_streaming operation is leaving buffer 2 in active st One CAMSS specific way to handle multiple VCs on the same RDI might be: - Reference count each pipeline enable for CSIPHY, CSID, VFE and RDIx. - The video buffers are already associated with msm_vfeN_rdiX so release video buffers when told to do so by stop_streaming. - Only release the power-domains for the CSIPHY, CSID and VFE when their internal refcounts drop. Either way refusing to release video buffers based on use_count is erro
CSID and VFE when their internal refcounts drop. Either way refusing to release video buffers based on use_count is erroneous and should be reverted. The silicon enabling code for selecting VCs is perfectly fine. Its a "known missing feature" that concurrent VCs won't work with CAMSS right now. Initial testing with this code didn't show an error but, SoftISP and "real" usage with Google Hangouts breaks the upstream code pretty quickly, we need to do a partial revert and take another pass at VCs. This commit partially reverts commit 89013969e232 ("media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels") Additional Analyst Notes: - CISA ADP Vulnrichment: References:
ine starting and stopping for multiple virtual channels") Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c2218a82f795dc3d0b6210bcaa3d9c5ca736fcd9 - https://git.kernel.org/stable/c/a975db8aea152f9907aa53a7f517e557ccb40da3 - https://git.kernel.org/stable/c/d7d4dde3decef1b5aa1f5c390147f79aae412dee - https://git.kernel.org/stable/c/25f18cb1b673220b76a86ebef8e7fb79bd303b27
CVE ID: CVE-2024-50176 State: PUBLISHED Published: 2024-11-08T05:23:58.496Z Last Updated: 2025-11-03T22:26:26.602Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: remoteproc: k3-r5: Fix error handling when power-up failed By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel
d instance. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/87ab3af7447791d0c619610fd560bd804549e187 - https://git.kernel.org/stable/c/fc71c23958931713b5e76f317b76be37189f2516 - https://git.kernel.org/stable/c/afd102bde99d90ef41e043c846ea34b04433eb7b - https://git.kernel.org/stable/c/7afb5e3aa989c479979faeb18768a67889a7a9c6 - https://git.kernel.org/stable/c/9ab27eb5866ccbf57715cfdba4b03d57776092fb
CVE ID: CVE-2024-50177 State: PUBLISHED Published: 2024-11-08T05:23:59.205Z Last Updated: 2025-10-01T20:27:10.217Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix a UBSAN warning in DML2.1 When programming phantom pipe, since cursor_width is explicity set to 0, this causes calculation logic to trigger overflow for an unsigned int triggering the kernel's UBSAN check as below: [ 40.962845] UBSAN: shift-out-of-bounds in /tmp/amd.EfpumTkO/amd/amdgpu/../display/dc/dml2/dml21/src/dml2_core/dml2_core_dcn4_calcs.c:3312:34 [ 40.962849] shift exponent 4294967170 is too large for 32-bit type 'unsigned int' [ 40.962852]
ore_dcn4_calcs.c:3312:34 [ 40.962849] shift exponent 4294967170 is too large for 32-bit type 'unsigned int' [ 40.962852] CPU: 1 PID: 1670 Comm: gnome-shell Tainted: G W OE 6.5.0-41-generic #41~22.04.2-Ubuntu [ 40.962854] Hardware name: Gigabyte Technology Co., Ltd. X670E AORUS PRO X/X670E AORUS PRO X, BIOS F21 01/10/2024 [ 40.962856] Call Trace: [ 40.962857] <TASK> [ 40.962860] dump_stack_lvl+0x48/0x70 [ 40.962870] dump_stack+0x10/0x20 [ 40.962872] __ubsan_handle_shift_out_of_bounds+0x1ac/0x360 [ 40.962878] calculate_cursor_req_attributes.cold+0x1b/0x28 [amdgpu] [ 40.963099] dml_core_mode_support+0x6b91/0x16bc0 [amdgpu] [ 40.963327] ? srso_alias_return_thunk+0x5/0x7f [ 40.963331] ? Calculate
] dml_core_mode_support+0x6b91/0x16bc0 [amdgpu] [ 40.963327] ? srso_alias_return_thunk+0x5/0x7f [ 40.963331] ? CalculateWatermarksMALLUseAndDRAMSpeedChangeSupport+0x18b8/0x2790 [amdgpu] [ 40.963534] ? srso_alias_return_thunk+0x5/0x7f [ 40.963536] ? dml_core_mode_support+0xb3db/0x16bc0 [amdgpu] [ 40.963730] dml2_core_calcs_mode_support_ex+0x2c/0x90 [amdgpu] [ 40.963906] ? srso_alias_return_thunk+0x5/0x7f [ 40.963909] ? dml2_core_calcs_mode_support_ex+0x2c/0x90 [amdgpu] [ 40.964078] core_dcn4_mode_support+0x72/0xbf0 [amdgpu] [ 40.964247] dml2_top_optimization_perform_optimization_phase+0x1d3/0x2a0 [amdgpu] [ 40.964420] dml2_build_mode_programming+0x23d/0x750 [amdgpu] [ 40.964587] dml21_validat
tion_phase+0x1d3/0x2a0 [amdgpu] [ 40.964420] dml2_build_mode_programming+0x23d/0x750 [amdgpu] [ 40.964587] dml21_validate+0x274/0x770 [amdgpu] [ 40.964761] ? srso_alias_return_thunk+0x5/0x7f [ 40.964763] ? resource_append_dpp_pipes_for_plane_composition+0x27c/0x3b0 [amdgpu] [ 40.964942] dml2_validate+0x504/0x750 [amdgpu] [ 40.965117] ? dml21_copy+0x95/0xb0 [amdgpu] [ 40.965291] ? srso_alias_return_thunk+0x5/0x7f [ 40.965295] dcn401_validate_bandwidth+0x4e/0x70 [amdgpu] [ 40.965491] update_planes_and_stream_state+0x38d/0x5c0 [amdgpu] [ 40.965672] update_planes_and_stream_v3+0x52/0x1e0 [amdgpu] [ 40.965845] ? srso_alias_return_thunk+0x5/0x7f [ 40.965849] dc_update_planes_and_stream+0x71/0xb0 [
0x52/0x1e0 [amdgpu] [ 40.965845] ? srso_alias_return_thunk+0x5/0x7f [ 40.965849] dc_update_planes_and_stream+0x71/0xb0 [amdgpu] Fix this by adding a guard for checking cursor width before triggering the size calculation. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/27bc3da5eae57e3af8f5648b4498ffde48781434 - https://git.kernel.org/stable/c/eaf3adb8faab611ba57594fa915893fc93a7788c
CVE ID: CVE-2024-50178 State: PUBLISHED Published: 2024-11-08T05:24:00.205Z Last Updated: 2025-10-01T20:27:10.074Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request() Use raw_smp_processor_id() instead of plain smp_processor_id() in do_service_request(), otherwise we may get some errors with the driver enabled: BUG: using smp_processor_id() in preemptible [00000000] code: (udev-worker)/208 caller is loongson3_cpufreq_probe+0x5c/0x250 [loongson3_cpufreq] Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/2f78e4a6d2702a
cpufreq] Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/2f78e4a6d2702ac03c2bf2ed3a0e344e1fa9f967 - https://git.kernel.org/stable/c/2b7ec33e534f7a10033a5cf07794acf48b182bbe
CVE ID: CVE-2024-50179 State: PUBLISHED Published: 2024-11-08T05:24:01.164Z Last Updated: 2025-11-03T22:26:28.089Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ceph: remove the incorrect Fw reference check when dirtying pages When doing the direct-io reads it will also try to mark pages dirty, but for the read path it won't hold the Fw caps and there is case will it get the Fw reference. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c26c5ec832dd9e9dcd0a0a892a485c99889b68f0 - https://git.kernel.org/stable/c/126b567a2ef65fc38a71d832bf1216c56816f231 - ht
c26c5ec832dd9e9dcd0a0a892a485c99889b68f0 - https://git.kernel.org/stable/c/126b567a2ef65fc38a71d832bf1216c56816f231 - https://git.kernel.org/stable/c/f55e003d261baa7c57d51ae5c8ec1f5c26a35c89 - https://git.kernel.org/stable/c/f863bfd0a2c6c99011c62ea71ac04f8e78707da9 - https://git.kernel.org/stable/c/ea98284fc4fb05f276737d2043b02b62be5a8dfb - https://git.kernel.org/stable/c/11ab19d48ab877430eed0c7d83810970bbcbc4f6 - https://git.kernel.org/stable/c/9d4f619153bab7fa59736462967821d6521a38cb - https://git.kernel.org/stable/c/74b302ebad5b43ac17460fa58092d892a3cba6eb - https://git.kernel.org/stable/c/c08dfb1b49492c09cf13838c71897493ea3b424e
CVE ID: CVE-2024-50180 State: PUBLISHED Published: 2024-11-08T05:38:21.657Z Last Updated: 2025-11-03T22:26:29.581Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fbdev: sisfb: Fix strbuf array overflow The values of the variables xres and yres are placed in strbuf. These variables are obtained from strbuf1. The strbuf1 array contains digit characters and a space if the array contains non-digit characters. Then, when executing sprintf(strbuf, "%ux%ux8", xres, yres); more than 16 bytes will be written to strbuf. It is suggested to increase the size of the strbuf array to 24. Found by Linux Verification Center (linuxtesting.org) w