CVE-2026-23445
Use-After-Free in Linux igc Driver Causes Kernel Page Fault
Publication date: 2026-04-03
Last updated on: 2026-04-27
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.10 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.20 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.10 (exc) |
| linux | linux_kernel | From 6.10.1 (inc) to 6.12.78 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel splats related to the igc driver when an XDP application using TX timestamping is shutting down. Specifically, look for messages indicating a page fault in the igc_ptp_tx_tstamp_event or igc_tsync_interrupt functions.
- Check kernel logs for error messages similar to: "BUG: unable to handle page fault for address" followed by a call trace involving igc_ptp_tx_tstamp_event and igc_tsync_interrupt.
- Use the command: dmesg | grep -i 'igc_ptp_tx_tstamp_event' to filter relevant kernel messages.
- Alternatively, monitor system logs with: journalctl -k | grep -i 'igc_ptp_tx_tstamp_event'
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's igc driver related to handling TX timestamps in XDP (Express Data Path) applications.
When an XDP application that requested TX timestamping shuts down while the network interface link is still active, a kernel page fault occurs. This happens because during the shutdown of the TX ring, some xsk_meta pointers are not properly cleaned up, causing the IRQ handler to access invalid memory.
The issue leads to a kernel crash (kernel splat) due to the page fault. The vulnerability is fixed by cleaning up the stale xsk meta data on TX shutdown, ensuring that TX timestamps on other queues are not affected.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (kernel splat) when an XDP application using TX timestamping shuts down improperly while the network interface is still active.
Such a crash can lead to system instability, potential downtime, and disruption of network services relying on the affected interface.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the Linux kernel is updated to a version where the fix for cleaning up stale xsk meta data on TX shutdown is applied.
Until the kernel is updated, avoid shutting down XDP applications that request TX timestamping while the network interface link is still up, as this triggers the kernel splat.