TI-2017-08113 Aliases CVE-2017-11041 GHSA-ff4w-rgwj-fx2j

In all Qualcomm products with Android releases from CAF using the Linux kernel, an output…

LOW 35Published 2017-09-21 · Updated 2024-08-05

Key facts

Attack vector: Local
Privileges required: None
User interaction: Required
Attack complexity: Low
Impact type: —
Confidentiality · integrity · availability: High · High · High
Fix status: No fix listed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA.

Summary

In all Qualcomm products with Android releases from CAF using the Linux kernel, an output buffer is accessed in one thread and can be potentially freed in another.

Why it matters now

EPSS 0.00526 44th percentileScored 2026-11-07

Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
—	—	all versions	—	No fix listed	CNA

— Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPE	Versions	Role	Vendor
cpe:2.3:o:google:android::::::::	up to 8.0	Vulnerable	Google

cpe:2.3:o:google:android:*:*:*:*:*:*:*:* Versions up to 8.0 Vulnerable ·Google

Remediation

No fixed version listed by the sources yet.

Timeline

2026-10-02 Threatist record created from CVE-2017-11041
2026-10-03 Alias added: GHSA-ff4w-rgwj-fx2j

References

Advisory 1

https://source.android.com/security/bulletin/2017-09-01

Other 1

https://source.android.com/security/bulletin/2018-02-01

TI-2026-42236 Improper authorization in Google Android KEVCVSS 3.1HIGH 8.8
TI-2025-30821 Use after free in Google Android KEVCVSS 3.1HIGH 8.8
TI-2023-17777 Improper privilege management in Google Android KEVCVSS 3.1HIGH 8.8
TI-2025-30872 Integer overflow in Google Android KEVCVSS 3.1HIGH 8.4
TI-2024-21766 there is a possible way to bypass due to a logic error in the code. KEVCVSS 3.1HIGH 8.1
TI-2025-30849 Missing authentication in Google Android KEVCVSS 3.1HIGH 7.8

See all 8410 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences