[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091718-CVE-2023-53336-0abd@gregkh>
Date: Wed, 17 Sep 2025 16:56:35 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53336: media: ipu-bridge: Fix null pointer deref on SSDB/PLD parsing warnings
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: ipu-bridge: Fix null pointer deref on SSDB/PLD parsing warnings
When ipu_bridge_parse_rotation() and ipu_bridge_parse_orientation() run
sensor->adev is not set yet.
So if either of the dev_warn() calls about unknown values are hit this
will lead to a NULL pointer deref.
Set sensor->adev earlier, with a borrowed ref to avoid making unrolling
on errors harder, to fix this.
The Linux kernel CVE team has assigned CVE-2023-53336 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.16 with commit 485aa3df0dffa62d347ea4e0116f549338accc59 and fixed in 6.4.16 with commit 3de35e29cfddfe6bff762b15bcfe8d80bebac6cb
Issue introduced in 5.16 with commit 485aa3df0dffa62d347ea4e0116f549338accc59 and fixed in 6.5.3 with commit e08b091e33ecf6e4cb2c0c5820a69abe7673280b
Issue introduced in 5.16 with commit 485aa3df0dffa62d347ea4e0116f549338accc59 and fixed in 6.6 with commit 284be5693163343e1cf17c03917eecd1d6681bcf
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-2023-53336
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/pci/intel/ipu-bridge.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/3de35e29cfddfe6bff762b15bcfe8d80bebac6cb
https://git.kernel.org/stable/c/e08b091e33ecf6e4cb2c0c5820a69abe7673280b
https://git.kernel.org/stable/c/284be5693163343e1cf17c03917eecd1d6681bcf
Powered by blists - more mailing lists