Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
tps://git.kernel.org/stable/c/72ee32d0907364104fbcf4f68dd5ae63cd8eae9e - https://git.kernel.org/stable/c/08ae395ea22fb3d9b318c8bde28c0dfd2f5fa4d2
CVE ID: CVE-2024-47721 State: PUBLISHED Published: 2024-10-21T11:53:50.861Z Last Updated: 2025-05-04T09:38:16.712Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: remove unused C2H event ID RTW89_MAC_C2H_FUNC_READ_WOW_CAM to prevent out-of-bounds reading The handler of firmware C2H event RTW89_MAC_C2H_FUNC_READ_WOW_CAM isn't implemented, but driver expects number of handlers is NUM_OF_RTW89_MAC_C2H_FUNC_WOW causing out-of-bounds access. Fix it by removing ID. Addresses-Coverity-ID: 1598775 ("Out-of-bounds read") Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/10463308
-bounds read") Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/10463308b9454f534d03300cf679bc4b3d078f46 - https://git.kernel.org/stable/c/2c9c2d1a20916589497a7facbea3e82cabec4ab8 - https://git.kernel.org/stable/c/56310ddb50b190b3390fdc974aec455d0a516bd2
CVE ID: CVE-2024-47722 State: REJECTED Published: 2024-10-21T12:13:56.954Z Last Updated: 2024-10-21T12:58:26.199Z Description: No description available.
CVE ID: CVE-2024-47723 State: PUBLISHED Published: 2024-10-21T12:13:57.614Z Last Updated: 2025-11-03T22:21:22.096Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp->db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp->db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or sa
added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/d1017d2a0f3f16dc1db5120e7ddbe7c6680425b0 - https://git.kernel.org/stable/c/5ad6284c8d433f8a213111c5c44ead4d9705b622 - https://git.kernel.org/stable/c/0338e66cba272351ca9d7d03f3628e390e70963b - https://git.kernel.org/stable/c/ead82533278502428883085a787d5a00f15e5eb9 - https://git.kernel.org/stable/c/6ce8b6ab44a8b5918c0ee373d4ad19d19017931b - https://git.kernel.org/stable/c/c1ba4b8ca799ff
ttps://git.kernel.org/stable/c/6ce8b6ab44a8b5918c0ee373d4ad19d19017931b - https://git.kernel.org/stable/c/c1ba4b8ca799ff1d99d01f37d7ccb7d5ba5533d2 - https://git.kernel.org/stable/c/128d5cfdcf844cb690c9295a3a1c1114c21fc15a - https://git.kernel.org/stable/c/96855f40e152989c9e7c20c4691ace5581098acc - https://git.kernel.org/stable/c/e63866a475562810500ea7f784099bfe341e761a
CVE ID: CVE-2024-47724 State: PUBLISHED Published: 2024-10-21T12:13:58.267Z Last Updated: 2025-05-04T09:38:19.543Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: use work queue to process beacon tx event Commit 3a415daa3e8b ("wifi: ath11k: add P2P IE in beacon template") from Feb 28, 2024 (linux-next), leads to the following Smatch static checker warning: drivers/net/wireless/ath/ath11k/wmi.c:1742 ath11k_wmi_p2p_go_bcn_ie() warn: sleeping in atomic context The reason is that ath11k_bcn_tx_status_event() will directly call might sleep function ath11k_wmi_cmd_send() during RCU read-side critical sections. The call t
event() will directly call might sleep function ath11k_wmi_cmd_send() during RCU read-side critical sections. The call trace is like: ath11k_bcn_tx_status_event() -> rcu_read_lock() -> ath11k_mac_bcn_tx_event() -> ath11k_mac_setup_bcn_tmpl() …… -> ath11k_wmi_bcn_tmpl() -> ath11k_wmi_cmd_send() -> rcu_read_unlock() Commit 886433a98425 ("ath11k: add support for BSS color change") added the ath11k_mac_bcn_tx_event(), commit 01e782c89108 ("ath11k: fix warning of RCU usage for ath11k_mac_get_arvif_by_vdev_id()") added the RCU lock to avoid warning but also introduced this BUG. Use work queue to avoid directly calling ath11k_mac_bcn_tx_event() during RCU critical sections. No need to worry about t
se work queue to avoid directly calling ath11k_mac_bcn_tx_event() during RCU critical sections. No need to worry about the deletion of vif because cancel_work_sync() will drop the work if it doesn't start or block vif deletion until the running work is done. Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/dbd51da69dda1137723b8f66460bf99a9dac8dd2 - https://git.kernel.org/stable/c/6db232905e094e64abff1f18249905d068285e09 - https://git.kernel.org/stable/c/177b49dbf9c1d8f9f25a22ffafa416fc2c8aa6a3
CVE ID: CVE-2024-47725 State: REJECTED Published: 2024-10-21T12:13:58.942Z Last Updated: 2024-10-23T06:07:36.698Z Description: No description available.
CVE ID: CVE-2024-47726 State: PUBLISHED Published: 2024-10-21T12:13:59.615Z Last Updated: 2025-11-03T19:31:22.106Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait dio completion It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/7be13b73409b553d9d9a6cbb042b4d19e2631cc7 - https://git.kernel.org/stable/c/3aa5254d80969cb576601fb9fec7a188cc8dc169 - https://git.kernel.org/stable/c/
19e2631cc7 - https://git.kernel.org/stable/c/3aa5254d80969cb576601fb9fec7a188cc8dc169 - https://git.kernel.org/stable/c/f81302decd64245bb1bd154ecae0f65a9ee21f04 - https://git.kernel.org/stable/c/c2a7fc514637f640ff55c3f3e3ed879970814a3f - https://git.kernel.org/stable/c/e3db757ff9b7101ae68650ac5f6dd5743b68164e - https://git.kernel.org/stable/c/96cfeb0389530ae32ade8a48ae3ae1ac3b6c009d
CVE ID: CVE-2024-47727 State: PUBLISHED Published: 2024-10-21T12:14:00.330Z Last Updated: 2025-11-03T22:21:23.601Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Fix "in-kernel MMIO" check TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not. However, userspace can deceive the kernel into performing MMIO on its behalf. For example, if userspace can point a syscall to an MMIO address, syscall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO. Ensure
scall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO. Ensure that the target MMIO address is within the kernel before decoding instruction. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/25703a3c980e21548774eea8c8a87a75c5c8f58c - https://git.kernel.org/stable/c/4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee - https://git.kernel.org/stable/c/18ecd5b74682839e7cdafb7cd1ec106df7baa18c - https://git.kernel.org/stable/c/bca2e29f7e26ce7c3522f8b324c0bd85612f68e3 - https://git.kernel.org/stable/c/d4fc4d01471528da8a9797a065982e05090e1d81
CVE ID: CVE-2024-47728 State: PUBLISHED Published: 2024-10-21T12:14:01.012Z Last Updated: 2025-11-03T22:21:25.047Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error For all non-tracing helpers which formerly had ARG_PTR_TO_{LONG,INT} as input arguments, zero the value for the case of an error as otherwise it could leak memory. For tracing, it is not needed given CAP_PERFMON can already read all kernel memory anyway hence bpf_get_func_arg() and bpf_get_func_ret() is skipped in here. Also, the MTU helpers mtu_len pointer value is being written but also read. Technically, t
unc_ret() is skipped in here. Also, the MTU helpers mtu_len pointer value is being written but also read. Technically, the MEM_UNINIT should not be there in order to always force init. Removing MEM_UNINIT needs more verifier rework though: MEM_UNINIT right now implies two things actually: i) write into memory, ii) memory does not have to be initialized. If we lift MEM_UNINIT, it then becomes: i) read into memory, ii) memory must be initialized. This means that for bpf_*_check_mtu() we're readding the issue we're trying to fix, that is, it would then be able to write back into things like .rodata BPF maps. Follow-up work will rework the MEM_UNINIT semantics such that the intent can be better
to things like .rodata BPF maps. Follow-up work will rework the MEM_UNINIT semantics such that the intent can be better expressed. For now just clear the *mtu_len on error path which can be lifted later again. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8397bf78988f3ae9dbebb0200189a62a57264980 - https://git.kernel.org/stable/c/a634fa8e480ac2423f86311a602f6295df2c8ed0 - https://git.kernel.org/stable/c/599d15b6d03356a97bff7a76155c5604c42a2962 - https://git.kernel.org/stable/c/594a9f5a8d2de2573a856e506f77ba7dd2cefc6a - https://git.kernel.org/stable/c/4b3786a6c5397dc220b1483d8e2f4867743e966f
CVE ID: CVE-2024-47729 State: PUBLISHED Published: 2024-10-21T12:14:01.685Z Last Updated: 2025-05-04T09:38:25.108Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Use reserved copy engine for user binds on faulting devices User binds map to engines with can fault, faults depend on user binds completion, thus we can deadlock. Avoid this by using reserved copy engine for user binds on faulting devices. While we are here, normalize bind queue creation with a helper. v2: - Pass in extensions to bind queue creation (CI) v3: - s/resevered/reserved (Lucas) - Fix NULL hwe check (Jonathan) Additional Analyst Notes: - CISA ADP Vul
reation (CI) v3: - s/resevered/reserved (Lucas) - Fix NULL hwe check (Jonathan) Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/439fc1e569c57669dbb842d0a77c7ba0a82a9f5d - https://git.kernel.org/stable/c/852856e3b6f679c694dd5ec41e5a3c11aa46640b
CVE ID: CVE-2024-47730 State: PUBLISHED Published: 2024-10-21T12:14:02.378Z Last Updated: 2025-11-03T22:21:26.550Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/qm - inject error before stopping queue The master ooo cannot be completely closed when the accelerator core reports memory error. Therefore, the driver needs to inject the qm error to close the master ooo. Currently, the qm error is injected after stopping queue, memory may be released immediately after stopping queue, causing the device to access the released memory. Therefore, error is injected to close master ooo before stopping queue to ensure th
evice to access the released memory. Therefore, error is injected to close master ooo before stopping queue to ensure that the device does not access the released memory. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/85e81103033324d7a271dafb584991da39554a89 - https://git.kernel.org/stable/c/801d64177faaec184cee1e1aa4d8487df1364a54 - https://git.kernel.org/stable/c/98d3be34c9153eceadb56de50d9f9347e88d86e4 - https://git.kernel.org/stable/c/aa3e0db35a60002fb34ef0e4ad203aa59fd00203 - https://git.kernel.org/stable/c/f8024f12752e32ffbbf59e1c09d949f977ff743f - https://git.kernel.org/stable/c/c5f5b813e546f7fe133539c3d7a5086c
org/stable/c/f8024f12752e32ffbbf59e1c09d949f977ff743f - https://git.kernel.org/stable/c/c5f5b813e546f7fe133539c3d7a5086cc8dd2aa1 - https://git.kernel.org/stable/c/b04f06fc0243600665b3b50253869533b7938468
CVE ID: CVE-2024-47731 State: PUBLISHED Published: 2024-10-21T12:14:03.184Z Last Updated: 2025-11-03T22:21:28.034Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drivers/perf: Fix ali_drw_pmu driver interrupt status clearing The alibaba_uncore_pmu driver forgot to clear all interrupt status in the interrupt processing function. After the PMU counter overflow interrupt occurred, an interrupt storm occurred, causing the system to hang. Therefore, clear the correct interrupt status in the interrupt handling function to fix it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.ker
ion to fix it. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/24f30b34ff76648d26872dd4eaa002f074225058 - https://git.kernel.org/stable/c/3b839d4619042b02eecdfc986484ac6e6be6acbf - https://git.kernel.org/stable/c/062b7176e484678b2c9072d28fbecea47846b274 - https://git.kernel.org/stable/c/85702fddba70d2b63f5646793d77de2ad4fc3784 - https://git.kernel.org/stable/c/a3dd920977dccc453c550260c4b7605b280b79c3
CVE ID: CVE-2024-47732 State: PUBLISHED Published: 2024-10-21T12:14:03.863Z Last Updated: 2025-05-04T09:38:29.225Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: iaa - Fix potential use after free bug The free_device_compression_mode(iaa_device, device_mode) function frees "device_mode" but it iss passed to iaa_compression_modes[i]->free() a few lines later resulting in a use after free. The good news is that, so far as I can tell, nothing implements the ->free() function and the use after free happens in dead code. But, with this fix, when something does implement it, we'll be ready. :) Additional Analyst Notes: - CISA
in dead code. But, with this fix, when something does implement it, we'll be ready. :) Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/b5d534b473e2c8d3e4560be2dd6c12a8eb9d61e9 - https://git.kernel.org/stable/c/c66f0be993ba52410edab06124c54ecf143b05c1 - https://git.kernel.org/stable/c/e0d3b845a1b10b7b5abdad7ecc69d45b2aab3209
CVE ID: CVE-2024-47733 State: PUBLISHED Published: 2024-10-21T12:14:04.544Z Last Updated: 2025-05-04T09:38:35.725Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: netfs: Delete subtree of 'fs/netfs' when netfs module exits In netfs_init() or fscache_proc_init(), we create dentry under 'fs/netfs', but in netfs_exit(), we only delete the proc entry of 'fs/netfs' without deleting its subtree. This triggers the following WARNING: ================================================================== remove_proc_entry: removing non-empty directory 'fs/netfs', leaking at least 'requests' WARNING: CPU: 4 PID: 566 at fs/proc/generic.c:717 r
removing non-empty directory 'fs/netfs', leaking at least 'requests' WARNING: CPU: 4 PID: 566 at fs/proc/generic.c:717 remove_proc_entry+0x160/0x1c0 Modules linked in: netfs(-) CPU: 4 UID: 0 PID: 566 Comm: rmmod Not tainted 6.11.0-rc3 #860 RIP: 0010:remove_proc_entry+0x160/0x1c0 Call Trace: <TASK> netfs_exit+0x12/0x620 [netfs] __do_sys_delete_module.isra.0+0x14c/0x2e0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e ================================================================== Therefore use remove_proc_subtree() instead of remove_proc_entry() to fix the above problem. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/603f95
e above problem. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/603f95cefbee06a31b03137b777f03e3c2163d72 - https://git.kernel.org/stable/c/7a9eaf97d56625e55b31a7beb558e1ee185ca461 - https://git.kernel.org/stable/c/3c58a9575e02c2b90a3180007d57105ceaa7c246
CVE ID: CVE-2024-47734 State: PUBLISHED Published: 2024-10-21T12:14:05.195Z Last Updated: 2025-11-03T22:21:29.564Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: bonding: Fix unnecessary warnings and logs from bond_xdp_get_xmit_slave() syzbot reported a WARNING in bond_xdp_get_xmit_slave. To reproduce this[1], one bond device (bond1) has xdpdrv, which increases bpf_master_redirect_enabled_key. Another bond device (bond0) which is unsupported by XDP but its slave (veth3) has xdpgeneric that returns XDP_TX. This triggers WARN_ON_ONCE() from the xdp_master_redirect(). To reduce unnecessary warnings and improve log management, we n
triggers WARN_ON_ONCE() from the xdp_master_redirect(). To reduce unnecessary warnings and improve log management, we need to delete the WARN_ON_ONCE() and add ratelimit to the netdev_err(). [1] Steps to reproduce: # Needs tx_xdp with return XDP_TX; ip l add veth0 type veth peer veth1 ip l add veth3 type veth peer veth4 ip l add bond0 type bond mode 6 # BOND_MODE_ALB, unsupported by XDP ip l add bond1 type bond # BOND_MODE_ROUNDROBIN by default ip l set veth0 master bond1 ip l set bond1 up # Increases bpf_master_redirect_enabled_key ip l set dev bond1 xdpdrv object tx_xdp.o section xdp_tx ip l set veth3 master bond0 ip l set bond0 up ip l set veth4 up # Triggers WARN_ON_ONCE() from the xdp_
o section xdp_tx ip l set veth3 master bond0 ip l set bond0 up ip l set veth4 up # Triggers WARN_ON_ONCE() from the xdp_master_redirect() ip l set veth3 xdpgeneric object tx_xdp.o section xdp_tx Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c1be35e774f8ed415e01209fddd963c5a74e8e9f - https://git.kernel.org/stable/c/6b64197b4bf1a5703a8b105367baf20f1e627a75 - https://git.kernel.org/stable/c/ccd3e6ff05e5236d1b9535f23f3e6622e0bb32b8 - https://git.kernel.org/stable/c/72e2c0825a480e19ee999cee9d018850d38c82b9 - https://git.kernel.org/stable/c/57b5fba55c6f8b1d83312a34bd656166fcd95658 - https://git.kernel.org/stable/c/0cbfd45f
b9 - https://git.kernel.org/stable/c/57b5fba55c6f8b1d83312a34bd656166fcd95658 - https://git.kernel.org/stable/c/0cbfd45fbcf0cb26d85c981b91c62fe73cdee01c
CVE ID: CVE-2024-47735 State: PUBLISHED Published: 2024-10-21T12:14:05.876Z Last Updated: 2025-11-03T22:21:31.011Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold. This was discovered through the lock debugging, and the corresponding log is as follows: raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace: warn_bogus_irq_restore+0x30/0x40 _raw_spin_unlock_i
/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace: warn_bogus_irq_restore+0x30/0x40 _raw_spin_unlock_irqrestore+0x84/0xc8 add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2] hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2] hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2] create_qp+0x138/0x258 ib_create_qp_kernel+0x50/0xe8 create_mad_qp+0xa8/0x128 ib_mad_port_open+0x218/0x448 ib_mad_init_device+0x70/0x1f8 add_client_context+0xfc/0x220 enable_device_and_get+0xd0/0x140 ib_register_device.part.0+0xf4/0x1c8 ib_register_device+0x34/0x50 hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2] hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2] __hns_roce_hw_v2_init_instance+0x7c/0x1d0
_device+0x174/0x3d0 [hns_roce_hw_v2] hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2] __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2] hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/07f0f643d7e570dbe8ef6f5c3367a43e3086a335 - https://git.kernel.org/stable/c/29c0f546d3fd66238b42cf25bcd5f193bb1cf794 - https://git.kernel.org/stable/c/425589d4af09c49574bd71ac31f811362a5126c3 - https://git.kernel.org/stable/c/094a1821903f33fb91de4b71087773ee16aeb3a0 - https://git.kernel.org/stable/c/2656336a84fcb6802f6e6c233f4661891deea24f - https://git.kernel.org/stable/c/a1a3403b
a0 - https://git.kernel.org/stable/c/2656336a84fcb6802f6e6c233f4661891deea24f - https://git.kernel.org/stable/c/a1a3403bb1826c8ec787f0d60c3e7b54f419129e - https://git.kernel.org/stable/c/74d315b5af180220d561684d15897730135733a6
CVE ID: CVE-2024-47736 State: PUBLISHED Published: 2024-10-21T12:14:06.530Z Last Updated: 2025-05-04T09:38:39.956Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: erofs: handle overlapped pclusters out of crafted images properly syzbot reported a task hang issue due to a deadlock case where it is waiting for the folio lock of a cached folio that will be used for cache I/Os. After looking into the crafted fuzzed image, I found it's formed with several overlapped big pclusters as below: Ext: logical offset | length : physical offset | length 0: 0.. 16384 | 16384 : 151552.. 167936 | 16384 1: 16384.. 32768 | 16384 : 155648.. 172032
th : physical offset | length 0: 0.. 16384 | 16384 : 151552.. 167936 | 16384 1: 16384.. 32768 | 16384 : 155648.. 172032 | 16384 2: 32768.. 49152 | 16384 : 537223168.. 537239552 | 16384 ... Here, extent 0/1 are physically overlapped although it's entirely _impossible_ for normal filesystem images generated by mkfs. First, managed folios containing compressed data will be marked as up-to-date and then unlocked immediately (unlike in-place folios) when compressed I/Os are complete. If physical blocks are not submitted in the incremental order, there should be separate BIOs to avoid dependency issues. However, the current code mis-arranges z_erofs_fill_bio_vec() and BIO submission which causes u
avoid dependency issues. However, the current code mis-arranges z_erofs_fill_bio_vec() and BIO submission which causes unexpected BIO waits. Second, managed folios will be connected to their own pclusters for efficient inter-queries. However, this is somewhat hard to implement easily if overlapped big pclusters exist. Again, these only appear in fuzzed images so let's simply fall back to temporary short-lived pages for correctness. Additionally, it justifies that referenced managed folios cannot be truncated for now and reverts part of commit 2080ca1ed3e4 ("erofs: tidy up `struct z_erofs_bvec`") for simplicity although it shouldn't be any difference. Additional Analyst Notes: - CISA ADP Vuln
struct z_erofs_bvec`") for simplicity although it shouldn't be any difference. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/1bf7e414cac303c9aec1be67872e19be8b64980c - https://git.kernel.org/stable/c/b9b30af0e86ffb485301ecd83b9129c9dfb7ebf8 - https://git.kernel.org/stable/c/9cfa199bcbbbba31cbf97b2786f44f4464f3f29a - https://git.kernel.org/stable/c/9e2f9d34dd12e6e5b244ec488bcebd0c2d566c50
CVE ID: CVE-2024-47737 State: PUBLISHED Published: 2024-10-21T12:14:07.168Z Last Updated: 2025-11-03T22:21:32.511Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfsd: call cache_put if xdr_reserve_space returns NULL If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get. Reviwed-by: Jeff Layton <jlayton@kernel.org> Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/3e8081ebff12bec1347deaceb6bce0765cce54df - https://git.ker