Project

General

Profile

ExynosModemIsolation » History » Version 10

Denis 'GNUtoo' Carikli, 03/02/2020 11:08 AM
update list of affected devices

1 9 Denis 'GNUtoo' Carikli
h1. Exynos 3110 modem isolation
2 1 Paul Kocialkowski
3 7 Denis 'GNUtoo' Carikli
This article talks about a very serious freedom, privacy and security issue we found during Replicant development.
4 1 Paul Kocialkowski
5 9 Denis 'GNUtoo' Carikli
We found that the modem wasn't isolated and was potentially able to read and write part of the RAM used by Replicant on several devices with an Exynos 3110.
6 7 Denis 'GNUtoo' Carikli
7
h2. Affected devices:
8
9 10 Denis 'GNUtoo' Carikli
At least the following devices are affected:
10
11
* Galaxy S (GT-I9000)
12 7 Denis 'GNUtoo' Carikli
* Nexus S (GT-I9020)
13
* Nexus S (GT-I9020A)
14
* Nexus S (GT-I9023)
15
16 1 Paul Kocialkowski
h2. Hardware design matrix
17
18
|_. *Chip* |_. Controlled by the CPU |_. Controlled by the modem |_. Connected to the modem |
19
| GPS | Yes | No | No? |
20
| Audio CODEC | Yes | No | Yes |
21
| NAND | Yes | No | No |
22 3 Paul Kocialkowski
| RAM | Yes | Yes (96Mib at least) | Yes |
23 1 Paul Kocialkowski
| WiFi/Bluetooth | Yes | No | No |
24
| Sensors | Yes | No | No |
25
| NFC | Yes | No | No |
26
| Camera | Yes | No | No |
27
28 5 Denis 'GNUtoo' Carikli
h2. Modem isolation
29 1 Paul Kocialkowski
30 5 Denis 'GNUtoo' Carikli
The modem (XMM 6160) is separated from the SoC and communicates with it via serial over 16Mib of shared memory: this is bad since it means that RAM is compromised (at least 80Mib + 16Mib = 96Mib) and can be used to spy.
31
Regarding audio, the modem is connected to the CODEC but cannot control it (the SoC has to enable routing from/to the modem).
32
There is no evidence that the GPS is connected to the modem, but since we cannot check on the hardware, there is no proof it's not connected to it either. The SoC is able to control the GPS power though, so we can keep it off.
33
Since the SoC has to load the modem firmware over the (fake) serial, and following the datasheets, the modem is not connected to the NAND.
34
35 3 Paul Kocialkowski
The modem is able to spy on (at least) 96 Mib of the main memory. So far, we cannot tell:
36
* if it can only spy 80Mib or the full memory
37 1 Paul Kocialkowski
* if it can be fixed or not
38 4 Paul Kocialkowski
39
The Linux kernel is being loaded at the beginning of the shared memory bank (0x30000000), however the kernel should be off when it loads.
40 1 Paul Kocialkowski
41
h3. Kernel details
42
43 5 Denis 'GNUtoo' Carikli
In "kernel-crespo/arch/arm/mach-s5pv210/dev-herring-phone.c":https://git.replicant.us/replicant/kernel_samsung_crespo/tree/arch/arm/mach-s5pv210/dev-herring-phone.c#n49 we have:
44 1 Paul Kocialkowski
<pre>
45
static struct resource mdmctl_res[] = {
46
[...]
47
        [2] = {
48
                .name = "onedram",
49
                .start = (S5PV210_PA_SDRAM + 0x05000000),
50
                .end = (S5PV210_PA_SDRAM + 0x05000000 + SZ_16M - 1),
51
                .flags = IORESOURCE_MEM,
52
        },
53
};
54
</pre>
55
56
* S5PV210_PA_SDRAM is 0x30000000
57 3 Paul Kocialkowski
* 0x05000000 is 80Mib
58 1 Paul Kocialkowski
* mdmctl_res goes in a platform device struct which is passed to the modem driver:
59
60
<pre>
61
static struct platform_device modemctl = {
62
        .name = "modemctl",
63
        .id = -1,
64
        .num_resources = ARRAY_SIZE(mdmctl_res),
65
        .resource = mdmctl_res,
66
        .dev = {
67
                .platform_data = &mdmctl_data,
68
        },
69
};
70
</pre>
71
72 6 Denis 'GNUtoo' Carikli
And in the board file, in "kernel-crespo/arch/arm/mach-s5pv210/mach-herring.c":https://git.replicant.us/replicant/kernel_samsung_crespo/tree/arch/arm/mach-s5pv210/mach-herring.c#n5596 we have: 
73 1 Paul Kocialkowski
<pre>
74
static void __init herring_fixup(struct machine_desc *desc,
75
                struct tag *tags, char **cmdline,
76
                struct meminfo *mi)
