In the Linux kernel, the following vulnerability has been resolved:
net: atm: fix /proc/net/atm/lec handling
/proc/net/atm/lec must ensure safety against dev_lec[] changes.
It appears it had dev_put() calls without prior dev_hold(),
leading to imbalance and UAF.
Security readout for executives and security teams
Plain-English summary
CVE-2025-38180 is a Linux kernel use-after-free flaw in ATM LAN Emulation handling. A low-privileged local user may be able to trigger serious memory corruption without user interaction. The CVSS assessment indicates possible loss of confidentiality, integrity, and availability, but the supplied sources do not confirm real-world exploitation.
Executive priority
Treat this as a high-priority kernel update for exposed shared, multi-user, or locally accessible systems. Other systems should enter the normal accelerated kernel-patching cycle after confirming applicability. Urgency reflects potential full-system impact after local access, not evidence of widespread remote attacks.
Technical view
The /proc/net/atm/lec handler is unsafe when dev_lec[] changes. It contains dev_put() calls without corresponding dev_hold() references, creating a reference-count imbalance and possible use-after-free. The flaw requires local access with low privileges and has a CVSS 3.1 score of 7.8.
Likely exposure
Exposure is most relevant to Linux systems where the affected ATM LEC proc interface is available to local users. The supplied affected-version data is ambiguous and includes multiple kernel branches, so vulnerability managers should map exact kernel packages to the applicable stable fix or distribution advisory.
Exploitation context
The CVSS vector indicates local, low-privileged exploitation with low complexity and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. This does not establish that exploitation is impossible or absent.
Researcher notes
The central condition is unsafe lifetime management around dev_lec[] and /proc/net/atm/lec, producing an apparent use-after-free through unbalanced device references. No CWE is supplied. Stable commits exist across several kernel branches, but the bundle does not provide sufficiently clear branch ranges or demonstrate exploitability beyond the CVSS assessment.
Mitigation direction
Inventory Linux kernel builds and map each to the applicable stable fix or distribution advisory.
Update affected systems to a vendor-supported kernel containing the relevant upstream stable correction.
Prioritize shared or multi-user hosts where low-privileged local users can reach the affected ATM LEC path.
If patching is delayed, restrict untrusted local access and follow vendor-approved guidance for reducing ATM LEC exposure.
Validation and detection
Record each system's running kernel version and distribution package release.
Determine whether /proc/net/atm/lec is present and accessible on representative systems.
Confirm the installed package includes the applicable Linux stable commit or distribution backport.
After updating, verify the patched kernel is running and repeat exposure checks.
Monitor vendor advisories because the supplied version boundaries are not sufficiently clear for package-level decisions.
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-2025-38180 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.
1CVSS vectors
3Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.