Skip to main content
VulnerabilityPublished Updated

CVE-2026-46102: Linux kernel · net: strparser: fix skb_head leak in strp_abort_strp()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in fe72340daaf1af588be88056faf98965f39e6032 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in fe72340daaf1af588be88056faf98965f39e6032, e9ae00490d474757c0f9c65073de83e6bb1e5a00, d6668ce0e78d23eabecef9a6bc4f0f739cb28ad3 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 43a0c6751a322847cb6fa0ab8cbf77a1d08bfc0a, < fe72340daaf1af588be88056faf98965f39e6032
Fixed in
  • fe72340daaf1af588be88056faf98965f39e6032
LinuxLinuxAffected
  • ≥ 43a0c6751a322847cb6fa0ab8cbf77a1d08bfc0a, < e9ae00490d474757c0f9c65073de83e6bb1e5a00
Fixed in
  • e9ae00490d474757c0f9c65073de83e6bb1e5a00
LinuxLinuxAffected
  • ≥ 43a0c6751a322847cb6fa0ab8cbf77a1d08bfc0a, < d6668ce0e78d23eabecef9a6bc4f0f739cb28ad3
Fixed in
  • d6668ce0e78d23eabecef9a6bc4f0f739cb28ad3
LinuxLinuxAffected
  • ≥ 43a0c6751a322847cb6fa0ab8cbf77a1d08bfc0a, < c2e57695ec9ff9d42f23de70f3805199153d007b
Fixed in
  • c2e57695ec9ff9d42f23de70f3805199153d007b
LinuxLinuxAffected
  • ≥ 43a0c6751a322847cb6fa0ab8cbf77a1d08bfc0a, < a470ed71c906cc8cbad0d74c9942216698911f8b
Fixed in
  • a470ed71c906cc8cbad0d74c9942216698911f8b
LinuxLinuxAffected
  • ≥ 43a0c6751a322847cb6fa0ab8cbf77a1d08bfc0a, < 56082f442023db9be1a5a29d4ee361de4017c0b7
Fixed in
  • 56082f442023db9be1a5a29d4ee361de4017c0b7

Description

In the Linux kernel, the following vulnerability has been resolved: net: strparser: fix skb_head leak in strp_abort_strp() When the stream parser is aborted, for example after a message assembly timeout, it can still hold a reference to a partially assembled message in strp->skb_head. That skb is not released in strp_abort_strp(), which leaks the partially assembled message and can be triggered repeatedly to exhaust memory. Fix this by freeing strp->skb_head and resetting the parser state in the abort path. Leave strp_stop() unchanged so final cleanup still happens in strp_done() after the work and timer have been synchronized.

References

Community reviews

Loading reviews…