77
{
78
        mi->bank[0].start = 0x30000000;
79
        mi->bank[0].size = 80 * SZ_1M;
80
        mi->bank[0].node = 0;
81
</pre>
82
83 3 Paul Kocialkowski
So we can suppose that there is at least one ram chip that is shared between the modem and the main CPU. Avoiding the use of this memory bank would result in loosing 80Mib of memory.
84 4 Paul Kocialkowski
85 8 Denis 'GNUtoo' Carikli
h3. Workaround attempt
86 1 Paul Kocialkowski
87 8 Denis 'GNUtoo' Carikli
It might be possible to limit the amount of damage by relying on the fact that the modem has to be booted by Replicant, and make sure that the RAM chip that is shared with the modem isn't used for other things than this memory sharing.
88
89
This would make us lose about 80Mib of RAM, and the shared memory would still be used for SoC/Modem communication but as the RAM chip would be used only for that, so the modem would not be able read and write problematic data on it.
90
91
We would also need to make sure that the booloader doesn't load the kernel in that region or that the kernel is relocated to some other region before intializing the modem.
92 4 Paul Kocialkowski
93
The current diff with the Nexus S kernel is here, but it doesn't boot at all with the following changes (and mkbootimg changes):
94
95
<pre>
96
diff --git a/arch/arm/configs/herring_defconfig b/arch/arm/configs/herring_defconfig
97
old mode 100755
98
new mode 100644
99
index 11abbf0..99bf3f5
100
--- a/arch/arm/configs/herring_defconfig
101
+++ b/arch/arm/configs/herring_defconfig
102
@@ -1,7 +1,7 @@
103
 #
104
 # Automatically generated make config: don't edit
105
 # Linux kernel version: 2.6.35.7
106
-# Fri Jun  3 07:07:08 2011
107
+# Sun Apr  8 14:40:16 2012
108
 #
109
 CONFIG_ARM=y
110
 CONFIG_HAVE_PWM=y
111
@@ -418,8 +418,8 @@ CONFIG_ALIGNMENT_TRAP=y
112
 #
113
 CONFIG_ZBOOT_ROM_TEXT=0
114
 CONFIG_ZBOOT_ROM_BSS=0
115
-CONFIG_CMDLINE="console=ttyFIQ0"
116
-# CONFIG_CMDLINE_FORCE is not set
117
+CONFIG_CMDLINE="console=ttyFIQ0 no_console_suspend earlyprintk=serial,ttySAC2,115200 androidboot.serialno=3733BAB66DE200EC androidboot.bootloader=I9020XXKA3 androidboot.baseband=I9020XXKB3 androidboot.info=0x4,0x0,1 androidboot.carrier=EUR gain_code=3 s3cfb.bootloaderfb=0x34a00000 mach-herring.lcd_type=0x00000000 oem_state=unlocked"
118
+CONFIG_CMDLINE_FORCE=y
119
 # CONFIG_XIP_KERNEL is not set
120
 # CONFIG_KEXEC is not set
121
 
122
@@ -823,8 +823,6 @@ CONFIG_UEVENT_HELPER_PATH=""
123
 CONFIG_STANDALONE=y
124
 CONFIG_PREVENT_FIRMWARE_BUILD=y
125
 # CONFIG_FW_LOADER is not set
126
-# CONFIG_FIRMWARE_IN_KERNEL is not set
127
-CONFIG_EXTRA_FIRMWARE=""
128
 # CONFIG_DEBUG_DRIVER is not set
129
 # CONFIG_DEBUG_DEVRES is not set
130
 # CONFIG_SYS_HYPERVISOR is not set
131
@@ -835,7 +833,7 @@ CONFIG_MTD=y
132
 CONFIG_MTD_CONCAT=y
133
 CONFIG_MTD_PARTITIONS=y
134
 # CONFIG_MTD_REDBOOT_PARTS is not set
135
-# CONFIG_MTD_CMDLINE_PARTS is not set
136
+CONFIG_MTD_CMDLINE_PARTS=y
137
 # CONFIG_MTD_AFS_PARTS is not set
138
 # CONFIG_MTD_AR7_PARTS is not set
139
 
140
@@ -1191,6 +1189,7 @@ CONFIG_DEVKMEM=y
141
 CONFIG_SERIAL_SAMSUNG=y
142
 CONFIG_SERIAL_SAMSUNG_UARTS_4=y
143
 CONFIG_SERIAL_SAMSUNG_UARTS=4
144
+# CONFIG_SERIAL_SAMSUNG_DEBUG is not set
145
 CONFIG_SERIAL_SAMSUNG_CONSOLE=y
146
 CONFIG_SERIAL_S5PV210=y
147
 # CONFIG_SERIAL_MAX3100 is not set
148
@@ -2046,7 +2045,9 @@ CONFIG_HAVE_ARCH_KGDB=y
149
 CONFIG_DEBUG_USER=y
150
 CONFIG_DEBUG_ERRORS=y
151
 # CONFIG_DEBUG_STACK_USAGE is not set
152
-# CONFIG_DEBUG_LL is not set
153
+CONFIG_DEBUG_LL=y
154
+CONFIG_EARLY_PRINTK=y
155
+# CONFIG_DEBUG_ICEDCC is not set
156
 CONFIG_OC_ETM=y
157
 CONFIG_DEBUG_S3C_UART=2
158
 
159
diff --git a/arch/arm/mach-s5pv210/dev-herring-phone.c b/arch/arm/mach-s5pv210/dev-herring-phone.c
160
index f8798b3..ecef636 100755
161
--- a/arch/arm/mach-s5pv210/dev-herring-phone.c
162
+++ b/arch/arm/mach-s5pv210/dev-herring-phone.c
163
@@ -48,8 +48,8 @@ static struct resource mdmctl_res[] = {
164
 	},
165
 	[2] = {
166
 		.name = "onedram",
167
-		.start = (S5PV210_PA_SDRAM + 0x05000000),
168
-		.end = (S5PV210_PA_SDRAM + 0x05000000 + SZ_16M - 1),
169
+		.start = (0x30000000  + 0x05000000),
170
+		.end = (0x30000000  + 0x05000000 + SZ_16M - 1),
171
 		.flags = IORESOURCE_MEM,
172
 	},
173
 };
