CVE-2026-0147
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.
NVD · uneditedIn __mfc_core_nal_q_get_dec_metadata_sei_nal of mfc_core_nal_q.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
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.
dbcve analysis · moderate confidenceAn out-of-bounds write vulnerability exists in the `__mfc_core_nal_q_get_dec_metadata_sei_nal` function within mfc_core_nal_q.c due to a missing bounds check. This allows writing beyond allocated memory boundaries, enabling remote code execution without requiring additional privileges or user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE dataall versionsCVSS 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.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the device runs AndroidCheck /system/build.prop or run 'getprop ro.build.version.release' to verify the OS is AndroidAffected if The device is running any Android version - all versions are affected per the CVE
-
Identify if MFC driver is presentCheck for MFC kernel modules: ls /proc/modules | grep mfc or check /sys/module/ for mfc_core module presenceAffected if MFC (Multi-Format Codec) driver module is loaded on the device - the vulnerability exists in mfc_core_nal_q.c
-
Check if hardware video decoding is enabledExamine /proc/cmdline or kernel config for mfc-related parameters, or check /dev/video* nodes for MFC device accessAffected if Hardware-accelerated video decoding via MFC is available/enabled on the device
-
Verify NAL processing is in useMonitor process activity during video playback: check which processes access /dev/video* or use 'cat /proc/*/fd' to find video device file descriptorsAffected if Any application is performing video decoding that utilizes NAL (Network Abstraction Layer) processing through the MFC driver
-
Check for untrusted video input exposureReview running services and apps that accept video input from network sources, external apps, or untrusted contentAffected if The device processes video from untrusted sources (network streams, third-party app video input) using the MFC codec
A device is affected if it runs Android with the MFC hardware codec driver present and processes video content through NAL processing, since the out-of-bounds write flaw in mfc_core_nal_q.c requires the MFC driver to be active for exploitation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patches when available. In the interim, restrict exposure to untrusted video input streams and minimize the attack surface by disabling unnecessary MFC/nal processing features if possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0147 in production — separate from our analysis above.
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.
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.
- 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