net/smc: check smcd_v2_ext_offset when receiving proposal msg
- 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.271, 5.15.176, 6.1.122, 6.6.68, 6.12.7
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: net/smc: check smcd_v2_ext_offset when receiving proposal msg When receiving proposal msg in server, the field smcd_v2_ext_offset in proposal msg is from the remote client and can not be fully trusted. Once the value of smcd_v2_ext_offset exceed the max value, there has the chance to access wrong address, and crash may happen. This patch checks the value of smcd_v2_ext_offset before using it.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5c21c4ccafe85906db809de3af391fd434df8a27 · fixed in 35da53027c1f2efdd7d0177dc00584134204761a; From 5c21c4ccafe85906db809de3af391fd434df8a27 · fixed in a36364d8d4fabb105001f992fb8ff2d3546203d6; From 5c21c4ccafe85906db809de3af391fd434df8a27 · fixed in e1cc8be2a785a8f1ce1f597f3e608602c5fccd46; From 5c21c4ccafe85906db809de3af391fd434df8a27 · fixed in 935caf324b445fe73d7708fae6f7176fb243f357; From 5c21c4ccafe85906db809de3af391fd434df8a27 · fixed in 48d5a8a304a643613dab376a278f29d3e22f7c34; From 5c21c4ccafe85906db809de3af391fd434df8a27 · fixed in 9ab332deb671d8f7e66d82a2ff2b3f715bc3a4ad
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.176; From 5.16.0 · fixed in 6.1.122; From 6.2.0 · fixed in 6.6.68; From 6.7.0 · fixed in 6.12.7