CVE-2024-38602: ax25: Fix reference count leak issues of ax25_dev
In the Linux kernel, the following vulnerability has been resolved:
ax25: Fix reference count leak issues of ax25_dev
The ax25_addr_ax25dev() and ax25_dev_device_down() exist a reference
count leak issue of the object "ax25_dev".
Memory leak issue in ax25_addr_ax25dev():
The reference count of the object "ax25_dev" can be increased multiple
times in ax25_addr_ax25dev(). This will cause a memory leak.
Memory leak issues in ax25_dev_device_down():
The reference count of ax25_dev is set to 1 in ax25_dev_device_up() and
then increase the reference count when ax25_dev is added to ax25_dev_list.
As a result, the reference count of ax25_dev is 2. But when the device is
shutting down. The ax25_dev_device_down() drops the reference count once
or twice depending on if we goto unlock_put or not, which will cause
memory leak.
As for the issue of ax25_addr_ax25dev(), it is impossible for one pointer
to be on a list twice. So add a break in ax25_addr_ax25dev(). As for the
issue of ax25_dev_device_down(), increase the reference count of ax25_dev
once in ax25_dev_device_up() and decrease the reference count of ax25_dev
after it is removed from the ax25_dev_list.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the AX.25 networking subsystem. On affected systems, repeated reference-count handling can leave AX.25 device objects unreleased, potentially causing gradual resource exhaustion or instability. The sources do not provide a CVSS score or evidence of active exploitation.
Executive priority
Treat as a patch-management item unless AX.25 is used in a sensitive or availability-critical environment. Current evidence does not justify emergency response, but kernel memory leaks can create operational reliability risk.
Technical view
The flaw is in ax25_addr_ax25dev() and ax25_dev_device_down(), where ax25_dev reference counts can be incremented or decremented incorrectly. The kernel fix adds a break in lookup handling and balances references when AX.25 devices are added to and removed from ax25_dev_list.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds where AX.25 networking code is present and reachable. The source bundle names Linux as affected but does not give deployment prevalence, attack prerequisites, or distribution-specific package status.
Exploitation context
The provided sources describe a reference-count leak and memory leak condition, not a confirmed exploit path. CISA KEV is false in the bundle, and no cited source reports active exploitation.
Researcher notes
The root issue is reference lifetime imbalance for ax25_dev objects. Evidence supports memory leak impact only; the bundle lacks CVSS, CWE, exploitability details, privileges required, and distribution-level fixed package data.
Mitigation direction
Check vendor kernel advisories for CVE-2024-38602 and applicable fixed packages.
Update affected Linux kernels to versions containing the referenced stable fixes.
Confirm distribution backports rather than relying only on upstream version numbers.
If AX.25 is unnecessary, check vendor guidance on disabling or avoiding it.
Validation and detection
Inventory Linux kernel versions on systems that may expose AX.25 functionality.
Compare installed kernels against vendor advisories and the CVE record.
Verify package changelogs or source metadata include the referenced fix commits.
Monitor affected systems for abnormal memory growth until patched.
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-2024-38602 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.