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: <2025100134-CVE-2023-53524-d438@gregkh>
Date: Wed,  1 Oct 2025 13:46:16 +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-53524: wifi: iwlwifi: pcie: Fix integer overflow in iwl_write_to_user_buf

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

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

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

wifi: iwlwifi: pcie: Fix integer overflow in iwl_write_to_user_buf

An integer overflow occurs in the iwl_write_to_user_buf() function,
which is called by the iwl_dbgfs_monitor_data_read() function.

static bool iwl_write_to_user_buf(char __user *user_buf, ssize_t count,
				  void *buf, ssize_t *size,
				  ssize_t *bytes_copied)
{
	int buf_size_left = count - *bytes_copied;

	buf_size_left = buf_size_left - (buf_size_left % sizeof(u32));
	if (*size > buf_size_left)
		*size = buf_size_left;

If the user passes a SIZE_MAX value to the "ssize_t count" parameter,
the ssize_t count parameter is assigned to "int buf_size_left".
Then compare "*size" with "buf_size_left" . Here, "buf_size_left" is a
negative number, so "*size" is assigned "buf_size_left" and goes into
the third argument of the copy_to_user function, causing a heap overflow.

This is not a security vulnerability because iwl_dbgfs_monitor_data_read()
is a debugfs operation with 0400 privileges.

The Linux kernel CVE team has assigned CVE-2023-53524 to this issue.


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

	Fixed in 5.4.244 with commit 0ad8dd870aa187d0c21d032bb2c6433559075eec
	Fixed in 5.10.181 with commit 059e426d666a41e26b184c177c1ca3ee2d6fa1b6
	Fixed in 5.15.113 with commit 82f877ec9b041edc4c7c509c605cc3393d837bf0
	Fixed in 6.1.30 with commit eb1ef44efac797b384d361a76e33f77027c29a14
	Fixed in 6.3.4 with commit de78456976026102babe66258c228691ca5677c0
	Fixed in 6.4 with commit 58d1b717879bfeabe09b35e41ad667c79933eb2e

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-53524
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/net/wireless/intel/iwlwifi/pcie/trans.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/0ad8dd870aa187d0c21d032bb2c6433559075eec
	https://git.kernel.org/stable/c/059e426d666a41e26b184c177c1ca3ee2d6fa1b6
	https://git.kernel.org/stable/c/82f877ec9b041edc4c7c509c605cc3393d837bf0
	https://git.kernel.org/stable/c/eb1ef44efac797b384d361a76e33f77027c29a14
	https://git.kernel.org/stable/c/de78456976026102babe66258c228691ca5677c0
	https://git.kernel.org/stable/c/58d1b717879bfeabe09b35e41ad667c79933eb2e

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