CVE-2026-43312: media: i2c: ov5647: Initialize subdev before controls
Noroxi assessment
Priority: Monitor (action score 22/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.12% (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 2dedda97a64e7735844609c6c77c0dd953d73833, 59e372aa4cf60e2500eba7f978acdcb18bb49032, 8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2dedda97a64e7735844609c6c77c0dd953d73833, 59e372aa4cf60e2500eba7f978acdcb18bb49032, 8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1 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: i2c: ov5647: Initialize subdev before controls In ov5647_init_controls() we call v4l2_get_subdevdata, but it is initialized by v4l2_i2c_subdev_init() in the probe, which currently happens after init_controls(). This can result in a segfault if the error condition is hit, and we try to access i2c_client, so fix the order.
- Published
- May 8, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.12 and later · before 5.15.202
- linux linux kernel5.16 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
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
- 5.12affected
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before f2a1998bc0053ebfe137f65081ed13afd9f34502affected · git
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before 59e372aa4cf60e2500eba7f978acdcb18bb49032affected · git
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before cabd025182cfed4a19b3aab57493e312d681e398affected · git
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before 2dedda97a64e7735844609c6c77c0dd953d73833affected · git
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before 8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1affected · git
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before fb69e4842f5b463ff5f121d2ac7746014e3477eaaffected · git
- 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and later · before eee13cbccacb6d0a3120c126b8544030905b069daffected · git
- before 5.12not affected · semver
- 5.15.202 and later · up to and including 5.15.*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.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43306May 8, 2026 · bpf: crypto: Use the correct destructor kfunc type22Monitor
- ← EarlierCVE-2026-43307May 8, 2026 · iio: accel: adxl380: Avoid reading more entries than present in FIFO31Monitor
- Later →CVE-2026-43313May 8, 2026 · ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4()22Monitor
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 | 2dedda97a64e7735844609c6c77c0dd953d73833 | Vendor (CNA) |
| Linux Linux | 59e372aa4cf60e2500eba7f978acdcb18bb49032 | Vendor (CNA) |
| Linux Linux | 8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1 | Vendor (CNA) |
| Linux Linux | cabd025182cfed4a19b3aab57493e312d681e398 | Vendor (CNA) |
| Linux Linux | eee13cbccacb6d0a3120c126b8544030905b069d | Vendor (CNA) |
| Linux Linux | f2a1998bc0053ebfe137f65081ed13afd9f34502 | Vendor (CNA) |
| Linux Linux | fb69e4842f5b463ff5f121d2ac7746014e3477ea | Vendor (CNA) |
| debian:linux | 6.1.170-1 · 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-0213 · May 12, 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (6 more)Show less
- git.kernel.org/stable/c/59e372aa4cf60e2500eba7f978acdcb18bb49032
- git.kernel.org/stable/c/8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1
- git.kernel.org/stable/c/cabd025182cfed4a19b3aab57493e312d681e398
- git.kernel.org/stable/c/eee13cbccacb6d0a3120c126b8544030905b069d
- git.kernel.org/stable/c/f2a1998bc0053ebfe137f65081ed13afd9f34502
- git.kernel.org/stable/c/fb69e4842f5b463ff5f121d2ac7746014e3477ea
Vendor advisories and official records. Exploit/PoC links are deliberately left out.