Kernel memory corruption via stale receive-buffer pointer
Published Oct 6, 2026 · Updated Oct 6, 2026
Use-after-free in the lan743x Ethernet driver in Linux 6.1 allows remote attackers to corrupt kernel memory via a received packet. After a multi-buffer packet is linearized, lan743x_rx_process_buffer() writes ip_summed through a pointer to freed fragment metadata instead of the surviving head buffer. The path requires LAN743x receive checksum offload and a packet spanning buffers, which can follow a live MTU increase; testing confirmed a one-byte write, but physical hardware was not tested.
Summary
What happened
Use-after-free in the lan743x Ethernet driver in Linux 6.1 allows remote attackers to corrupt kernel memory via a received packet. After a multi-buffer packet is linearized, lan743x_rx_process_buffer() writes ip_summed through a pointer to freed fragment metadata instead of the surviving head buffer. The path requires LAN743x receive checksum offload and a packet spanning buffers, which can follow a live MTU increase; testing confirmed a one-byte write, but physical hardware was not tested.
The record
- CVE
- CVE-2026-98239
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 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=6.1
- Affected versionversion=cd6910501cfd9a3bdff2f5fc33c9f3cf165ca54a <0e52886c4324c9897c2c62f92be3dc8316cee67e
- Affected versionversion=cd6910501cfd9a3bdff2f5fc33c9f3cf165ca54a <161a403c8625e152de03d1da22bbf9cda6dc9f9f
- Affected versionversion=cd6910501cfd9a3bdff2f5fc33c9f3cf165ca54a <5c216bfa9fb7b36804485e67975e9c98055b31ef
- Affected versionversion=cd6910501cfd9a3bdff2f5fc33c9f3cf165ca54a <6fe5c3a2503983abb431d93faeadfc7f5e6a7e33
- Affected versionversion=cd6910501cfd9a3bdff2f5fc33c9f3cf165ca54a <a58024835c704419bb46d2a34e5223f65605f958
- Affected versionversion=cd6910501cfd9a3bdff2f5fc33c9f3cf165ca54a <a9ce4053dc945c5372dedba5017ee675b30dc0c5
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