linux-cve-announce - CVE-2022-49307: tty: synclink_gt: Fix null-pointer-dereference in slgt

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: <2025022635-CVE-2022-49307-246e@gregkh>
Date: Wed, 26 Feb 2025 03:09:41 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49307: tty: synclink_gt: Fix null-pointer-dereference in slgt_clean()

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

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

tty: synclink_gt: Fix null-pointer-dereference in slgt_clean()

When the driver fails at alloc_hdlcdev(), and then we remove the driver
module, we will get the following splat:

[   25.065966] general protection fault, probably for non-canonical address 0xdffffc0000000182: 0000 [#1] PREEMPT SMP KASAN PTI
[   25.066914] KASAN: null-ptr-deref in range [0x0000000000000c10-0x0000000000000c17]
[   25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0
[   25.077709] Call Trace:
[   25.077924]  <TASK>
[   25.078108]  unregister_hdlc_device+0x16/0x30
[   25.078481]  slgt_cleanup+0x157/0x9f0 [synclink_gt]

Fix this by checking whether the 'info->netdev' is a null pointer first.

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


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

	Fixed in 4.9.318 with commit 50c341f9a2adc4c32a8ad5a39eb99d9c4a419e0d
	Fixed in 4.14.283 with commit 078212ad15dbd88840c82c97f12c93d83703c8fd
	Fixed in 4.19.247 with commit ba08cbc5b53e151d0acf1930fb526fc65b7f3e65
	Fixed in 5.4.198 with commit f6e07eb7ebec53ffe81fc2489589320fbe4a6b75
	Fixed in 5.10.122 with commit d68d5e68b7f64de7170f8e04dd9b995c36b2c71c
	Fixed in 5.15.47 with commit 8a95696bdc0e13f8980f05b54a3b9081963d1256
	Fixed in 5.17.15 with commit ddd67751ab86c6a65f95c35293c42f85a42ac05d
	Fixed in 5.18.4 with commit 1ceb4ca9543a8a788febf6bc8dad2e605e172d5e
	Fixed in 5.19 with commit 689ca31c542687709ba21ec2195c1fbce34fd029

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-49307
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/tty/synclink_gt.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/50c341f9a2adc4c32a8ad5a39eb99d9c4a419e0d
	https://git.kernel.org/stable/c/078212ad15dbd88840c82c97f12c93d83703c8fd
	https://git.kernel.org/stable/c/ba08cbc5b53e151d0acf1930fb526fc65b7f3e65
	https://git.kernel.org/stable/c/f6e07eb7ebec53ffe81fc2489589320fbe4a6b75
	https://git.kernel.org/stable/c/d68d5e68b7f64de7170f8e04dd9b995c36b2c71c
	https://git.kernel.org/stable/c/8a95696bdc0e13f8980f05b54a3b9081963d1256
	https://git.kernel.org/stable/c/ddd67751ab86c6a65f95c35293c42f85a42ac05d
	https://git.kernel.org/stable/c/1ceb4ca9543a8a788febf6bc8dad2e605e172d5e
	https://git.kernel.org/stable/c/689ca31c542687709ba21ec2195c1fbce34fd029