[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026012533-CVE-2026-22997-42ca@gregkh>
Date: Sun, 25 Jan 2026 15:36:33 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-22997: net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts
Since j1939_session_deactivate_activate_next() in j1939_tp_rxtimer() is
called only when the timer is enabled, we need to call
j1939_session_deactivate_activate_next() if we cancelled the timer.
Otherwise, refcount for j1939_session leaks, which will later appear as
| unregister_netdevice: waiting for vcan0 to become free. Usage count = 2.
problem.
The Linux kernel CVE team has assigned CVE-2026-22997 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.12.67 with commit cb2a610867bc379988bae0bb4b8bbc59c0decf1a
Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.18.7 with commit 6121b7564c725b632ffe4764abe85aa239d37703
Issue introduced in 5.4 with commit 9d71dd0c70099914fcd063135da3c580865e924c and fixed in 6.19-rc6 with commit 1809c82aa073a11b7d335ae932d81ce51a588a4a
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-2026-22997
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:
net/can/j1939/transport.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/cb2a610867bc379988bae0bb4b8bbc59c0decf1a
https://git.kernel.org/stable/c/6121b7564c725b632ffe4764abe85aa239d37703
https://git.kernel.org/stable/c/1809c82aa073a11b7d335ae932d81ce51a588a4a
Powered by blists - more mailing lists