CVE-2026-0117
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_dec_dqbuf of mfc_dec_v4l2.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege 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 · high confidenceA bounds check error in the mfc_dec_dqbuf function of the MFC (Multi-Format Codec) V4L2 video decoder driver causes an out-of-bounds write vulnerability. This allows a local attacker to escalate privileges to root without needing user interaction or additional execution privileges.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 device is running AndroidCheck /system/build.prop or run 'getprop ro.build.version.release' to verify the operating system is Google AndroidAffected if Device is running any version of Google Android and uses the MFC video decoder driver
-
Identify MFC driver presenceCheck if the MFC (Multi-Format Codec) kernel module is loaded by examining /proc/modules or searching for 'mfc' in /proc/devices; also check kernel config for CONFIG_VIDEO_SAMSUNG_MFCAffected if MFC V4L2 driver is compiled or loaded on the device
-
Locate vulnerable driver fileSearch for mfc_dec_v4l2.c in the kernel source tree or /sys/module/ directory; check /vendor or /kernel directories for Samsung Exynos MFC driver filesAffected if The mfc_dec_v4l2.c source file exists in the system's driver implementation
-
Verify V4L2 video decoder usageCheck if V4L2 video decoder is active by examining /dev/video* devices or running 'v4l2-ctl --list-devices' if available; look for MFC decoder nodesAffected if V4L2 MFC video decoder device nodes are accessible on the system
-
Check kernel version against patch availabilityCompare the running kernel version with the vendor security bulletin; review the kernel build configuration for CONFIG_VIDEO_MFC_V5 or similar MFC version flagsAffected if Kernel is an unpatched Android build containing the MFC V4L2 driver without the bounds check fix in mfc_dec_dqbuf
The device is affected if it runs Google Android with the Samsung MFC (Multi-Format Codec) V4L2 video decoder driver present and the mfc_dec_dqbuf function lacks the corrected bounds check from the vendor patch.
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 the vendor-supplied kernel patch to correct the bounds check in mfc_dec_v4l2.c and rebuild the MFC kernel module; prioritize patching given the high severity and local privilege escalation capability.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0117 — 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-0117 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