Google Android 14/15/16/16-qpr2 Nfc.h use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$5k-$25k0.00

Summaryinfo

A vulnerability has been found in Google Android 14/15/16/16-qpr2 and classified as critical. This affects an unknown part in the library Nfc.h. The manipulation leads to use after free. This vulnerability is traded as CVE-2025-48641. An attack has to be approached locally. There is no exploit available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in Google Android 14/15/16/16-qpr2 and classified as critical. This issue affects an unknown part in the library Nfc.h. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In multiple functions of Nfc.h, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2025-48641 since 05/22/2025. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/09/2026).

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0569). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Google Android

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.0
NVD Vector: 🔒

ADP CISA Base Score: 7.0
ADP CISA Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Timelineinfo

05/22/2025 CVE reserved
03/02/2026 +284 days Advisory disclosed
03/02/2026 +0 days VulDB entry created
03/09/2026 +7 days VulDB entry last update

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Status: Confirmed

CVE: CVE-2025-48641 (🔒)
GCVE (CVE): GCVE-0-2025-48641
GCVE (VulDB): GCVE-100-348449
CERT Bund: WID-SEC-2026-0569 - Google Android: Mehrere Schwachstellen

scip Labs: https://www.scip.ch/en/?labs.20150917

Entryinfo

Created: 03/02/2026 20:26
Updated: 03/09/2026 21:14
Changes: 03/02/2026 20:26 (56), 03/04/2026 12:23 (20), 03/09/2026 21:14 (6)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!