174
diff --git a/arch/arm/mach-s5pv210/mach-herring.c b/arch/arm/mach-s5pv210/mach-herring.c
175
index c3a0182..67fa1cf 100755
176
--- a/arch/arm/mach-s5pv210/mach-herring.c
177
+++ b/arch/arm/mach-s5pv210/mach-herring.c
178
@@ -5494,21 +5494,17 @@ static void __init herring_fixup(struct machine_desc *desc,
179
 		struct tag *tags, char **cmdline,
180
 		struct meminfo *mi)
181
 {
182
-	mi->bank[0].start = 0x30000000;
183
-	mi->bank[0].size = 80 * SZ_1M;
184
+	mi->bank[0].start = 0x40000000;
185
+	mi->bank[0].size = 256 * SZ_1M;
186
 	mi->bank[0].node = 0;
187
 
188
-	mi->bank[1].start = 0x40000000;
189
-	mi->bank[1].size = 256 * SZ_1M;
190
-	mi->bank[1].node = 1;
191
-
192
-	mi->bank[2].start = 0x50000000;
193
+	mi->bank[1].start = 0x50000000;
194
 	/* 1M for ram_console buffer */
195
-	mi->bank[2].size = 127 * SZ_1M;
196
-	mi->bank[2].node = 2;
197
-	mi->nr_banks = 3;
198
+	mi->bank[1].size = 127 * SZ_1M;
199
+	mi->bank[1].node = 1;
200
+	mi->nr_banks = 2;
201
 
202
-	ram_console_start = mi->bank[2].start + mi->bank[2].size;
203
+	ram_console_start = mi->bank[1].start + mi->bank[1].size;
204
 	ram_console_size = SZ_1M - SZ_4K;
205
 
206
 	pm_debug_scratchpad = ram_console_start + ram_console_size;
207
</pre>
208
209
<pre>
210
diff --git a/BoardConfigCommon.mk b/BoardConfigCommon.mk
211
index fff6d1b..c09d935 100755
212
--- a/BoardConfigCommon.mk
213
+++ b/BoardConfigCommon.mk
214
@@ -51,10 +51,10 @@ DEFAULT_FB_NUM := 2
215
 
216
 BOARD_NAND_PAGE_SIZE := 4096 -s 128
217
 
218
-BOARD_KERNEL_BASE := 0x30000000
219
+BOARD_KERNEL_BASE := 0x40000000
220
 BOARD_KERNEL_PAGESIZE := 4096
221
-BOARD_KERNEL_CMDLINE := console=ttyFIQ0 no_console_suspend
222
-
223
+BOARD_KERNEL_CMDLINE := console=ttyFIQ0 no_console_suspend earlyprintk=serial,ttySAC2,115200 bootmem_debug
224
+BOARD_FORCE_RAMDISK_ADDRESS := 0x41000000
225
 #TARGET_RECOVERY_UI_LIB := librecovery_ui_crespo
226
 TARGET_RELEASETOOLS_EXTENSIONS := device/samsung/crespo
227
</pre>