[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110555-CVE-2024-50113-fc8e@gregkh>
Date: Tue, 5 Nov 2024 18:11:02 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50113: firewire: core: fix invalid port index for parent device
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
firewire: core: fix invalid port index for parent device
In a commit 24b7f8e5cd65 ("firewire: core: use helper functions for self
ID sequence"), the enumeration over self ID sequence was refactored with
some helper functions with KUnit tests. These helper functions are
guaranteed to work expectedly by the KUnit tests, however their application
includes a mistake to assign invalid value to the index of port connected
to parent device.
This bug affects the case that any extra node devices which has three or
more ports are connected to 1394 OHCI controller. In the case, the path
to update the tree cache could hits WARN_ON(), and gets general protection
fault due to the access to invalid address computed by the invalid value.
This commit fixes the bug to assign correct port index.
The Linux kernel CVE team has assigned CVE-2024-50113 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 24b7f8e5cd65 and fixed in 6.11.6 with commit 90753a38bc3d
Issue introduced in 6.11 with commit 24b7f8e5cd65 and fixed in 6.12-rc5 with commit f6a6780e0b9b
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-2024-50113
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/firewire/core-topology.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/90753a38bc3d058820981f812a908a99f7b337c1
https://git.kernel.org/stable/c/f6a6780e0b9bbcf311a727afed06fee533a5e957
Powered by blists - more mailing lists