From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43312: media: i2c: ov5647: Initialize subdev before controls
Date: Fri, 8 May 2026 15:12:17 +0200 [thread overview]
Message-ID: <2026050800-CVE-2026-43312-b723@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2026-43312 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 5.15.202 with commit f2a1998bc0053ebfe137f65081ed13afd9f34502
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 6.1.165 with commit 59e372aa4cf60e2500eba7f978acdcb18bb49032
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 6.6.128 with commit cabd025182cfed4a19b3aab57493e312d681e398
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 6.12.75 with commit 2dedda97a64e7735844609c6c77c0dd953d73833
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 6.18.16 with commit 8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 6.19.6 with commit fb69e4842f5b463ff5f121d2ac7746014e3477ea
Issue introduced in 5.12 with commit 4974c2f19fd810ec9a4e534bfc69e176256b7a03 and fixed in 7.0 with commit eee13cbccacb6d0a3120c126b8544030905b069d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-43312
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/media/i2c/ov5647.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f2a1998bc0053ebfe137f65081ed13afd9f34502
https://git.kernel.org/stable/c/59e372aa4cf60e2500eba7f978acdcb18bb49032
https://git.kernel.org/stable/c/cabd025182cfed4a19b3aab57493e312d681e398
https://git.kernel.org/stable/c/2dedda97a64e7735844609c6c77c0dd953d73833
https://git.kernel.org/stable/c/8ecb21c20387cc0c8aa00489a21ccc69f6b0f5d1
https://git.kernel.org/stable/c/fb69e4842f5b463ff5f121d2ac7746014e3477ea
https://git.kernel.org/stable/c/eee13cbccacb6d0a3120c126b8544030905b069d
reply other threads:[~2026-05-08 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050800-CVE-2026-43312-b723@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox