net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.266, 5.15.217, 6.1.175, 6.6.142, 6.12.92, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in 903f7688ffeb9b323d70652c01f554bd4ba2a3d6; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in 6927cacf2b10d4fa80c1a2d407512ef9397c59c6; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in 53eb7bd09aace72fa17510d80e0caf5ca058c231; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in afa9036b8c9963947b487c36e332df6a42c96fcb; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in 65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e; From a7c9c5f4af7f6098da68705fc5d86565d0728ef7 · fixed in 277740023def559a4a2ddc3e8e784ee37a0f16a9
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.10.266; From 5.11.0 · fixed in 5.15.217; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.142; From 6.7.0 · fixed in 6.12.92; From 6.13.0 · fixed in 6.18.34; From 6.19.0 · fixed in 7.0.11
References 8
git.kernel.org
- stable/c/903f7688ffeb9b323d70652c01f554bd4ba2a3d6
- stable/c/dd2f9dd83c68abd7ba7ded7075290b016cb7ecd0
- stable/c/6927cacf2b10d4fa80c1a2d407512ef9397c59c6
- stable/c/d38ba387244e5c5f7db3e11ea98bc2c7beccb0c0
- stable/c/53eb7bd09aace72fa17510d80e0caf5ca058c231
- stable/c/afa9036b8c9963947b487c36e332df6a42c96fcb
- stable/c/65edb3b0822cfe5041be8fbabebd57e2e5ad9f4e
- stable/c/277740023def559a4a2ddc3e8e784ee37a0f16a9