Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
able/c/423c6939758fb3b9cf5abbd1e7792068a5c4ae8c - https://git.kernel.org/stable/c/1f79bc8ae81c05eb112a53f981cb2c244ee50d02 - https://git.kernel.org/stable/c/06b7cb0194bd1ede0dd27f3a946e7c0279fba44a - https://git.kernel.org/stable/c/2038cd15eacdf7512755c27686822e0052eb9042 - https://git.kernel.org/stable/c/5946fbf48355f5a8caeff72580c7658da5966b86 - https://git.kernel.org/stable/c/b25b60d076164edb3025e85aabd2cf50a5215b91 - https://git.kernel.org/stable/c/49bfcbfd989a8f1f23e705759a6bb099de2cff9f
CVE ID: CVE-2021-47250 State: PUBLISHED Published: 2024-05-21T14:19:46.886Z Last Updated: 2025-05-04T07:07:08.871Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix memory leak in netlbl_cipsov4_add_std Reported by syzkaller: BUG: memory leak unreferenced object 0xffff888105df7000 (size 64): comm "syz-executor842", pid 360, jiffies 4294824824 (age 22.546s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000e67ed558>] kmalloc include/linux/slab.h:590 [inline] [<00000000e67ed558>] kzalloc incl
............ backtrace: [<00000000e67ed558>] kmalloc include/linux/slab.h:590 [inline] [<00000000e67ed558>] kzalloc include/linux/slab.h:720 [inline] [<00000000e67ed558>] netlbl_cipsov4_add_std net/netlabel/netlabel_cipso_v4.c:145 [inline] [<00000000e67ed558>] netlbl_cipsov4_add+0x390/0x2340 net/netlabel/netlabel_cipso_v4.c:416 [<0000000006040154>] genl_family_rcv_msg_doit.isra.0+0x20e/0x320 net/netlink/genetlink.c:739 [<00000000204d7a1c>] genl_family_rcv_msg net/netlink/genetlink.c:783 [inline] [<00000000204d7a1c>] genl_rcv_msg+0x2bf/0x4f0 net/netlink/genetlink.c:800 [<00000000c0d6a995>] netlink_rcv_skb+0x134/0x3d0 net/netlink/af_netlink.c:2504 [<00000000d78b9d2c>] genl_rcv+0x24/0x40 net/ne
00000c0d6a995>] netlink_rcv_skb+0x134/0x3d0 net/netlink/af_netlink.c:2504 [<00000000d78b9d2c>] genl_rcv+0x24/0x40 net/netlink/genetlink.c:811 [<000000009733081b>] netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline] [<000000009733081b>] netlink_unicast+0x4a0/0x6a0 net/netlink/af_netlink.c:1340 [<00000000d5fd43b8>] netlink_sendmsg+0x789/0xc70 net/netlink/af_netlink.c:1929 [<000000000a2d1e40>] sock_sendmsg_nosec net/socket.c:654 [inline] [<000000000a2d1e40>] sock_sendmsg+0x139/0x170 net/socket.c:674 [<00000000321d1969>] ____sys_sendmsg+0x658/0x7d0 net/socket.c:2350 [<00000000964e16bc>] ___sys_sendmsg+0xf8/0x170 net/socket.c:2404 [<000000001615e288>] __sys_sendmsg+0xd3/0x190 net/socket
<00000000964e16bc>] ___sys_sendmsg+0xf8/0x170 net/socket.c:2404 [<000000001615e288>] __sys_sendmsg+0xd3/0x190 net/socket.c:2433 [<000000004ee8b6a5>] do_syscall_64+0x37/0x90 arch/x86/entry/common.c:47 [<00000000171c7cee>] entry_SYSCALL_64_after_hwframe+0x44/0xae The memory of doi_def->map.std pointing is allocated in netlbl_cipsov4_add_std, but no place has freed it. It should be freed in cipso_v4_doi_free which frees the cipso DOI resource. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/212166510582631994be4f4b3fe15e10a03c1dd4 - https://git.kernel.org/stable/c/086e92b1d68c6338535f715aad173f8cf4bfbc8c - https://git.ker
31994be4f4b3fe15e10a03c1dd4 - https://git.kernel.org/stable/c/086e92b1d68c6338535f715aad173f8cf4bfbc8c - https://git.kernel.org/stable/c/6dcea66d3bb519b426282588f38e884e07893c1f - https://git.kernel.org/stable/c/5340858147e3dc60913fb3dd0cbb758ec4a26e66 - https://git.kernel.org/stable/c/398a24447eb60f060c8994221cb5ae6caf355fa1 - https://git.kernel.org/stable/c/deeeb65c6ee404f2d1fb80b38b2730645c0f4663 - https://git.kernel.org/stable/c/0ffb460be3abac86f884a8c548bb02724ec370f4 - https://git.kernel.org/stable/c/d612c3f3fae221e7ea736d196581c2217304bbbc
CVE ID: CVE-2021-47251 State: PUBLISHED Published: 2024-05-21T14:19:47.534Z Last Updated: 2025-05-04T07:07:09.917Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mac80211: fix skb length check in ieee80211_scan_rx() Replace hard-coded compile-time constants for header length check with dynamic determination based on the frame type. Otherwise, we hit a validation WARN_ON in cfg80211 later. [style fixes, reword commit message] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/5a1cd67a801cf5ef989c4783e07b86a25b143126 - https://git.kernel.org/stable/c/d1b949c70
: - https://git.kernel.org/stable/c/5a1cd67a801cf5ef989c4783e07b86a25b143126 - https://git.kernel.org/stable/c/d1b949c70206178b12027f66edc088d40375b5cb - https://git.kernel.org/stable/c/e298aa358f0ca658406d524b6639fe389cb6e11e
CVE ID: CVE-2021-47252 State: PUBLISHED Published: 2024-05-21T14:19:48.174Z Last Updated: 2025-05-04T07:07:11.197Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: batman-adv: Avoid WARN_ON timing related checks The soft/batadv interface for a queued OGM can be changed during the time the OGM was queued for transmission and when the OGM is actually transmitted by the worker. But WARN_ON must be used to denote kernel bugs and not to print simple warnings. A warning can simply be printed using pr_warn. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/45011f297
Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/45011f2973f6b52cf50db397bb27bf805f5f0e7f - https://git.kernel.org/stable/c/6031daaaf6d5c359c99dfffa102e332df234ff09 - https://git.kernel.org/stable/c/77a99aad5bc3ea105806ebae6be3cbadc2fc615e - https://git.kernel.org/stable/c/e8e9d2968a9d08bf5c683afca182f1537edebf8d - https://git.kernel.org/stable/c/e7fbd8184fa9e85f0d648c499841cb7ff6dec9f4 - https://git.kernel.org/stable/c/282baa8104af44e04c4af3e7f933b44267c7f86f - https://git.kernel.org/stable/c/2eb4e0b3631832a4291c8bf4c9db873f60b128c8 - https://git.kernel.org/stable/c/9f460ae31c4435fd022c443a6029352217a16ac1
CVE ID: CVE-2021-47253 State: PUBLISHED Published: 2024-05-21T14:19:48.825Z Last Updated: 2025-07-11T17:18:58.229Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix potential memory leak in DMUB hw_init [Why] On resume we perform DMUB hw_init which allocates memory: dm_resume->dm_dmub_hw_init->dc_dmub_srv_create->kzalloc That results in memory leak in suspend/resume scenarios. [How] Allocate memory for the DC wrapper to DMUB only if it was not allocated before. No need to reallocate it on suspend/resume. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kerne
pend/resume. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/9e8c2af010463197315fa54a6c17e74988b5259c - https://git.kernel.org/stable/c/aa000f828e60ac15d6340f606ec4a673966f5b0b - https://git.kernel.org/stable/c/c5699e2d863f58221044efdc3fa712dd32d55cde
CVE ID: CVE-2021-47254 State: PUBLISHED Published: 2024-05-21T14:19:49.475Z Last Updated: 2025-05-21T08:31:40.360Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix use-after-free in gfs2_glock_shrink_scan The GLF_LRU flag is checked under lru_lock in gfs2_glock_remove_from_lru() to remove the glock from the lru list in __gfs2_glock_put(). On the shrink scan path, the same flag is cleared under lru_lock but because of cond_resched_lock(&lru_lock) in gfs2_dispose_glock_lru(), progress on the put side can be made without deleting the glock from the lru list. Keep GLF_LRU across the race window opened by cond_resched_lock(&
be made without deleting the glock from the lru list. Keep GLF_LRU across the race window opened by cond_resched_lock(&lru_lock) to ensure correct behavior on both sides - clear GLF_LRU after list_del under lru_lock. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/38ce329534500bf4ae71f81df6a37a406cf187b4 - https://git.kernel.org/stable/c/92869945cc5b78ee8a1ef90336fe070893e3458a - https://git.kernel.org/stable/c/0364742decb0f02bc183404868b82896f7992595 - https://git.kernel.org/stable/c/094bf5670e762afa243d2c41a5c4ab71c7447bf4 - https://git.kernel.org/stable/c/86fd5b27db743a0ce0cc245e3a34813b2aa6ec1d - https://git.kerne
a243d2c41a5c4ab71c7447bf4 - https://git.kernel.org/stable/c/86fd5b27db743a0ce0cc245e3a34813b2aa6ec1d - https://git.kernel.org/stable/c/a61156314b66456ab6a291ed5deba1ebd002ab3c - https://git.kernel.org/stable/c/e87ef30fe73e7e10d2c85bdcc778dcec24dca553 - https://git.kernel.org/stable/c/1ab19c5de4c537ec0d9b21020395a5b5a6c059b2
CVE ID: CVE-2021-47255 State: PUBLISHED Published: 2024-05-21T14:19:50.125Z Last Updated: 2025-05-04T07:07:14.476Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: kvm: LAPIC: Restore guard to prevent illegal APIC register access Per the SDM, "any access that touches bytes 4 through 15 of an APIC register may cause undefined behavior and must not be executed." Worse, such an access in kvm_lapic_reg_read can result in a leak of kernel stack contents. Prior to commit 01402cf81051 ("kvm: LAPIC: write down valid APIC registers"), such an access was explicitly disallowed. Restore the guard that was removed in that commit. Additional A
C registers"), such an access was explicitly disallowed. Restore the guard that was removed in that commit. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/bf99ea52970caeb4583bdba1192c1f9b53b12c84 - https://git.kernel.org/stable/c/018685461a5b9a9a70e664ac77aef0d7415a3fd5 - https://git.kernel.org/stable/c/a2aff09807fbe4018c269d3773a629949058b210 - https://git.kernel.org/stable/c/218bf772bddd221489c38dde6ef8e917131161f6
CVE ID: CVE-2021-47256 State: PUBLISHED Published: 2024-05-21T14:19:50.777Z Last Updated: 2025-05-04T07:07:15.673Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: make sure wait for page writeback in memory_failure Our syzkaller trigger the "BUG_ON(!list_empty(&inode->i_wb_list))" in clear_inode: kernel BUG at fs/inode.c:519! Internal error: Oops - BUG: 0 [#1] SMP Modules linked in: Process syz-executor.0 (pid: 249, stack limit = 0x00000000a12409d7) CPU: 1 PID: 249 Comm: syz-executor.0 Not tainted 4.19.95 Hardware name: linux,dummy-virt (DT) pstate: 80000005 (Nzcv daif -PAN -UAO) pc : clear_inode+0x280/0x2a8 l
inted 4.19.95 Hardware name: linux,dummy-virt (DT) pstate: 80000005 (Nzcv daif -PAN -UAO) pc : clear_inode+0x280/0x2a8 lr : clear_inode+0x280/0x2a8 Call trace: clear_inode+0x280/0x2a8 ext4_clear_inode+0x38/0xe8 ext4_free_inode+0x130/0xc68 ext4_evict_inode+0xb20/0xcb8 evict+0x1a8/0x3c0 iput+0x344/0x460 do_unlinkat+0x260/0x410 __arm64_sys_unlinkat+0x6c/0xc0 el0_svc_common+0xdc/0x3b0 el0_svc_handler+0xf8/0x160 el0_svc+0x10/0x218 Kernel panic - not syncing: Fatal exception A crash dump of this problem show that someone called __munlock_pagevec to clear page LRU without lock_page: do_mmap -> mmap_region -> do_munmap -> munlock_vma_pages_range -> __munlock_pagevec. As a result memory_failure will
e: do_mmap -> mmap_region -> do_munmap -> munlock_vma_pages_range -> __munlock_pagevec. As a result memory_failure will call identify_page_state without wait_on_page_writeback. And after truncate_error_page clear the mapping of this page. end_page_writeback won't call sb_clear_inode_writeback to clear inode->i_wb_list. That will trigger BUG_ON in clear_inode! Fix it by checking PageWriteback too to help determine should we skip wait_on_page_writeback. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/d05267fd27a5c4f54e06daefa3035995d765ca0c - https://git.kernel.org/stable/c/6d210d547adc2218ef8b5bcf23518c5f2f1fd872 - http
5267fd27a5c4f54e06daefa3035995d765ca0c - https://git.kernel.org/stable/c/6d210d547adc2218ef8b5bcf23518c5f2f1fd872 - https://git.kernel.org/stable/c/566345aaabac853aa866f53a219c4b02a6beb527 - https://git.kernel.org/stable/c/9e379da727a7a031be9b877cde7b9c34a0fb8306 - https://git.kernel.org/stable/c/28788dc5c70597395b6b451dae4549bbaa8e2c56 - https://git.kernel.org/stable/c/e8675d291ac007e1c636870db880f837a9ea112a
CVE ID: CVE-2021-47257 State: PUBLISHED Published: 2024-05-21T14:19:51.445Z Last Updated: 2025-05-04T07:07:16.909Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: ieee802154: fix null deref in parse dev addr Fix a logic error that could result in a null deref if the user sets the mode incorrectly for the given addr type. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/1f95741981c899c4724647291fec5faa3c777185 - https://git.kernel.org/stable/c/c6998ccfefa652bac3f9b236821e392af43efa1e - https://git.kernel.org/stable/c/5f728ec65485625e30f46e5b4917ff023ad2
stable/c/c6998ccfefa652bac3f9b236821e392af43efa1e - https://git.kernel.org/stable/c/5f728ec65485625e30f46e5b4917ff023ad29ea0 - https://git.kernel.org/stable/c/d0f47648b87b6d5f204cb7f3cbce6d36dab85a67 - https://git.kernel.org/stable/c/c7836de2cadd88bc2f20f2c5a3d4ef4c73aef627 - https://git.kernel.org/stable/c/fdd51e34f45311ab6e48d2147cbc2904731b9993 - https://git.kernel.org/stable/c/9fdd04918a452980631ecc499317881c1d120b70
CVE ID: CVE-2021-47258 State: PUBLISHED Published: 2024-05-21T14:19:52.082Z Last Updated: 2025-05-04T07:07:17.929Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix error handling of scsi_host_alloc() After device is initialized via device_initialize(), or its name is set via dev_set_name(), the device has to be freed via put_device(). Otherwise device name will be leaked because it is allocated dynamically in dev_set_name(). Fix the leak by replacing kfree() with put_device(). Since scsi_host_dev_release() properly handles IDA and kthread removal, remove special-casing these from the error handling as well. Additi
_release() properly handles IDA and kthread removal, remove special-casing these from the error handling as well. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8958181c1663e24a13434448e7d6b96b5d04900a - https://git.kernel.org/stable/c/db08ce595dd64ea9859f7d088b51cbfc8e685c66 - https://git.kernel.org/stable/c/2dc85045ae65b9302a1d2e2ddd7ce4c030153a6a - https://git.kernel.org/stable/c/79296e292d67fa7b5fb8d8c27343683e823872c8 - https://git.kernel.org/stable/c/7a696ce1d5d16a33a6cd6400bbcc0339b2460e11 - https://git.kernel.org/stable/c/45d83db4728127944b237c0c8248987df9d478e7 - https://git.kernel.org/stable/c/66a834d092930c
ttps://git.kernel.org/stable/c/45d83db4728127944b237c0c8248987df9d478e7 - https://git.kernel.org/stable/c/66a834d092930cf41d809c0e989b13cd6f9ca006
CVE ID: CVE-2021-47259 State: PUBLISHED Published: 2024-05-21T14:19:52.738Z Last Updated: 2025-05-04T07:07:18.962Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: NFS: Fix use-after-free in nfs4_init_client() KASAN reports a use-after-free when attempting to mount two different exports through two different NICs that belong to the same server. Olga was able to hit this with kernels starting somewhere between 5.7 and 5.10, but I traced the patch that introduced the clear_bit() call to 4.13. So something must have changed in the refcounting of the clp pointer to make this call to nfs_put_client() the very last one. Additional Anal
e changed in the refcounting of the clp pointer to make this call to nfs_put_client() the very last one. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/c7eab9e2d7b4e983ce280276fb920af649955897 - https://git.kernel.org/stable/c/42c10b0db064e45f5c5ae7019bbf2168ffab766c - https://git.kernel.org/stable/c/3e3c7ebbfac152d08be75c92802a64a1f6471a15 - https://git.kernel.org/stable/c/c3b6cf64dfe4ef96e7341508d50d6998da7062c7 - https://git.kernel.org/stable/c/72651c6579a25317a90536181d311c663d0329ab - https://git.kernel.org/stable/c/476bdb04c501fc64bf3b8464ffddefc8dbe01577
CVE ID: CVE-2021-47260 State: PUBLISHED Published: 2024-05-21T14:19:53.375Z Last Updated: 2025-05-04T07:07:25.090Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a potential NULL dereference in nfs_get_client() None of the callers are expecting NULL returns from nfs_get_client() so this code will lead to an Oops. It's better to return an error pointer. I expect that this is dead code so hopefully no one is affected. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/fab8bfdfb4aac9e4e8363666333adfdf21e89106 - https://git.kernel.org/stable/c/a979e6010
: - https://git.kernel.org/stable/c/fab8bfdfb4aac9e4e8363666333adfdf21e89106 - https://git.kernel.org/stable/c/a979e601000982a3ca693171a6d4dffc47f8ad00 - https://git.kernel.org/stable/c/634f17ff1d59905eb3b4bbbc00805961d08beaee - https://git.kernel.org/stable/c/4b380a7d84ef2ce3f4f5bec5d8706ed937ac6502 - https://git.kernel.org/stable/c/0057ecef9f324007c0ba5fcca4ddd131178ce78b - https://git.kernel.org/stable/c/279ad78a00f8b9c5ff24171a59297187a3bd44b7 - https://git.kernel.org/stable/c/58ddf61f10b8f9b7b1341644bfee2f1c6508d4e1 - https://git.kernel.org/stable/c/09226e8303beeec10f2ff844d2e46d1371dc58e0
CVE ID: CVE-2021-47261 State: PUBLISHED Published: 2024-05-21T14:19:54.025Z Last Updated: 2025-05-04T07:07:26.307Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix initializing CQ fragments buffer The function init_cq_frag_buf() can be called to initialize the current CQ fragments buffer cq->buf, or the temporary cq->resize_buf that is filled during CQ resize operation. However, the offending commit started to use function get_cqe() for getting the CQEs, the issue with this change is that get_cqe() always returns CQEs from cq->buf, which leads us to initialize the wrong buffer, and in case of enlarging the CQ we try
always returns CQEs from cq->buf, which leads us to initialize the wrong buffer, and in case of enlarging the CQ we try to access elements beyond the size of the current cq->buf and eventually hit a kernel panic. [exception RIP: init_cq_frag_buf+103] [ffff9f799ddcbcd8] mlx5_ib_resize_cq at ffffffffc0835d60 [mlx5_ib] [ffff9f799ddcbdb0] ib_resize_cq at ffffffffc05270df [ib_core] [ffff9f799ddcbdc0] llt_rdma_setup_qp at ffffffffc0a6a712 [llt] [ffff9f799ddcbe10] llt_rdma_cc_event_action at ffffffffc0a6b411 [llt] [ffff9f799ddcbe98] llt_rdma_client_conn_thread at ffffffffc0a6bb75 [llt] [ffff9f799ddcbec8] kthread at ffffffffa66c5da1 [ffff9f799ddcbf50] ret_from_fork_nospec_begin at ffffffffa6d95ddd F
[llt] [ffff9f799ddcbec8] kthread at ffffffffa66c5da1 [ffff9f799ddcbf50] ret_from_fork_nospec_begin at ffffffffa6d95ddd Fix it by getting the needed CQE by calling mlx5_frag_buf_get_wqe() that takes the correct source buffer as a parameter. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/1ec2dcd680c71d0d36fa25638b327a468babd5c9 - https://git.kernel.org/stable/c/e3ecd9c09fcc10cf6b2bc67e2990c397c40a8c26 - https://git.kernel.org/stable/c/91f7fdc4cc10542ca1045c06aad23365f0d067e0 - https://git.kernel.org/stable/c/3e670c54eda238cb8a1ea93538a79ae89285c1c4 - https://git.kernel.org/stable/c/2ba0aa2feebda680ecfc3c552e867cf4d1b05a
able/c/3e670c54eda238cb8a1ea93538a79ae89285c1c4 - https://git.kernel.org/stable/c/2ba0aa2feebda680ecfc3c552e867cf4d1b05a3a
CVE ID: CVE-2021-47262 State: PUBLISHED Published: 2024-05-21T14:19:54.666Z Last Updated: 2025-05-04T07:07:27.662Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Ensure liveliness of nested VM-Enter fail tracepoint message Use the __string() machinery provided by the tracing subystem to make a copy of the string literals consumed by the "nested VM-Enter failed" tracepoint. A complete copy is necessary to ensure that the tracepoint can't outlive the data/memory it consumes and deference stale memory. Because the tracepoint itself is defined by kvm, if kvm-intel and/or kvm-amd are built as modules, the memory holding th
Because the tracepoint itself is defined by kvm, if kvm-intel and/or kvm-amd are built as modules, the memory holding the string literals defined by the vendor modules will be freed when the module is unloaded, whereas the tracepoint and its data in the ring buffer will live until kvm is unloaded (or "indefinitely" if kvm is built-in). This bug has existed since the tracepoint was added, but was recently exposed by a new check in tracing to detect exactly this type of bug. fmt: '%s%s ' current_buffer: ' vmx_dirty_log_t-140127 [003] .... kvm_nested_vmenter_failed: ' WARNING: CPU: 3 PID: 140134 at kernel/trace/trace.c:3759 trace_check_vprintf+0x3be/0x3e0 CPU: 3 PID: 140134 Comm: less Not taint
CPU: 3 PID: 140134 at kernel/trace/trace.c:3759 trace_check_vprintf+0x3be/0x3e0 CPU: 3 PID: 140134 Comm: less Not tainted 5.13.0-rc1-ce2e73ce600a-req #184 Hardware name: ASUS Q87M-E/Q87M-E, BIOS 1102 03/03/2014 RIP: 0010:trace_check_vprintf+0x3be/0x3e0 Code: <0f> 0b 44 8b 4c 24 1c e9 a9 fe ff ff c6 44 02 ff 00 49 8b 97 b0 20 RSP: 0018:ffffa895cc37bcb0 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffffa895cc37bd08 RCX: 0000000000000027 RDX: 0000000000000027 RSI: 00000000ffffdfff RDI: ffff9766cfad74f8 RBP: ffffffffc0a041d4 R08: ffff9766cfad74f0 R09: ffffa895cc37bad8 R10: 0000000000000001 R11: 0000000000000001 R12: ffffffffc0a041d4 R13: ffffffffc0f4dba8 R14: 0000000000000000 R15: ffff976409f2c00
00000000001 R11: 0000000000000001 R12: ffffffffc0a041d4 R13: ffffffffc0f4dba8 R14: 0000000000000000 R15: ffff976409f2c000 FS: 00007f92fa200740(0000) GS:ffff9766cfac0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000559bd11b0000 CR3: 000000019fbaa002 CR4: 00000000001726e0 Call Trace: trace_event_printf+0x5e/0x80 trace_raw_output_kvm_nested_vmenter_failed+0x3a/0x60 [kvm] print_trace_line+0x1dd/0x4e0 s_show+0x45/0x150 seq_read_iter+0x2d5/0x4c0 seq_read+0x106/0x150 vfs_read+0x98/0x180 ksys_read+0x5f/0xe0 do_syscall_64+0x40/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References:
CALL_64_after_hwframe+0x44/0xae Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/796d3bd4ac9316e70c181189318cd2bd98af34bc - https://git.kernel.org/stable/c/d046f724bbd725a24007b7e52b2d675249870888 - https://git.kernel.org/stable/c/9fb088ce13bc3c59a51260207b487db3e556f275 - https://git.kernel.org/stable/c/f31500b0d437a2464ca5972d8f5439e156b74960
CVE ID: CVE-2021-47263 State: PUBLISHED Published: 2024-05-21T14:19:55.318Z Last Updated: 2025-05-04T07:07:28.795Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: gpio: wcd934x: Fix shift-out-of-bounds error bit-mask for pins 0 to 4 is BIT(0) to BIT(4) however we ended up with BIT(n - 1) which is not right, and this was caught by below usban check UBSAN: shift-out-of-bounds in drivers/gpio/gpio-wcd934x.c:34:14 Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e0b518a2eb44d8a74c19e50f79a8ed393e96d634 - https://git.kernel.org/stable/c/dd55331d493b7ea75c5db1f24
kernel.org/stable/c/e0b518a2eb44d8a74c19e50f79a8ed393e96d634 - https://git.kernel.org/stable/c/dd55331d493b7ea75c5db1f24d6822946fde2862 - https://git.kernel.org/stable/c/dbec64b11c65d74f31427e2b9d5746fbf17bf840