AndroidOperating system · Google

CVE-2022-39847

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-07

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

55/100

Remediation priority · Elevated

Zero-click

Official description

NVD · unedited

Use after free vulnerability in set_nft_pid and signal_handler function of NFC driver prior to SMR Oct-2022 Release 1 allows attackers to perform malicious actions.

Technical summary

dbcve analysis · moderate confidence

Use after free vulnerability in the set_nft_pid and signal_handler functions of Samsung's NFC driver allows attackers to perform malicious actions. The vulnerability exists in devices running firmware prior to the SMR October 2022 Release 1, where memory is accessed after being freed, potentially enabling arbitrary code execution or privilege escalation.

MitigationApply the Samsung SMR Oct-2022 Release 1 or later security patch, which contains the vendor fix for this NFC driver vulnerability. Users should ensure their devices receive monthly security updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

AndroidOperating system

Affected:= 10.0= 11.0= 12.0

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify device manufacturer

Check if the device is a Samsung Galaxy device. On Android, go to Settings > About Phone > Manufacturer or Model, or run: `getprop ro.product.manufacturer`

Affected if Device is NOT a Samsung manufacturer - the Samsung NFC driver is not present on non-Samsung devices
Verify Android version

Check Settings > About Phone > Android version, or run: `getprop ro.build.version.release`

Affected if Android version is 10.0, 11.0, or 12.0 - these specific versions are listed as affected
Check SMR firmware version

On Samsung device, go to Settings > About Phone > Software information > Build number, or run: `getprop ro.build.version.sem` to view the Samsung Maintenance Release version

Affected if SMR version is earlier than Oct-2022 Release 1 - the vulnerability exists in versions prior to the fix release
Confirm NFC is enabled

Check if NFC is turned on: go to Settings > Connections > NFC and contactless payments, or run: `settings get secure nfc_on` (returns 1 if enabled, 0 if disabled)

Affected if NFC is enabled - the vulnerable NFC driver code is only reached when NFC functionality is active

A Samsung device on Android 10.0, 11.0, or 12.0 with an SMR version earlier than Oct-2022 Release 1 and NFC enabled is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the Samsung SMR Oct-2022 Release 1 or later security patch, which contains the vendor fix for this NFC driver vulnerability. Users should ensure their devices receive monthly security updates.

Recommended fix High confidence

SMR Oct-2022 Release 1 (or later security update)

1. Identify your Samsung device model number (found in Settings > About Phone)
2. Check for a system software update by going to Settings > Software Update > Download and install
3. Ensure the device updates to the SMR Oct-2022 Release 1 or later security patch level
4. Verify the update was applied by checking Settings > Software Update > SMR Oct-2022 Release 1 or later in the security patch level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory

Consultation8.0 h
Implementation2.0 h
Testing4.0 h
Review / QA2.0 h

16.0 hours of engineering $2,920

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-39847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

security.samsungmobile.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39847 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-39847?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.1%

Affects: Android

Remediation

Need this fixed?

Fix this in Android 16 hrs · High

Typical engagement from $2,920

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-39847 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References