Kernel oops via post-failure RxRPC buffer trace
Published May 27, 2026 · Updated May 27, 2026
Use-after-free in the Linux Kernel RxRPC receive path allows local users to trigger a kernel oops while DATA packets are processed. When skb_unshare() fails in rxrpc_input_packet(), it frees the socket buffer and clears the parent pointer before rxrpc_io_thread() passes that pointer to trace_rxrpc_rx_done(). Reachability requires a packet-unsharing allocation failure; the published direct consequence is an oops rather than an independently demonstrated kernel-wide crash.
Summary
What happened
Use-after-free in the Linux Kernel RxRPC receive path allows local users to trigger a kernel oops while DATA packets are processed. When skb_unshare() fails in rxrpc_input_packet(), it frees the socket buffer and clears the parent pointer before rxrpc_io_thread() passes that pointer to trace_rxrpc_rx_done(). Reachability requires a packet-unsharing allocation failure; the published direct consequence is an oops rather than an independently demonstrated kernel-wide crash.
The record
- CVE
- CVE-2026-45998
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-825, CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <1f2740150f904bfa60e4bad74d65add3ccb5e7f8
- Affected versionversion=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <8fde6296c4d4da2be7ab761305ab7f232b94eefd
- Affected versionversion=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <996b0487b3cdda4c91811dbb1c9564626bc840bd
- Affected versionversion=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <bf20f46d94f1db38e6ffc0ca204a5fe0de01b495
- Affected versionversion=2d1faf7a0ca3c0b327cf064c80e4e775532c9319 <e3bf143b1e98fb3d6d9e6825bcd683974d478e8c
- Affected versionversion=6.2
What conditions does exploitation require?
What is affected?
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