linux-cve-announce - CVE-2022-50272: media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091505-CVE-2022-50272-4120@gregkh>
Date: Mon, 15 Sep 2025 16:21:14 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50272: media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()

Wei Chen reports a kernel bug as blew:

general protection fault, probably for non-canonical address
KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
...
Call Trace:
<TASK>
__i2c_transfer+0x77e/0x1930 drivers/i2c/i2c-core-base.c:2109
i2c_transfer+0x1d5/0x3d0 drivers/i2c/i2c-core-base.c:2170
i2cdev_ioctl_rdwr+0x393/0x660 drivers/i2c/i2c-dev.c:297
i2cdev_ioctl+0x75d/0x9f0 drivers/i2c/i2c-dev.c:458
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0x90 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fd834a8bded

In az6027_i2c_xfer(), if msg[i].addr is 0x99,
a null-ptr-deref will caused when accessing msg[i].buf.
For msg[i].len is 0 and msg[i].buf is null.

Fix this by checking msg[i].len in az6027_i2c_xfer().

The Linux kernel CVE team has assigned CVE-2022-50272 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 4.9.337 with commit 2b6a8a1a32746981044e7ab06649c804acb4068a
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 4.14.303 with commit c712d1ccbfb787620422b437a5b8fac0802547bd
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 4.19.270 with commit 7abfe467cd685f5da7ecb415441e45e3e4e2baa8
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 5.4.229 with commit 8b256d23361c51aa4b7fdb71176c1ca50966fb39
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 5.10.163 with commit 559891d430e3f3a178040c4371ed419edbfa7d65
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 5.15.86 with commit 210fcf64be4db82c0e190e74b5111e4eef661a7a
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 6.0.16 with commit 6fbc44731a4665cbe92a5090e9804a388a72214b
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 6.1.2 with commit 6b60cf73a931af34b7a0a3f467a79d9fe0df2d70
	Issue introduced in 2.6.34 with commit 76f9a820c8672ada12ffa0903652c9e6f2429462 and fixed in 6.2 with commit 0ed554fd769a19ea8464bb83e9ac201002ef74ad

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-2022-50272
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/usb/dvb-usb/az6027.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/2b6a8a1a32746981044e7ab06649c804acb4068a
	https://git.kernel.org/stable/c/c712d1ccbfb787620422b437a5b8fac0802547bd
	https://git.kernel.org/stable/c/7abfe467cd685f5da7ecb415441e45e3e4e2baa8
	https://git.kernel.org/stable/c/8b256d23361c51aa4b7fdb71176c1ca50966fb39
	https://git.kernel.org/stable/c/559891d430e3f3a178040c4371ed419edbfa7d65
	https://git.kernel.org/stable/c/210fcf64be4db82c0e190e74b5111e4eef661a7a
	https://git.kernel.org/stable/c/6fbc44731a4665cbe92a5090e9804a388a72214b
	https://git.kernel.org/stable/c/6b60cf73a931af34b7a0a3f467a79d9fe0df2d70
	https://git.kernel.org/stable/c/0ed554fd769a19ea8464bb83e9ac201002ef74ad