CVE-2023-54094
Use-After-Free Vulnerability in Linux Kernel Network skb Segmentation
Publication date: 2025-12-24
Last updated on: 2025-12-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.4.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves skb (socket buffer) corruption during frag list segmentation. Specifically, when rx-gro-list GRO-ed packets are processed via a network bridge to both local input and an egress device, the segmentation operation unsafely writes to cloned skbs that share heads, leading to skb corruption and kernel crashes such as NULL pointer dereferences. The fix involves uncloning the skbs as needed before segmentation to prevent this unsafe write.
How can this vulnerability impact me? :
This vulnerability can cause kernel crashes due to skb corruption, resulting in system instability or denial of service. It may disrupt network packet processing, potentially affecting network performance and reliability on affected Linux systems.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for specific oops messages related to skb corruption and NULL pointer dereferences. Look for kernel log entries similar to: '[ 62.624003] BUG: kernel NULL pointer dereference, address: 00000000000000c0' and call traces involving __udp_gso_segment and related network functions. You can use the command 'dmesg | grep -i "BUG: kernel NULL pointer dereference"' or 'journalctl -k | grep -i "BUG: kernel NULL pointer dereference"' to find such messages.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by changes that uncloned to-be-segmented skbs. Until an update is applied, consider disabling GRO (Generic Receive Offload) or bridging features that may trigger the vulnerability to reduce risk.