Kernel memory exhaustion via AX.25 device shutdown
Published Jun 19, 2024 · Updated May 23, 2026
Memory leak in the Linux kernel AX.25 subsystem allows local users to exhaust kernel memory by repeatedly shutting down AX.25 devices. The ax25_dev_device_down() path releases the net_device reference only on one branch, leaving a reference held when dev->ax25_ptr is cleared. Reaching the flaw requires local low-privileged access and an AX.25 device shutdown; repeated shutdowns can consume kernel memory and interrupt service.
Summary
What happened
Memory leak in the Linux kernel AX.25 subsystem allows local users to exhaust kernel memory by repeatedly shutting down AX.25 devices. The ax25_dev_device_down() path releases the net_device reference only on one branch, leaving a reference held when dev->ax25_ptr is cleared. Reaching the flaw requires local low-privileged access and an AX.25 device shutdown; repeated shutdowns can consume kernel memory and interrupt service.
The record
- CVE
- CVE-2024-38554
- Published
- Jun 19, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.14.277 <4.15
- Affected versionversion=418993bbaafb0cd48f904ba68eeda052d624c821
- Affected versionversion=4.19.240 <4.20
- Affected versionversion=5.10.112 <5.11
- Affected versionversion=5.15.35 <5.16
- Affected versionversion=5.17
- Affected versionversion=5.4.190 <5.5
- Affected versionversion=5ea00fc60676c0eebfa8560ec461209d638bca9d
- Affected versionversion=9af0fd5c4453a44c692be0cbb3724859b75d739b
- Affected versionversion=d01ffb9eee4af165d83b08dd73ebdf9fe94a519b <36e56b1b002bb26440403053f19f9e1a8bc075b2
- Affected versionversion=d01ffb9eee4af165d83b08dd73ebdf9fe94a519b <3ec437f9bbae68e9b38115c4c91de995f73f6bad
- Affected versionversion=d01ffb9eee4af165d83b08dd73ebdf9fe94a519b <8bad3a20a27be8d935f2aae08d3c6e743754944a
- Affected versionversion=d01ffb9eee4af165d83b08dd73ebdf9fe94a519b <965d940fb7414b310a22666503d2af69459c981b
- Affected versionversion=d01ffb9eee4af165d83b08dd73ebdf9fe94a519b <eef95df9b752699bddecefa851f64858247246e9
- Affected versionversion=e2b558fe507a1ed4c43db2b0057fc6e41f20a14c
- Affected versionversion=ef0a2a0565727a48f2e36a2c461f8b1e3a61922d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo