Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
ed by syzkaller was something like: (1) create a TCP socket (2) initiate a TFO connect via sendto() (3) while socket is in TCP_SYN_SENT, call setsockopt(TCP_CONGESTION), which calls: tcp_set_congestion_control() -> tcp_reinit_congestion_control() -> tcp_init_congestion_control() (4) receive ACK, connection is established, call tcp_init_transfer(), set icsk_ca_initialized=0 (without first calling cc->release()), call tcp_init_congestion_control() again. Note that in this sequence tcp_init_congestion_control() is called twice without a cc->release() call in between. Thus, for CC modules that allocate memory in their init() function, e.g, CDG, a memory leak may occur. The syzkaller tool managed
CC modules that allocate memory in their init() function, e.g, CDG, a memory leak may occur. The syzkaller tool managed to find a reproducer that triggered such a leak in CDG. The bug was introduced when that commit 8919a9b31eb4 ("tcp: Only init congestion control if not initialized already") introduced icsk_ca_initialized and set icsk_ca_initialized to 0 in tcp_init_transfer(), missing the possibility for a sequence like the one above, where a process could call setsockopt(TCP_CONGESTION) in state TCP_SYN_SENT (i.e. after the connect() or TFO open sendmsg()), which would call tcp_init_congestion_control(). It did not intend to reset any initialization that the user had already explicitly m
call tcp_init_congestion_control(). It did not intend to reset any initialization that the user had already explicitly made; it just missed the possibility of that particular sequence (which syzkaller managed to find). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/ad4ba3404931745a5977ad12db4f0c34080e52f7 - https://git.kernel.org/stable/c/fe77b85828ca9ddc42977b79de9e40d18545b4fe - https://git.kernel.org/stable/c/be5d1b61a2ad28c7e57fe8bfa277373e8ecffcdc
CVE ID: CVE-2021-47305 State: PUBLISHED Published: 2024-05-21T14:35:25.345Z Last Updated: 2025-05-04T07:08:20.792Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: dma-buf/sync_file: Don't leak fences on merge failure Each add_fence() call does a dma_fence_get() on the relevant fence. In the error path, we weren't calling dma_fence_put() so all those fences got leaked. Also, in the krealloc_array failure case, we weren't freeing the fences array. Instead, ensure that i and fences are always zero-initialized and dma_fence_put() all the fences and kfree(fences) on every error path. Additional Analyst Notes: - CISA ADP Vulnrichment:
dma_fence_put() all the fences and kfree(fences) on every error path. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/19f51c2529339280d2c8c6427cd3e21ddf1ac3f8 - https://git.kernel.org/stable/c/e0355a0ad31a1d677b2a4514206de4902bd550e8 - https://git.kernel.org/stable/c/41f45e91c92c8480242ea448d54e28c753b13902 - https://git.kernel.org/stable/c/0d514185ae792d3a1903c8e1a83899aa996705ce - https://git.kernel.org/stable/c/19edcd97727aae9362444a859a24d99a8730cb27 - https://git.kernel.org/stable/c/ffe000217c5068c5da07ccb1c0f8cce7ad767435
CVE ID: CVE-2021-47306 State: PUBLISHED Published: 2024-05-21T14:35:26.005Z Last Updated: 2025-05-04T07:08:21.801Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: fddi: fix UAF in fza_probe fp is netdev private data and it cannot be used after free_netdev() call. Using fp after free_netdev() can cause UAF bug. Fix it by moving free_netdev() after error message. TURBOchannel adapter") Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/04b06716838bfc26742dbed3ae1d3697fe5317ee - https://git.kernel.org/stable/c/f33605908a9b6063525e9f68e62d739948c5fccf - http
b06716838bfc26742dbed3ae1d3697fe5317ee - https://git.kernel.org/stable/c/f33605908a9b6063525e9f68e62d739948c5fccf - https://git.kernel.org/stable/c/bdfbb51f7a437ae8ea91317a5c133ec13adf3c47 - https://git.kernel.org/stable/c/deb7178eb940e2c5caca1b1db084a69b2e59b4c9
CVE ID: CVE-2021-47307 State: PUBLISHED Published: 2024-05-21T14:35:26.667Z Last Updated: 2025-05-04T07:08:22.855Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cifs: prevent NULL deref in cifs_compose_mount_options() The optional @ref parameter might contain an NULL node_name, so prevent dereferencing it in cifs_compose_mount_options(). Addresses-Coverity: 1476408 ("Explicit null dereferenced") Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/f7d1fa65e74263d11f90ddd33b4d4cd905a93759 - https://git.kernel.org/stable/c/e58c162789becede894d3e94c0ce6695a2ef57
able/c/f7d1fa65e74263d11f90ddd33b4d4cd905a93759 - https://git.kernel.org/stable/c/e58c162789becede894d3e94c0ce6695a2ef5796 - https://git.kernel.org/stable/c/ae3d181f4e912f51af7776ea165f199b16fc165d - https://git.kernel.org/stable/c/03313d1c3a2f086bb60920607ab79ac8f8578306
CVE ID: CVE-2021-47308 State: PUBLISHED Published: 2024-05-21T14:35:27.319Z Last Updated: 2025-05-04T07:08:23.900Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: libfc: Fix array index out of bound exception Fix array index out of bound exception in fc_rport_prli_resp(). Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/44651522941c623e20882b3b443f23f77de1ea8b - https://git.kernel.org/stable/c/4921b1618045ffab71b1050bf0014df3313a2289 - https://git.kernel.org/stable/c/0fe70c15f9435bb3c50954778245d62ee38b0e03 - https://git.kernel.org/stable/c/a4a54c54af
- https://git.kernel.org/stable/c/0fe70c15f9435bb3c50954778245d62ee38b0e03 - https://git.kernel.org/stable/c/a4a54c54af2516caa9c145015844543cfc84316a - https://git.kernel.org/stable/c/8511293e643a18b248510ae5734e4f360754348c - https://git.kernel.org/stable/c/b27c4577557045f1ab3cdfeabfc7f3cd24aca1fe
CVE ID: CVE-2021-47309 State: PUBLISHED Published: 2024-05-21T14:35:27.981Z Last Updated: 2025-05-04T07:08:24.966Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: validate lwtstate->data before returning from skb_tunnel_info() skb_tunnel_info() returns pointer of lwtstate->data as ip_tunnel_info type without validation. lwtstate->data can have various types such as mpls_iptunnel_encap, etc and these are not compatible. So skb_tunnel_info() should validate before returning that pointer. Splat looks like: BUG: KASAN: slab-out-of-bounds in vxlan_get_route+0x418/0x4b0 [vxlan] Read of size 2 at addr ffff888106ec2698 by task ping
G: KASAN: slab-out-of-bounds in vxlan_get_route+0x418/0x4b0 [vxlan] Read of size 2 at addr ffff888106ec2698 by task ping/811 CPU: 1 PID: 811 Comm: ping Not tainted 5.13.0+ #1195 Call Trace: dump_stack_lvl+0x56/0x7b print_address_description.constprop.8.cold.13+0x13/0x2ee ? vxlan_get_route+0x418/0x4b0 [vxlan] ? vxlan_get_route+0x418/0x4b0 [vxlan] kasan_report.cold.14+0x83/0xdf ? vxlan_get_route+0x418/0x4b0 [vxlan] vxlan_get_route+0x418/0x4b0 [vxlan] [ ... ] vxlan_xmit_one+0x148b/0x32b0 [vxlan] [ ... ] vxlan_xmit+0x25c5/0x4780 [vxlan] [ ... ] dev_hard_start_xmit+0x1ae/0x6e0 __dev_queue_xmit+0x1f39/0x31a0 [ ... ] neigh_xmit+0x2f9/0x940 mpls_xmit+0x911/0x1600 [mpls_iptunnel] lwtunnel_xmit+0x18f/
_dev_queue_xmit+0x1f39/0x31a0 [ ... ] neigh_xmit+0x2f9/0x940 mpls_xmit+0x911/0x1600 [mpls_iptunnel] lwtunnel_xmit+0x18f/0x450 ip_finish_output2+0x867/0x2040 [ ... ] Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e7f3c9df40515a6c6b46f36c4c94cf48a043f887 - https://git.kernel.org/stable/c/b61d327cd3cc5ea591f3bf751dd11e034f388bb5 - https://git.kernel.org/stable/c/83bdcfbd968bcc91a0632b7b625e4a9b0cba5e0d - https://git.kernel.org/stable/c/8bb1589c89e61e3b182dd546f1021928ebb5c2a6 - https://git.kernel.org/stable/c/8aa13a86964cdec4fd969ef677c6614ff068641a - https://git.kernel.org/stable/c/2179d96ec702cc33ead02a9ce40ece599b8538
able/c/8aa13a86964cdec4fd969ef677c6614ff068641a - https://git.kernel.org/stable/c/2179d96ec702cc33ead02a9ce40ece599b8538c5 - https://git.kernel.org/stable/c/a915379594f1e045421635c6316d8f3ffa018c58 - https://git.kernel.org/stable/c/67a9c94317402b826fc3db32afc8f39336803d97
CVE ID: CVE-2021-47310 State: PUBLISHED Published: 2024-05-21T14:35:28.649Z Last Updated: 2025-05-04T07:08:26.087Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: ti: fix UAF in tlan_remove_one priv is netdev private data and it cannot be used after free_netdev() call. Using priv after free_netdev() can cause UAF bug. Fix it by moving free_netdev() at the end of the function. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/a18a8d9cfbb112ad72e625372849adc3986fd6bf - https://git.kernel.org/stable/c/c263ae8c7e4c482387de5e6c89e213f8173fe8b6 - https://git.
b112ad72e625372849adc3986fd6bf - https://git.kernel.org/stable/c/c263ae8c7e4c482387de5e6c89e213f8173fe8b6 - https://git.kernel.org/stable/c/0538b0ab7d2c396e385694228c7cdcd2d2c514e9 - https://git.kernel.org/stable/c/a0a817b2d308fac090a05cbbe80988e073ac5193 - https://git.kernel.org/stable/c/b7e5563f2a7862a9e4796abb9908b092f677e3c1 - https://git.kernel.org/stable/c/f2a062fcfe1d6f1b0a86fa76ae21c277d65f4405 - https://git.kernel.org/stable/c/93efab0ef2a607fff9166d447c4035f98b5db342 - https://git.kernel.org/stable/c/0336f8ffece62f882ab3012820965a786a983f70
CVE ID: CVE-2021-47311 State: PUBLISHED Published: 2024-05-21T14:35:29.304Z Last Updated: 2025-05-04T07:08:27.212Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emac_remove adpt is netdev private data and it cannot be used after free_netdev() call. Using adpt after free_netdev() can cause UAF bug. Fix it by moving free_netdev() at the end of the function. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/4d04a42b926e682140776e54188f4a44f1f01a81 - https://git.kernel.org/stable/c/b1e091331920f8fbfc747dcbd16263fcd71abb2d - https://g
b926e682140776e54188f4a44f1f01a81 - https://git.kernel.org/stable/c/b1e091331920f8fbfc747dcbd16263fcd71abb2d - https://git.kernel.org/stable/c/11e9d163d631198bb3eb41a677a61b499516c0f7 - https://git.kernel.org/stable/c/2b70ca92847c619d6264c7372ef74fcbfd1e048c - https://git.kernel.org/stable/c/b560521eca03d0a2db6093a5a632cbdd0a0cf833 - https://git.kernel.org/stable/c/8a225a6e07a57a1538d53637cb3d82bd3e477839 - https://git.kernel.org/stable/c/ad297cd2db8953e2202970e9504cab247b6c7cb4
CVE ID: CVE-2021-47312 State: PUBLISHED Published: 2024-05-21T14:35:29.963Z Last Updated: 2025-05-04T07:08:28.332Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix dereference of null pointer flow In the case where chain->flags & NFT_CHAIN_HW_OFFLOAD is false then nft_flow_rule_create is not called and flow is NULL. The subsequent error handling execution via label err_destroy_flow_rule will lead to a null pointer dereference on flow when calling nft_flow_rule_destroy. Since the error path to err_destroy_flow_rule has to cater for null and non-null flows, only call nft_flow_rule_destroy if flow is non-nu
ath to err_destroy_flow_rule has to cater for null and non-null flows, only call nft_flow_rule_destroy if flow is non-null to fix this issue. Addresses-Coverity: ("Explicity null dereference") Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/70a5a1950cca02c5cd161bb3846b4d983eed97d3 - https://git.kernel.org/stable/c/4ca041f919f13783b0b03894783deee00dbca19a
CVE ID: CVE-2021-47313 State: PUBLISHED Published: 2024-05-21T14:35:30.607Z Last Updated: 2025-05-04T07:08:29.568Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init It's a classic example of memleak, we allocate something, we fail and never free the resources. Make sure we free all resources on policy ->init() failures. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/b775383355755885b19d2acef977f1ca132e80a3 - https://git.kernel.org/stable/c/e1b2b2b61d30d7ce057ec17237c217d152ed97f2 - https://git.ke
5885b19d2acef977f1ca132e80a3 - https://git.kernel.org/stable/c/e1b2b2b61d30d7ce057ec17237c217d152ed97f2 - https://git.kernel.org/stable/c/fe2535a44904a77615a3af8e8fd7dafb98fb0e1b
CVE ID: CVE-2021-47314 State: PUBLISHED Published: 2024-05-21T14:35:31.274Z Last Updated: 2025-05-04T07:08:30.629Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: memory: fsl_ifc: fix leak of private memory on probe failure On probe error the driver should free the memory allocated for private structure. Fix this by using resource-managed allocation. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/8018476756066e97ecb886c3dc024aeb7d5792ad - https://git.kernel.org/stable/c/3b45b8a7d549bd92ec94b5357c2c2c1a7ed107e4 - https://git.kernel.org/stable/c/7626ffbea70
- https://git.kernel.org/stable/c/3b45b8a7d549bd92ec94b5357c2c2c1a7ed107e4 - https://git.kernel.org/stable/c/7626ffbea708e5aba6912295c012d2b409a1769f - https://git.kernel.org/stable/c/ee1aa737ba0b75ab8af3444c4ae5bdba36aed6e6 - https://git.kernel.org/stable/c/443f6ca6fd186b4fa4e6f377b6e19a91feb1a0d5 - https://git.kernel.org/stable/c/b5789e23773f4a852fbfe244b63f675e265d3a7f - https://git.kernel.org/stable/c/48ee69825f7480622ed447b0249123236d3b3ad0 - https://git.kernel.org/stable/c/a6b45b4932f7b0c36b41fb56a35ad679ece939a0 - https://git.kernel.org/stable/c/8e0d09b1232d0538066c40ed4c13086faccbdff6
CVE ID: CVE-2021-47315 State: PUBLISHED Published: 2024-05-21T14:35:31.925Z Last Updated: 2025-05-04T07:08:31.724Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: memory: fsl_ifc: fix leak of IO mapping on probe failure On probe error the driver should unmap the IO memory. Smatch reports: drivers/memory/fsl_ifc.c:298 fsl_ifc_ctrl_probe() warn: 'fsl_ifc_ctrl_dev->gregs' not released on lines: 298. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/d0d04b95e8ed0223844a1d58497c686fe2e4a955 - https://git.kernel.org/stable/c/6b3b002de90738e3c85853a682ce7e0fa078d42
ble/c/d0d04b95e8ed0223844a1d58497c686fe2e4a955 - https://git.kernel.org/stable/c/6b3b002de90738e3c85853a682ce7e0fa078d42b - https://git.kernel.org/stable/c/94bc2fe46102d1e060fc749c0c19511e76c9995f - https://git.kernel.org/stable/c/d9213d4f372d30b5bc4d921795d6bed0c0e3eebf - https://git.kernel.org/stable/c/8d071d270afba468708faca5f7b6d9e656f75e27 - https://git.kernel.org/stable/c/83af5816308b490b05fc8fa27fc1bdc769df200a - https://git.kernel.org/stable/c/28f71fd81ebd3b386bf5c7c5539664156f7d72c1 - https://git.kernel.org/stable/c/3b132ab67fc7a358fff35e808fa65d4bea452521
CVE ID: CVE-2021-47316 State: PUBLISHED Published: 2024-05-21T14:35:32.564Z Last Updated: 2025-05-04T07:08:32.797Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfsd: fix NULL dereference in nfs3svc_encode_getaclres In error cases the dentry may be NULL. Before 20798dfe249a, the encoder also checked dentry and d_really_is_positive(dentry), but that looks like overkill to me--zero status should be enough to guarantee a positive dentry. This isn't the first time we've seen an error-case NULL dereference hidden in the initialization of a local variable in an xdr encoder. But I went back through the other recent rewrites and didn'
in the initialization of a local variable in an xdr encoder. But I went back through the other recent rewrites and didn't spot any similar bugs. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/e79057d15d96ef19de4de6d7e479bae3d58a2a8d - https://git.kernel.org/stable/c/650e6f383a6eb40f7c0a010982a74ab4b6893870 - https://git.kernel.org/stable/c/ab1016d39cc052064e32f25ad18ef8767a0ee3b8
CVE ID: CVE-2021-47317 State: PUBLISHED Published: 2024-05-21T14:35:33.212Z Last Updated: 2025-05-04T07:08:33.868Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 ("bpf: Rename BPF_XADD and prepare to encode other atomics in .imm") converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did
ing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT'ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/7284dab07e4d51d453cc42851fae9ec4fac6ef2f - https://git.kernel.org/stable/c/0d435b6d94b05dcfd836d758a63145aa566618e2 - https://git.kernel.org/stable/c/419ac821766cbdb9fd85872bb3f1a589df05c94c
CVE ID: CVE-2021-47318 State: PUBLISHED Published: 2024-05-21T14:35:33.884Z Last Updated: 2025-05-04T07:08:34.975Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: arch_topology: Avoid use-after-free for scale_freq_data Currently topology_scale_freq_tick() (which gets called from scheduler_tick()) may end up using a pointer to "struct scale_freq_data", which was previously cleared by topology_clear_scale_freq_source(), as there is no protection in place here. The users of topology_clear_scale_freq_source() though needs a guarantee that the previously cleared scale_freq_data isn't used anymore, so they can free the related resourc
h needs a guarantee that the previously cleared scale_freq_data isn't used anymore, so they can free the related resources. Since topology_scale_freq_tick() is called from scheduler tick, we don't want to add locking in there. Use the RCU update mechanism instead (which is already used by the scheduler's utilization update path) to guarantee race free updates here. synchronize_rcu() makes sure that all RCU critical sections that started before it is called, will finish before it returns. And so the callers of topology_clear_scale_freq_source() don't need to worry about their callback getting called anymore. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: Reference
r callback getting called anymore. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/ccdf7e073170886bc370c613e269de610a794c4a - https://git.kernel.org/stable/c/83150f5d05f065fb5c12c612f119015cabdcc124
CVE ID: CVE-2021-47319 State: PUBLISHED Published: 2024-05-21T14:35:34.541Z Last Updated: 2025-05-04T07:08:36.046Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: virtio-blk: Fix memory leak among suspend/resume procedure The vblk->vqs should be freed before we call init_vqs() in virtblk_restore(). Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/381bde79d11e596002edfd914e6714291826967a - https://git.kernel.org/stable/c/102d6bc6475ab09bab579c18704e6cf8d898e93c - https://git.kernel.org/stable/c/863da837964c80c72e368a4f748c30d25daa1815 - https://git.kernel.or
79c18704e6cf8d898e93c - https://git.kernel.org/stable/c/863da837964c80c72e368a4f748c30d25daa1815 - https://git.kernel.org/stable/c/600942d2fd49b90e44857d20c774b20d16f3130f - https://git.kernel.org/stable/c/04c6e60b884cb5e94ff32af46867fb41d5848358 - https://git.kernel.org/stable/c/cd24da0db9f75ca11eaf6060f0ccb90e2f3be3b0 - https://git.kernel.org/stable/c/ca2b8ae93a6da9839dc7f9eb9199b18aa03c3dae - https://git.kernel.org/stable/c/29a2f4a3214aa14d61cc9737c9f886dae9dbb710 - https://git.kernel.org/stable/c/b71ba22e7c6c6b279c66f53ee7818709774efa1f
CVE ID: CVE-2021-47320 State: PUBLISHED Published: 2024-05-21T14:35:35.205Z Last Updated: 2025-05-04T07:08:37.097Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: nfs: fix acl memory leak of posix_acl_create() When looking into another nfs xfstests report, I found acl and default_acl in nfs3_proc_create() and nfs3_proc_mknod() error paths are possibly leaked. Fix them in advance. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://git.kernel.org/stable/c/2e3960f276b4574a9bb0dfa31a7497302f6363b2 - https://git.kernel.org/stable/c/cef9d9acb7c80ed6bace894b6334557fd493863b - https://git.k
4574a9bb0dfa31a7497302f6363b2 - https://git.kernel.org/stable/c/cef9d9acb7c80ed6bace894b6334557fd493863b - https://git.kernel.org/stable/c/8a2b308a54c5ec224fedc753617f99b29ffcd883 - https://git.kernel.org/stable/c/0704f617040c397ae73c1f88f3956787ec5d6529 - https://git.kernel.org/stable/c/d0b32dc1409f7e65e4fcc34e236462268e69a357 - https://git.kernel.org/stable/c/4b515308ab875c7e8ada8e606fe0c64762da5ed4 - https://git.kernel.org/stable/c/c8fc86e9df6a6a03f5a8e15a3b7a5c75fd05aa38 - https://git.kernel.org/stable/c/687cf32865b2d6960214bce523f2afac58dd3cd2 - https://git.kernel.org/stable/c/1fcb6fcd74a222d9ead54d405842fc763bb86262
CVE ID: CVE-2021-47321 State: PUBLISHED Published: 2024-05-21T14:35:35.877Z Last Updated: 2025-05-04T07:08:38.170Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: watchdog: Fix possible use-after-free by calling del_timer_sync() This driver's remove path calls del_timer(). However, that function does not wait until the timer handler finishes. This means that the timer handler may still be running after the driver's remove function has finished, which would result in a use-after-free. Fix by calling del_timer_sync(), which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CVE
nc(), which makes sure the timer handler has finished, and unable to re-schedule itself. Additional Analyst Notes: - CVE Program Container: - CISA ADP Vulnrichment: References: - https://git.kernel.org/stable/c/58606882ad8ec6c39e0f40344b922921ef94ab4d - https://git.kernel.org/stable/c/ca96b8ea5e74956071154bdb456778cc3027e79f - https://git.kernel.org/stable/c/8bec568d7518b1504a602ed5376bb322e4dbb270 - https://git.kernel.org/stable/c/ecd620e0fb1ff7f78fdb593379b2e6938c99707a - https://git.kernel.org/stable/c/db222f1477ad5692cd454709b714949807e5d111 - https://git.kernel.org/stable/c/66ba9cf929b1c4fabf545bd4c18f6f64e23e46e4 - https://git.kernel.org/stable/c/4c05dac488a660fe2925c047ecb119e7afaaeb1
ble/c/66ba9cf929b1c4fabf545bd4c18f6f64e23e46e4 - https://git.kernel.org/stable/c/4c05dac488a660fe2925c047ecb119e7afaaeb1e - https://git.kernel.org/stable/c/1a053c4d716898a53c2e31c574a70ea0c37044a3 - https://git.kernel.org/stable/c/d0212f095ab56672f6f36aabc605bda205e1e0bf