Kernel memory corruption via split ROSE refcounts
Published Sep 16, 2025 · Updated Sep 16, 2025
Use-after-free in Linux kernel ROSE networking allows remote attackers to corrupt kernel memory through crafted ROSE frames from AX.25 peers. rose_node entries retain rose_neigh pointers without holding the same use refcount as sockets, so route or device teardown frees a neighbor while routes, nodes, or sockets still reference it. Reachability requires link-adjacent ROSE routing over radio, serial TNC, or local Ethernet; reuse can disclose or overwrite kernel memory and trigger an oops or panic.
Summary
What happened
Use-after-free in Linux kernel ROSE networking allows remote attackers to corrupt kernel memory through crafted ROSE frames from AX.25 peers. rose_node entries retain rose_neigh pointers without holding the same use refcount as sockets, so route or device teardown frees a neighbor while routes, nodes, or sockets still reference it. Reachability requires link-adjacent ROSE routing over radio, serial TNC, or local Ethernet; reuse can disclose or overwrite kernel memory and trigger an oops or panic.
The record
- CVE
- CVE-2025-39827
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <384210cceb1873a4c8218b27ba0745444436b728
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4cce478c3e82a5fc788d72adb2f4c4e983997639
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9c547c8eee9d1cf6e744611d688b9f725cf9a115
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d7563b456ed44151e1a82091d96f60166daea89b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <da9c9c877597170b929a6121a68dcd3dd9a80f45
- Affected versionversion=2.6.12
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