CVE-2026-31518: esp: fix skb leak with espintcp and async crypto
Published Apr 22, 2026
·Updated
esp: fix skb leak with espintcp and async crypto
Affected Software
16 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.6<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
Microsoft azl3 kernel 6.6.130.1-3
Event History
Apr 22, 2026
CVE Published
via MITRE·01:54 PM
Data Sourced
via MITRE·01:54 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:06 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:06 AM
Affected Software
Updated
via Microsoft·08:06 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-31518?
CVE-2026-31518 is classified as a medium severity vulnerability.
2
How do I fix CVE-2026-31518?
To fix CVE-2026-31518, update your Linux kernel to a version that includes the patch for this vulnerability.
3
What is the impact of CVE-2026-31518 on the Linux kernel?
CVE-2026-31518 can lead to a resource leak in the espintcp module, causing degraded system performance.
4
Which Linux kernel versions are affected by CVE-2026-31518?
CVE-2026-31518 affects multiple versions of the Linux kernel that utilize espintcp with asynchronous crypto.
5
How does CVE-2026-31518 affect networking functionality?
CVE-2026-31518 can cause the transmission queue to become full, leading to errors without freeing network buffers.