Local system crash via unchecked SMBus block length
Published Sep 9, 2022 · Updated Aug 3, 2024
Buffer overflow in the Linux kernel before 5.19 allows local users to crash the system through an iSMT SMBus ioctl. In ismt_access(), the I2C_SMBUS_BLOCK_PROC_CALL branch trusts user-controlled data->block[0] as a memcpy length and writes past dma_buffer when it exceeds I2C_SMBUS_BLOCK_MAX. Exploitation requires local low-privileged access to the ioctl on a system using the iSMT driver with a supported Intel S12xx SMBus controller.
Summary
What happened
Buffer overflow in the Linux kernel before 5.19 allows local users to crash the system through an iSMT SMBus ioctl. In ismt_access(), the I2C_SMBUS_BLOCK_PROC_CALL branch trusts user-controlled data->block[0] as a memcpy length and writes past dma_buffer when it exceeds I2C_SMBUS_BLOCK_MAX. Exploitation requires local low-privileged access to the ioctl on a system using the iSMT driver with a supported Intel S12xx SMBus controller.
The record
- CVE
- CVE-2022-3077
- Published
- Sep 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=fixed in kernel 5.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo