LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22997: net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux CAN J1939 flaw can leak kernel session references when a second connection request arrives. The leak may prevent a CAN network device from being released, disrupting shutdown, reconfiguration, or recovery operations. The documented impact is availability loss, not data theft or modification.

Executive priority

Prioritize remediation for safety-sensitive, industrial, automotive, or embedded systems that actively use reachable J1939. Treat it as high operational risk where device reconfiguration or recovery is essential. Lower the immediate priority only after confirming J1939 is unused or isolated and documenting that evidence.

Technical view

When a second J1939 RTS is received for an active session, cancelling the receive timer can bypass session deactivation. The retained j1939_session reference later causes unregister_netdevice to wait indefinitely for the CAN device. The upstream resolution explicitly deactivates the session after timer cancellation.

Likely exposure

Exposure is concentrated in Linux systems using CAN J1939, particularly embedded, vehicle, and industrial environments where untrusted traffic can reach the J1939 interface. The supplied record lists affected kernels from 5.4 through 6.19, but provides no CPEs. Systems not using reachable J1939 functionality are less likely to be exposed.

Exploitation context

The CVSS 3.1 assessment is 7.5 with network reachability, low complexity, no privileges, and high availability impact. The record is not in KEV, and the supplied sources do not establish active exploitation or a public exploit. Practical reachability depends on CAN/J1939 topology and trust boundaries.

Researcher notes

The failure mechanism and upstream correction are clearly described. However, the supplied affected-version data mixes release numbers with duplicated commit identifiers, lacks CPEs, and does not identify distribution package versions. Validate exposure against vendor advisories and confirm which stable fix applies to each deployed kernel branch.

Mitigation direction

  • Install a vendor-supported kernel release incorporating the applicable upstream stable fix.
  • Consult the Linux distribution or device vendor for exact fixed package versions.
  • Restrict untrusted access to CAN and J1939 interfaces where operationally feasible.
  • Disable unused J1939 functionality after confirming safety and operational requirements.
  • Monitor affected systems for CAN device release or reconfiguration failures.

Validation and detection

  • Inventory kernel versions on systems using CAN J1939.
  • Confirm vendor packages include the applicable linked stable-kernel correction.
  • Verify whether untrusted sources can send traffic to J1939 interfaces.
  • Review logs for unregister_netdevice waits and persistent CAN device usage counts.
  • Regression-test CAN device shutdown and reconfiguration after updating.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-22997 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-22997Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9d71dd0c70099914fcd063135da3c580865e924c, 9d71dd0c70099914fcd063135da3c580865e924c, 9d71dd0c70099914fcd063135da3c580865e924c, 9d71dd0c70099914fcd063135da3c580865e924c, 9d71dd0c70099914fcd063135da3c580865e924c, 9d71dd0c70099914fcd063135da3c580865e924c, 9d71dd0c70099914fcd063135da3c580865e924cunaffected
LinuxLinux5.4, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.67, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.