CVE-2022-50786 json
media: s5p-mfc: Clear workbit to handle error condition
published 2025-12-30 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-205767
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
media: s5p-mfc: Clear workbit to handle error condition
During error on CLOSE_INSTANCE command, ctx_work_bits was not getting cleared. During consequent mfc execution NULL pointer dereferencing of this context led to kernel panic. This patch fixes this issue by making sure to clear ctx_work_bits always.
Patch / fix
- Linux Linux 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.18, 6.1.4, 6.2
- linux Debian 14, Debian 13, Debian 12 6.1.4-1
debian advisories DEBIAN-CVE-2022-50786
- linux Ubuntu 18.04 LTS 4.15.0-208.220
- linux Ubuntu 20.04 LTS 5.4.0-144.161
- linux Ubuntu 22.04 LTS 5.15.0-69.76
- linux-aws Ubuntu 18.04 LTS 4.15.0-1153.166
- linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
- linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38
ubuntu advisories UBUNTU-CVE-2022-50786
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-syms SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.293.1
- kernel-source SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 4.12.14-122.293.1
- kernel-default SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS, SLE Live Patching 12 SP5 4.12.14-122.293.1
- kgraft-patch-SLE12-SP5_Update_77 SLE Live Patching 12 SP5 1-8.3.1
suse advisories SUSE-SU-2026:0473-1
- git.kernel.org/stable/c/12242bd13ce68acd571b2cce6ab302e154e8a4ee commit
- git.kernel.org/stable/c/640075400c7c577b0f5369b935e22a588773fafa commit
- git.kernel.org/stable/c/8ff64edf9d16e8c277dcc8189794763624e6b4b8 commit
- git.kernel.org/stable/c/ff27800c0a6d81571671b33f696109804d015409 commit
- git.kernel.org/stable/c/09c1fbbe532758e4046c20829f4c0c50b99332dc commit
- git.kernel.org/stable/c/bd1b72f0c39a0d791a087b4e643701a48328ba8e commit
- git.kernel.org/stable/c/d3f3c2fe54e30b0636496d842ffbb5ad3a547f9b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50786 updated
kernel: media: s5p-mfc: Clear workbit to handle error condition
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/12242bd13ce68acd571b2cce6ab302e154e8a4ee
- git.kernel.org /stable/c/640075400c7c577b0f5369b935e22a588773fafa
- git.kernel.org /stable/c/8ff64edf9d16e8c277dcc8189794763624e6b4b8
- git.kernel.org /stable/c/ff27800c0a6d81571671b33f696109804d015409
- git.kernel.org /stable/c/09c1fbbe532758e4046c20829f4c0c50b99332dc
- git.kernel.org /stable/c/bd1b72f0c39a0d791a087b4e643701a48328ba8e
- git.kernel.org /stable/c/d3f3c2fe54e30b0636496d842ffbb5ad3a547f9b
Sources
- CVE List CVE-2022-50786
- NVD CVE-2022-50786
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.