Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
is, we introduce a limit to the size of the list. After considering typical scenarios, such as OpenSM processing, which can handle approximately 100k packets per second, and the 1-second retry timeout for most packets, we set the list size limit to 200k. Packets received beyond this limit are dropped, assuming they are likely timed out by the time they are handled by user-space. Notably, packets queued on the receive list due to reasons like timed-out sends are preserved even when the list is full. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/1288cf1cceb0e6df276e182f5412370fb4169bcb - https://git.kernel.org/stable/c
References: - https://git.kernel.org/stable/c/1288cf1cceb0e6df276e182f5412370fb4169bcb - https://git.kernel.org/stable/c/b4913702419d064ec4c4bbf7270643c95cc89a1b - https://git.kernel.org/stable/c/62349fbf86b5e13b02721bdadf98c29afd1e7b5f - https://git.kernel.org/stable/c/d73cb8862e4d6760ccc94d3b57b9ef6271400607 - https://git.kernel.org/stable/c/63d202d948bb6d3a28cd8e8b96b160fa53e18baa - https://git.kernel.org/stable/c/b8c5f635997f49c625178d1a0cb32a80ed33abe6 - https://git.kernel.org/stable/c/a6627fba793cc75b7365d9504a0095fb2902dda4 - https://git.kernel.org/stable/c/ca0b44e20a6f3032224599f02e7c8fb49525c894
CVE ID: CVE-2024-42146 State: PUBLISHED Published: 2024-07-30T07:46:39.573Z Last Updated: 2025-05-04T09:24:05.952Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Add outer runtime_pm protection to xe_live_ktest@xe_dma_buf Any kunit doing any memory access should get their own runtime_pm outer references since they don't use the standard driver API entries. In special this dma_buf from the same driver. Found by pre-merge CI on adding WARN calls for unprotected inner callers: <6> [318.639739] # xe_dma_buf_kunit: running xe_test_dmabuf_import_same_driver <4> [318.639957] ------------[ cut here ]------------ <4> [318.639967
f_kunit: running xe_test_dmabuf_import_same_driver <4> [318.639957] ------------[ cut here ]------------ <4> [318.639967] xe 0000:4d:00.0: Missing outer runtime PM protection <4> [318.640049] WARNING: CPU: 117 PID: 3832 at drivers/gpu/drm/xe/xe_pm.c:533 xe_pm_runtime_get_noresume+0x48/0x60 [xe] Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/0888d15ea45ba8ef4508edd1123ea5ad95b58994 - https://git.kernel.org/stable/c/f9116f658a6217b101e3b4e89f845775b6fb05d9
CVE ID: CVE-2024-42147 State: PUBLISHED Published: 2024-07-30T07:46:40.483Z Last Updated: 2025-11-03T22:02:12.650Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/debugfs - Fix debugfs uninit process issue During the zip probe process, the debugfs failure does not stop the probe. When debugfs initialization fails, jumping to the error branch will also release regs, in addition to its own rollback operation. As a result, it may be released repeatedly during the regs uninit process. Therefore, the null check needs to be added to the regs uninit process. Additional Analyst Notes: - CVE Program Container: - CISA AD
he null check needs to be added to the regs uninit process. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/eda60520cfe3aba9f088c68ebd5bcbca9fc6ac3c - https://git.kernel.org/stable/c/7fc8d9a525b5c3f8dfa5ed50901e764d8ede7e1e - https://git.kernel.org/stable/c/e0a2d2df9ba7bd6bd7e0a9b6a5e3894f7e8445b3 - https://git.kernel.org/stable/c/8be0913389718e8d27c4f1d4537b5e1b99ed7739
CVE ID: CVE-2024-42148 State: PUBLISHED Published: 2024-07-30T07:46:41.203Z Last Updated: 2025-11-03T22:02:14.116Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bnx2x: Fix multiple UBSAN array-index-out-of-bounds Fix UBSAN warnings that occur when using a system with 32 physical cpu cores or more, or when the user defines a number of Ethernet queues greater than or equal to FP_SB_MAX_E1x using the num_queues module parameter. Currently there is a read/write out of bounds that occurs on the array "struct stats_query_entry query" present inside the "bnx2x_fw_stats_req" struct in "drivers/net/ethernet/broadcom/bnx2x/bnx2x.h". Loo
_query_entry query" present inside the "bnx2x_fw_stats_req" struct in "drivers/net/ethernet/broadcom/bnx2x/bnx2x.h". Looking at the definition of the "struct stats_query_entry query" array: struct stats_query_entry query[FP_SB_MAX_E1x+ BNX2X_FIRST_QUEUE_QUERY_IDX]; FP_SB_MAX_E1x is defined as the maximum number of fast path interrupts and has a value of 16, while BNX2X_FIRST_QUEUE_QUERY_IDX has a value of 3 meaning the array has a total size of 19. Since accesses to "struct stats_query_entry query" are offset-ted by BNX2X_FIRST_QUEUE_QUERY_IDX, that means that the total number of Ethernet queues should not exceed FP_SB_MAX_E1x (16). However one of these queues is reserved for FCOE and thus t
ber of Ethernet queues should not exceed FP_SB_MAX_E1x (16). However one of these queues is reserved for FCOE and thus the number of Ethernet queues should be set to [FP_SB_MAX_E1x -1] (15) if FCOE is enabled or [FP_SB_MAX_E1x] (16) if it is not. This is also described in a comment in the source code in drivers/net/ethernet/broadcom/bnx2x/bnx2x.h just above the Macro definition of FP_SB_MAX_E1x. Below is the part of this explanation that it important for this patch /* * The total number of L2 queues, MSIX vectors and HW contexts (CIDs) is * control by the number of fast-path status blocks supported by the * device (HW/FW). Each fast-path status block (FP-SB) aka non-default * status block re
h status blocks supported by the * device (HW/FW). Each fast-path status block (FP-SB) aka non-default * status block represents an independent interrupts context that can * serve a regular L2 networking queue. However special L2 queues such * as the FCoE queue do not require a FP-SB and other components like * the CNIC may consume FP-SB reducing the number of possible L2 queues * * If the maximum number of FP-SB available is X then: * a. If CNIC is supported it consumes 1 FP-SB thus the max number of * regular L2 queues is Y=X-1 * b. In MF mode the actual number of L2 queues is Y= (X-1/MF_factor) * c. If the FCoE L2 queue is supported the actual number of L2 queues * is Y+1 * d. The number
es is Y= (X-1/MF_factor) * c. If the FCoE L2 queue is supported the actual number of L2 queues * is Y+1 * d. The number of irqs (MSIX vectors) is either Y+1 (one extra for * slow-path interrupts) or Y+2 if CNIC is supported (one additional * FP interrupt context for the CNIC). * e. The number of HW context (CID count) is always X or X+1 if FCoE * L2 queue is supported. The cid for the FCoE L2 queue is always X. */ However this driver also supports NICs that use the E2 controller which can handle more queues due to having more FP-SB represented by FP_SB_MAX_E2. Looking at the commits when the E2 support was added, it was originally using the E1x parameters: commit f2e0899f0f27 ("bnx2x: Add 57
e commits when the E2 support was added, it was originally using the E1x parameters: commit f2e0899f0f27 ("bnx2x: Add 57712 support"). Back then FP_SB_MAX_E2 was set to 16 the same as E1x. However the driver was later updated to take full advantage of the E2 instead of having it be limited to the capabilities of the E1x. But as far as we can tell, the array "stats_query_entry query" was still limited to using the FP-SB available to the E1x cards as part of an oversignt when the driver was updated to take full advantage of the E2, and now with the driver being aware of the greater queue size supported by E2 NICs, it causes the UBSAN warnings seen in the stack traces below. This patch increase
reater queue size supported by E2 NICs, it causes the UBSAN warnings seen in the stack traces below. This patch increases the size of the "stats_query_entry query" array by replacing FP_SB_MAX_E1x with FP_SB_MAX_E2 to be large enough to handle both types of NICs. Stack traces: UBSAN: array-index-out-of-bounds in drivers/net/ethernet/broadcom/bnx2x/bnx2x_stats.c:1529:11 index 20 is out of range for type 'stats_query_entry [19]' CPU: 12 PID: 858 Comm: systemd-network Not tainted 6.9.0-060900rc7-generic #202405052133 Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 ---truncated--- Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.or
cated--- Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/cfb04472ce33bee2579caf4dc9f4242522f6e26e - https://git.kernel.org/stable/c/cbe53087026ad929cd3950508397e8892a6a2a0f - https://git.kernel.org/stable/c/8b17cec33892a66bbd71f8d9a70a45e2072ae84f - https://git.kernel.org/stable/c/0edae06b4c227bcfaf3ce21208d49191e1009d3b - https://git.kernel.org/stable/c/9504a1550686f53b0bab4cab31d435383b1ee2ce - https://git.kernel.org/stable/c/f1313ea92f82451923e28ab45a4aaa0e70e80b98 - https://git.kernel.org/stable/c/b9ea38e767459111a511ed4fb74abc37db95a59d - https://git.kernel.org/stable/c/134061163ee5ca4759de5c24ca3bd71608891ba7
CVE ID: CVE-2024-42149 State: PUBLISHED Published: 2024-07-30T07:46:42.133Z Last Updated: 2025-05-04T09:24:10.572Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fs: don't misleadingly warn during thaw operations The block device may have been frozen before it was claimed by a filesystem. Concurrently another process might try to mount that frozen block device and has temporarily claimed the block device for that purpose causing a concurrent fs_bdev_thaw() to end up here. The mounter is already about to abort mounting because they still saw an elevanted bdev->bd_fsfreeze_count so get_bdev_super() will return NULL in that case.
mounting because they still saw an elevanted bdev->bd_fsfreeze_count so get_bdev_super() will return NULL in that case. For example, P1 calls dm_suspend() which calls into bdev_freeze() before the block device has been claimed by the filesystem. This brings bdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() is required. Now P2 tries to mount that frozen block device. It claims it and checks bdev->bd_fsfreeze_count. As it's elevated it aborts mounting. In the meantime P3 called dm_resume(). P3 sees that the block device is already claimed by a filesystem and calls into fs_bdev_thaw(). P3 takes a passive reference and realizes that the filesystem isn't ready yet. P3 puts itself to
s into fs_bdev_thaw(). P3 takes a passive reference and realizes that the filesystem isn't ready yet. P3 puts itself to sleep to wait for the filesystem to become ready. P2 now puts the last active reference to the filesystem and marks it as dying. P3 gets woken, sees that the filesystem is dying and get_bdev_super() fails. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/25b1e3906e050d452427bc51620bb7f0a591373a - https://git.kernel.org/stable/c/2ae4db5647d807efb6a87c09efaa6d1db9c905d7
CVE ID: CVE-2024-42150 State: PUBLISHED Published: 2024-07-30T07:46:43.031Z Last Updated: 2025-05-04T12:57:47.297Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: txgbe: remove separate irq request for MSI and INTx When using MSI or INTx interrupts, request_irq() for pdev->irq will conflict with request_threaded_irq() for txgbe->misc.irq, to cause system crash. So remove txgbe_request_irq() for MSI/INTx case, and rename txgbe_request_msix_irqs() since it only request for queue irqs. Add wx->misc_irq_domain to determine whether the driver creates an IRQ domain and threaded request the IRQs. Additional Analyst Notes: - CVE Pr
to determine whether the driver creates an IRQ domain and threaded request the IRQs. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/850103ebe6b062ee0ab0f6670205f861acc76ace - https://git.kernel.org/stable/c/bd07a98178462e7a02ed2bf7dec90a00944c1da5
CVE ID: CVE-2024-42151 State: PUBLISHED Published: 2024-07-30T07:46:43.969Z Last Updated: 2025-05-04T09:24:13.803Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bpf: mark bpf_dummy_struct_ops.test_1 parameter as nullable Test case dummy_st_ops/dummy_init_ret_value passes NULL as the first parameter of the test_1() function. Mark this parameter as nullable to make verifier aware of such possibility. Otherwise, NULL check in the test_1() code: SEC("struct_ops/test_1") int BPF_PROG(test_1, struct bpf_dummy_ops_state *state) { if (!state) return ...; ... access state ... } Might be removed by verifier, thus triggering NULL pointer
tate *state) { if (!state) return ...; ... access state ... } Might be removed by verifier, thus triggering NULL pointer dereference under certain conditions. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/7f79097b0de97a486b137b750d7dd7b20b519d23 - https://git.kernel.org/stable/c/1479eaff1f16983d8fda7c5a08a586c21891087d
CVE ID: CVE-2024-42152 State: PUBLISHED Published: 2024-07-30T07:46:44.795Z Last Updated: 2025-11-03T22:02:15.586Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nvmet: fix a possible leak when destroy a ctrl during qp establishment In nvmet_sq_destroy we capture sq->ctrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl->sqs and sq->ctrl (for nvme-loop primarily), and drop the final reference on the ctrl. However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) conc
r, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But *before* kill_and_confirm of sq->ref (i.e. the admin connect managed to get an sq live reference). In this case, sq->ctrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl. Solve this by re-capturing the sq->ctrl after all inflight request has completed, where for sure sq->ctrl reference is final, and move forward based on that. This issue was observed in an environment with many hosts connecting multiple ctrls
nal, and move forward based on that. This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/2f3c22b1d3d7e86712253244797a651998c141fa - https://git.kernel.org/stable/c/b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5 - https://git.kernel.org/stable/c/940a71f08ef153ef807f751310b0648d1fa5d0da - https://git.kernel.org/stable/c/5502c1f1d0d7472706cc1f201aecf1c935d302d1 - https://git.kernel.org/stable/c/818004f2a380420c19872171be716174d4985e33 - https://git.kernel.org/stable
cf1c935d302d1 - https://git.kernel.org/stable/c/818004f2a380420c19872171be716174d4985e33 - https://git.kernel.org/stable/c/c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4
CVE ID: CVE-2024-42153 State: PUBLISHED Published: 2024-07-30T07:46:45.724Z Last Updated: 2025-11-03T22:02:17.048Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: i2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr When del_timer_sync() is called in an interrupt context it throws a warning because of potential deadlock. The timer is used only to exit from wait_for_completion() after a timeout so replacing the call with wait_for_completion_timeout() allows to remove the problematic timer and its related functions altogether. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: Referen
nd its related functions altogether. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a349e5ab4dc9954746e836cd10b407ce48f9b2f6 - https://git.kernel.org/stable/c/effe0500afda017a86c94482b1e36bc37586c9af - https://git.kernel.org/stable/c/2849a1b747cf37aa5b684527104d3a53f1e296d2 - https://git.kernel.org/stable/c/3503372d0bf7b324ec0bd6b90606703991426176 - https://git.kernel.org/stable/c/3d32327f5cfc087ee3922a3bcdcc29880dcdb50f - https://git.kernel.org/stable/c/92e494a7568b60ae80d57fc0deafcaf3a4029ab3 - https://git.kernel.org/stable/c/27cd3873fa76ebeb9f948baae40cb9a6d8692289 - https://git.kernel.org/stable/c/f63b94be6942ba82
ps://git.kernel.org/stable/c/27cd3873fa76ebeb9f948baae40cb9a6d8692289 - https://git.kernel.org/stable/c/f63b94be6942ba82c55343e196bd09b53227618e
CVE ID: CVE-2024-42154 State: PUBLISHED Published: 2024-07-30T07:46:51.456Z Last Updated: 2025-11-03T22:02:18.507Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: tcp_metrics: validate source addr length I don't see anything checking that TCP_METRICS_ATTR_SADDR_IPV4 is at least 4 bytes long, and the policy doesn't have an entry for this attribute at all (neither does it for IPv6 but v6 is manually validated). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/19d997b59fa1fd7a02e770ee0881c0652b9c32c9 - https://git.kernel.org/stable/c/2a2e79dbe2236a1289412d2044
ernel.org/stable/c/19d997b59fa1fd7a02e770ee0881c0652b9c32c9 - https://git.kernel.org/stable/c/2a2e79dbe2236a1289412d2044994f7ab419b44c - https://git.kernel.org/stable/c/cdffc358717e436bb67122bb82c1a2a26e050f98 - https://git.kernel.org/stable/c/ef7c428b425beeb52b894e16f1c4b629d6cebfb6 - https://git.kernel.org/stable/c/31f03bb04146c1c6df6c03e9f45401f5f5a985d3 - https://git.kernel.org/stable/c/8c2debdd170e395934ac0e039748576dfde14e99 - https://git.kernel.org/stable/c/3d550dd5418729a6e77fe7721d27adea7152e321 - https://git.kernel.org/stable/c/66be40e622e177316ae81717aa30057ba9e61dff
CVE ID: CVE-2024-42155 State: PUBLISHED Published: 2024-07-30T07:46:57.729Z Last Updated: 2025-05-04T09:24:19.111Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe copies of protected- and secure-keys Although the clear-key of neither protected- nor secure-keys is accessible, this key material should only be visible to the calling process. So wipe all copies of protected- or secure-keys from stack, even in case of an error. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/c746f7ced4ad88ee48d0b6c92710e4674403185b - https://git.kernel.org/stabl
t: References: - https://git.kernel.org/stable/c/c746f7ced4ad88ee48d0b6c92710e4674403185b - https://git.kernel.org/stable/c/f2ebdadd85af4f4d0cae1e5d009c70eccc78c207
CVE ID: CVE-2024-42156 State: PUBLISHED Published: 2024-07-30T07:46:58.513Z Last Updated: 2025-05-20T14:27:36.396Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe copies of clear-key structures on failure Wipe all sensitive data from stack for all IOCTLs, which convert a clear-key into a protected- or secure-key. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/a891938947f4427f98cb1ce54f27223501efe750 - https://git.kernel.org/stable/c/7f6243edd901b75aaece326c90a1cc0dcb60cc3d - https://git.kernel.org/stable/c/d65d76a44ffe74c73298ada25b0f57868
rg/stable/c/7f6243edd901b75aaece326c90a1cc0dcb60cc3d - https://git.kernel.org/stable/c/d65d76a44ffe74c73298ada25b0f578680576073
CVE ID: CVE-2024-42157 State: PUBLISHED Published: 2024-07-30T07:46:59.362Z Last Updated: 2025-11-03T22:02:19.958Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Wipe sensitive data on failure Wipe sensitive data from stack also if the copy_to_user() fails. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6e2e374403bf73140d0efc9541cb1b3bea55ac02 - https://git.kernel.org/stable/c/b5eb9176ebd4697bc248bf8d145e66d782cf5250 - https://git.kernel.org/stable/c/93c034c4314bc4c4450a3869cd5da298502346ad - https://git.kernel.org/stable/c/4889f117755b2f18c23
//git.kernel.org/stable/c/93c034c4314bc4c4450a3869cd5da298502346ad - https://git.kernel.org/stable/c/4889f117755b2f18c23045a0f57977f3ec130581 - https://git.kernel.org/stable/c/c51795885c801b6b7e976717e0d6d45b1e5be0f0 - https://git.kernel.org/stable/c/90a01aefb84b09ccb6024d75d85bb8f620bd3487 - https://git.kernel.org/stable/c/c44a2151e5d21c66b070a056c26471f30719b575 - https://git.kernel.org/stable/c/1d8c270de5eb74245d72325d285894a577a945d9
CVE ID: CVE-2024-42158 State: PUBLISHED Published: 2024-07-30T07:47:00.343Z Last Updated: 2025-05-04T09:24:22.974Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/pkey: Use kfree_sensitive() to fix Coccinelle warnings Replace memzero_explicit() and kfree() with kfree_sensitive() to fix warnings reported by Coccinelle: WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1506) WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1643) WARNING opportunity for kfree_sensitive/kvfree_sensitive (line 1770) Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.ke
ive (line 1770) Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/62151a0acde90823bdfa991d598c85cf4b1d387d - https://git.kernel.org/stable/c/22e6824622e8a8889df0f8fc4ed5aea0e702a694
CVE ID: CVE-2024-42159 State: PUBLISHED Published: 2024-07-30T07:47:01.276Z Last Updated: 2025-11-03T22:02:21.409Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Sanitise num_phys Information is stored in mr_sas_port->phy_mask, values larger then size of this field shouldn't be allowed. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b869ec89d2ee923d46608b76e54c006680c9b4df - https://git.kernel.org/stable/c/586b41060113ae43032ec6c4a16d518cef5da6e0 - https://git.kernel.org/stable/c/c8707901b53a48106d7501bdbd0350cefaefa4cf - https://git.kernel
032ec6c4a16d518cef5da6e0 - https://git.kernel.org/stable/c/c8707901b53a48106d7501bdbd0350cefaefa4cf - https://git.kernel.org/stable/c/3668651def2c1622904e58b0280ee93121f2b10b
CVE ID: CVE-2024-42160 State: PUBLISHED Published: 2024-07-30T07:47:02.208Z Last Updated: 2025-11-03T22:02:22.875Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: f2fs: check validation of fault attrs in f2fs_build_fault_attr() - It missed to check validation of fault attrs in parse_options(), let's fix to add check condition in f2fs_build_fault_attr(). - Use f2fs_build_fault_attr() in __sbi_store() to clean up code. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/6e5b601706ce05d94338cad598736d96bb8096c8 - https://git.kernel.org/stable/c/bc84dd2c33e0c10fd9
://git.kernel.org/stable/c/6e5b601706ce05d94338cad598736d96bb8096c8 - https://git.kernel.org/stable/c/bc84dd2c33e0c10fd90d60f0cfc0bfb504d4692d - https://git.kernel.org/stable/c/44958ca9e400f57bd0478115519ffc350fcee61e - https://git.kernel.org/stable/c/ecb641f424d6d1f055d149a15b892edcc92c504b - https://git.kernel.org/stable/c/4ed886b187f47447ad559619c48c086f432d2b77