CARCOM code execution via shared physical memory
Published Jun 28, 2025 · Updated Jun 30, 2025
Improper access control in JOYNEXT MIB3 OI MQB 0304 and earlier allows local users with root access to execute code on the CARCOM core. The R-CAR M3 main Linux cores and CARCOM core share physical memory without restrictions, so the main OS can read or overwrite CARCOM memory directly. Root control of the main OS is required; exploitation permits CARCOM code execution and infotainment CAN reads and writes, while CAN3 filtering limits safety-critical buses.
Summary
What happened
Improper access control in JOYNEXT MIB3 OI MQB 0304 and earlier allows local users with root access to execute code on the CARCOM core. The R-CAR M3 main Linux cores and CARCOM core share physical memory without restrictions, so the main OS can read or overwrite CARCOM memory directly. Root control of the main OS is required; exploitation permits CARCOM code execution and infotainment CAN reads and writes, while CAN3 filtering limits safety-critical buses.
The record
- CVE
- CVE-2023-28907
- Published
- Jun 28, 2025
- Updated
- Jun 30, 2025
- Vendor
- JOYNEXT GmbH
- Product
- JOYNEXT MIB3 OI MQB
- Classifications
- CWE-284
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 28, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 2025Record 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=0 <=0304
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