Kernel memory corruption via pending TX cleanup tasklet
Published Sep 24, 2026 · Updated Sep 24, 2026
Use-after-free in Linux's Octeon Ethernet staging driver lets pending TX cleanup access freed network-device memory during teardown. The watchdog IRQ can queue cvm_oct_tx_do_cleanup after cvm_oct_remove frees entries referenced through cvm_oct_device because shutdown does not kill the tasklet. Reachability requires the Octeon driver and device teardown while cleanup remains pending; public sources establish no attacker-controlled trigger or consequence beyond the invalid access.
Summary
What happened
Use-after-free in Linux's Octeon Ethernet staging driver lets pending TX cleanup access freed network-device memory during teardown. The watchdog IRQ can queue cvm_oct_tx_do_cleanup after cvm_oct_remove frees entries referenced through cvm_oct_device because shutdown does not kill the tasklet. Reachability requires the Octeon driver and device teardown while cleanup remains pending; public sources establish no attacker-controlled trigger or consequence beyond the invalid access.
The record
- CVE
- CVE-2026-93279
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=2.6.34
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <03d12490afd1198310ad0aba42462329832eb739
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <2c0c9956596e48654bb4855e2a0742748a0826a7
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <32efcb6d5f4e3f030e7b0a3ba5c6c0684dd07486
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <41a79bd9e5a74f8f483b3b206d10567912874fb4
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <a77efd85e0d48c877f66d2bc3ab89cc1b8dacd19
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <b6365e4186322858a82c8713b1d0bd209c8e765a
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <b9af44b0d20b2247c4eb0ea5cfca907d643eea50
- Affected versionversion=4898c560103fb8075c10a8e9d70e0ca26873075e <d15226338dfaa84ffff142d32723cdf74d0c47c4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started