CVE-2015-9218 [Medium] | Security Vulnerability in Msm8909w Firmware

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, SD 845, SDM630, SDM636, SDM660, and Snapdragon_High_Med_2016, when processing bad HEVC clips, the DPB fills, and with no error handling for DPB being full, a hang occurs.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.05%	0.19%	+0.15%
2	2025-03-30	0.07%	0.05%	-0.02%
3	2025-03-29	—	0.07%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.05%

0.19%

+0.15%

2025-03-30

0.07%

0.05%

-0.02%

2025-03-29

—

0.07%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.0	MEDIUM	`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]
4.9	2.0	MEDIUM	`AV:L/AC:L/Au:N/C:N/I:N/A:C` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:N) No integrity impact. Availability impact (A:C) Complete availability impact.	3.9	6.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.0

MEDIUM

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

4.9

2.0

MEDIUM

AV:L/AC:L/Au:N/C:N/I:N/A:C Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:N): No integrity impact.
Availability impact (A:C): Complete availability impact.

3.9

6.9

[email protected]

Affected software / configurations for CVE-2015-9218

Vendor	Product	Version	Raw CPE
qualcomm	msm8909w_firmware	—	cpe:2.3:o:qualcomm:msm8909w_firmware:-:::::::*
qualcomm	sd_210_firmware	—	cpe:2.3:o:qualcomm:sd_210_firmware:-:::::::*
qualcomm	sd_212_firmware	—	cpe:2.3:o:qualcomm:sd_212_firmware:-:::::::*
qualcomm	sd_205_firmware	—	cpe:2.3:o:qualcomm:sd_205_firmware:-:::::::*
qualcomm	sd_400_firmware	—	cpe:2.3:o:qualcomm:sd_400_firmware:-:::::::*
qualcomm	sd_410_firmware	—	cpe:2.3:o:qualcomm:sd_410_firmware:-:::::::*
qualcomm	sd_412_firmware	—	cpe:2.3:o:qualcomm:sd_412_firmware:-:::::::*
qualcomm	sd_425_firmware	—	cpe:2.3:o:qualcomm:sd_425_firmware:-:::::::*
qualcomm	sd_430_firmware	—	cpe:2.3:o:qualcomm:sd_430_firmware:-:::::::*
qualcomm	sd_450_firmware	—	cpe:2.3:o:qualcomm:sd_450_firmware:-:::::::*
qualcomm	sd_625_firmware	—	cpe:2.3:o:qualcomm:sd_625_firmware:-:::::::*
qualcomm	sd_650_firmware	—	cpe:2.3:o:qualcomm:sd_650_firmware:-:::::::*
qualcomm	sd_652_firmware	—	cpe:2.3:o:qualcomm:sd_652_firmware:-:::::::*
qualcomm	sd_800_firmware	—	cpe:2.3:o:qualcomm:sd_800_firmware:-:::::::*
qualcomm	sd_808_firmware	—	cpe:2.3:o:qualcomm:sd_808_firmware:-:::::::*
qualcomm	sd_810_firmware	—	cpe:2.3:o:qualcomm:sd_810_firmware:-:::::::*
qualcomm	sd_820_firmware	—	cpe:2.3:o:qualcomm:sd_820_firmware:-:::::::*
qualcomm	sd_835_firmware	—	cpe:2.3:o:qualcomm:sd_835_firmware:-:::::::*
qualcomm	sd_845_firmware	—	cpe:2.3:o:qualcomm:sd_845_firmware:-:::::::*
qualcomm	sdm630_firmware	—	cpe:2.3:o:qualcomm:sdm630_firmware:-:::::::*
qualcomm	sdm636_firmware	—	cpe:2.3:o:qualcomm:sdm636_firmware:-:::::::*
qualcomm	sd_427_firmware	—	cpe:2.3:o:qualcomm:sd_427_firmware:-:::::::*
qualcomm	sd_435_firmware	—	cpe:2.3:o:qualcomm:sd_435_firmware:-:::::::*
qualcomm	sdm660_firmware	—	cpe:2.3:o:qualcomm:sdm660_firmware:-:::::::*

References for CVE-2015-9218

URL	Tags
http://www.securityfocus.com/bid/103671	Third Party Advisory VDB Entry
https://source.android.com/security/bulletin/2018-04-01	Vendor Advisory

URL

CVE-2015-9218

Exploit prediction scoring system (EPSS) score for CVE-2015-9218

Common vulnerability scoring system (CVSS) metrics for CVE-2015-9218

Weakness enumeration for CVE-2015-9218

Affected software / configurations for CVE-2015-9218

References for CVE-2015-9218