Local kernel crash via premature control initialization
Published May 8, 2026 · Updated May 8, 2026
NULL pointer dereference in the Linux kernel OV5647 camera driver allows local users to crash the kernel during device probe. The probe calls ov5647_init_controls() before v4l2_i2c_subdev_init() establishes subdevice data, leaving v4l2_get_subdevdata() without a valid i2c_client on the error path. Reachability requires the OV5647 driver and a probe-time control initialization error; the reported consequence is an availability-only kernel segfault.
Summary
What happened
NULL pointer dereference in the Linux kernel OV5647 camera driver allows local users to crash the kernel during device probe. The probe calls ov5647_init_controls() before v4l2_i2c_subdev_init() establishes subdevice data, leaving v4l2_get_subdevdata() without a valid i2c_client on the error path. Reachability requires the OV5647 driver and a probe-time control initialization error; the reported consequence is an availability-only kernel segfault.
The record
- CVE
- CVE-2026-43312
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <2dedda97a64e7735844609c6c77c0dd953d73833
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <59e372aa4cf60e2500eba7f978acdcb18bb49032
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <cabd025182cfed4a19b3aab57493e312d681e398
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <eee13cbccacb6d0a3120c126b8544030905b069d
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <f2a1998bc0053ebfe137f65081ed13afd9f34502
- Affected versionversion=4974c2f19fd810ec9a4e534bfc69e176256b7a03 <fb69e4842f5b463ff5f121d2ac7746014e3477ea
- Affected versionversion=5.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo