Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in AX.25 networking reference tracking. The public record shows it was fixed in stable kernel commits, but does not describe a proven attacker impact, CVSS score, or active exploitation.
Executive priority
Track and remediate through normal kernel patch management unless AX.25 is enabled in sensitive or multi-user environments. Business urgency is unclear because public impact evidence is incomplete.
Technical view
The issue concerns incorrect dev_tracker usage in the Linux kernel AX.25 implementation. An ax25_dev may be shared by multiple ax25_cb structures, requiring separate tracking per control block. The report includes ref_tracker warnings after bind and release paths.
Likely exposure
Exposure is most likely on Linux systems that enable or load AX.25 amateur packet radio networking support and run affected kernel ranges before the referenced stable fixes.
Exploitation context
The provided sources do not show KEV listing, active exploitation, public exploit details, or a clear privilege boundary impact. Treat exploitability as unproven from this bundle.
Researcher notes
The evidence points to a kernel reference-tracking correctness fix, not a fully characterized vulnerability class. Avoid assuming memory corruption, privilege escalation, or denial of service without additional vendor analysis.
Mitigation direction
Update to a vendor kernel containing the referenced stable AX.25 fixes.
If AX.25 is unnecessary, disable or avoid loading AX.25 support.
Check Linux distribution advisories for backported fixes matching your kernel package.
Prioritize externally reachable or multi-user Linux systems with AX.25 enabled.
Validation and detection
Inventory Linux kernel versions across servers, workstations, appliances, and embedded systems.
Identify whether AX.25 support is built in, loadable, or currently loaded.
Compare installed kernels against vendor advisories and the referenced stable commits.
Review kernel logs for AX.25 ref_tracker warnings if debug tracking is enabled.
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-2022-50163 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.