net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 277740023def559a4a2ddc3e8e784ee37a0f16a9, Kernel 53eb7bd09aace72fa17510d80e0caf5ca058c231, Kernel 65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e and 5 more.
In the Linux kernel, the following vulnerability has been resolved: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot On the SMC-D client, slot 0 of ini->ism_dev[]/ini->ism_chid[] is reserved for an SMC-Dv1 device. smc_find_ism_v2_device_clnt() populates V2 entries starting at index 1, so when no V1 device is selected slot 0 is left in its kzalloc()'ed state with ism_dev[0] == NULL and ism_chid[0] == 0. smc_v2_determine_accepted_chid() then matches the peer's CHID against the array starting from index 0 using the CHID alone. A malicious peer replying to a SMC-Dv2-only proposal with d1.chid == 0 matches the empty slot, ini->ism_selected becomes 0, and the subsequent ism_dev[0]->lgr_lock dereference in smc_conn_create() faults at offsetof(struct smcd_dev, lgr_lock) == 0x68: BUG: KASAN: null-ptr-deref in _raw_spin_lock_bh+0x79/0xe0 Write of size 4 at addr 0000000000000068 by task exploit/144 Call Trace: _raw_spin_lock_bh smc_conn_create (net/smc/smc_core.c:1997) __smc_connect (net/smc/af_smc.c:1447) smc_connect (net/smc/af_smc.c:1720) __sys_connect __x64_sys_connect do_syscall_64 Require ism_dev[i] to be non-NULL before accepting a CHID match.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.10, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <277740023def559a4a2ddc3e8e784ee37a0f16a9, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <53eb7bd09aace72fa17510d80e0caf5ca058c231, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <6927cacf2b10d4fa80c1a2d407512ef9397c59c6, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <903f7688ffeb9b323d70652c01f554bd4ba2a3d6, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <afa9036b8c9963947b487c36e332df6a42c96fcb, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0, >=a7c9c5f4af7f6098da68705fc5d86565d0728ef7 <dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0 | 277740023def559a4a2ddc3e8e784ee37a0f16a9, 53eb7bd09aace72fa17510d80e0caf5ca058c231, 65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e, 6927cacf2b10d4fa80c1a2d407512ef9397c59c6, 903f7688ffeb9b323d70652c01f554bd4ba2a3d6, afa9036b8c9963947b487c36e332df6a42c96fcb, d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0, dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket