Kernel memory access via connector index underflow
Published Dec 27, 2024 · Updated May 11, 2026
Improper array-index validation in Linux 5.6 through 6.11.10 and 6.12 through 6.12.1 allows local users to access memory before a connector array. ucsi_ccg_sync_control() derives con_index from a user-controlled debugfs command and subtracts one before indexing the UCSI connector array without rejecting zero. Reaching the path requires low-privilege local access to debugfs and the affected USB Type-C driver; the access exposes or corrupts kernel memory or interrupts host operation.
Summary
What happened
Improper array-index validation in Linux 5.6 through 6.11.10 and 6.12 through 6.12.1 allows local users to access memory before a connector array. ucsi_ccg_sync_control() derives con_index from a user-controlled debugfs command and subtracts one before indexing the UCSI connector array without rejecting zero. Reaching the path requires low-privilege local access to debugfs and the affected USB Type-C driver; the access exposes or corrupts kernel memory or interrupts host operation.
The record
- CVE
- CVE-2024-53203
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=170a6726d0e266f2c8f306e3d61715c32f4ee41e <0e66fd8e5a2e45c7dacfc9178ba702153f4a61a8
- Affected versionversion=170a6726d0e266f2c8f306e3d61715c32f4ee41e <56971710cd541f2f05160a84b3183477d34a1be9
- Affected versionversion=170a6726d0e266f2c8f306e3d61715c32f4ee41e <627c2a5056aba42a8a96a8fffe8996aeccf919a9
- Affected versionversion=170a6726d0e266f2c8f306e3d61715c32f4ee41e <e15fd96c0b701c53f9006bcc836eaeb35a05a023
- Affected versionversion=170a6726d0e266f2c8f306e3d61715c32f4ee41e <e44189455c62469eb91d383ce9103d54c1f807a3
- Affected versionversion=170a6726d0e266f2c8f306e3d61715c32f4ee41e <e56aac6e5a25630645607b6856d4b2a17b2311a5
- Affected versionversion=170a6726d0e266f2c8f306e3d61715c32f4ee41e <ef92cd55289a282910575c5b9d87f646f2d39b38
- Affected versionversion=5.6
What conditions does exploitation require?
What is affected?
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