CVE-2026-68210: media: stm32: dcmi: unregister notifier on probe failure
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 084973ebd67b28f0945c5d45408f86c58b540110, 222a9301b086852b90d3b092fef436c3f4e927c4, 37ff63c5d7119cbc5c6bacdcc658add6008a8e1f; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 084973ebd67b28f0945c5d45408f86c58b540110, 222a9301b086852b90d3b092fef436c3f4e927c4, 37ff63c5d7119cbc5c6bacdcc658add6008a8e1f; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: media: stm32: dcmi: unregister notifier on probe failure dcmi_graph_init() registers the async notifier before dcmi_probe() toggles the reset line. If reset_control_assert() or reset_control_deassert() fails afterwards, probe returns through err_cleanup and the driver core will not call dcmi_remove(). Unregister the notifier before cleaning it up on that error path, matching the successful remove path and the V4L2 async notifier lifetime rules. [hverkuil: added Fixes tag]
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.20affected
- d079f94c90469f413920b9f2b201537fac2ceb06 and later · before 222a9301b086852b90d3b092fef436c3f4e927c4affected · git
- d079f94c90469f413920b9f2b201537fac2ceb06 and later · before 37ff63c5d7119cbc5c6bacdcc658add6008a8e1faffected · git
- d079f94c90469f413920b9f2b201537fac2ceb06 and later · before 6c6f22b7e6cbc4e8c1e359fc9b190419391c3db7affected · git
- d079f94c90469f413920b9f2b201537fac2ceb06 and later · before 931abe1deb65b919d23fa203d7f6d6fbd4fccd8eaffected · git
- d079f94c90469f413920b9f2b201537fac2ceb06 and later · before 4b7ee504969e074725e439c949f2483e5fa5572aaffected · git
- d079f94c90469f413920b9f2b201537fac2ceb06 and later · before 084973ebd67b28f0945c5d45408f86c58b540110affected · git
- before 4.20not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.148 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68208Aug 10, 2026 · media: ti: vpe: Fix the error code of devm_kzalloc() in vip_probe_slice()0Monitor
- ← EarlierCVE-2026-68209Aug 10, 2026 · media: sun4i-csi: Return queued buffers on start_streaming() failure31Monitor
- Later →CVE-2026-68212Aug 10, 2026 · media: saa7134: Fix a possible memory leak in saa7134_video_init10Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 084973ebd67b28f0945c5d45408f86c58b540110 | Vendor (CNA) |
| Linux Linux | 222a9301b086852b90d3b092fef436c3f4e927c4 | Vendor (CNA) |
| Linux Linux | 37ff63c5d7119cbc5c6bacdcc658add6008a8e1f | Vendor (CNA) |
| Linux Linux | 4b7ee504969e074725e439c949f2483e5fa5572a | Vendor (CNA) |
| Linux Linux | 6c6f22b7e6cbc4e8c1e359fc9b190419391c3db7 | Vendor (CNA) |
| Linux Linux | 931abe1deb65b919d23fa203d7f6d6fbd4fccd8e | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/222a9301b086852b90d3b092fef436c3f4e927c4
- git.kernel.org/stable/c/37ff63c5d7119cbc5c6bacdcc658add6008a8e1f
- git.kernel.org/stable/c/4b7ee504969e074725e439c949f2483e5fa5572a
- git.kernel.org/stable/c/6c6f22b7e6cbc4e8c1e359fc9b190419391c3db7
- git.kernel.org/stable/c/931abe1deb65b919d23fa203d7f6d6fbd4fccd8e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.