CVE-2026-99056

strparser: make sure __strp_recv isn't running before tearing down the parser

  • High 7.8

Description

In the Linux kernel, the following vulnerability has been resolved: strparser: make sure __strp_recv isn't running before tearing down the parser The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done(). This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed. Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug. This could crash on strp->sk ("general mode" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it. Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause(). A reproducer has been published and turns the possible UAF into an exploit [1].

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.164% likely to be exploited in the next 30 days, higher than 5.64% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.8CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding b09071e2f8460b35c7d355addad0fc7b31c6904d (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding 933df60a465b1b82ff92dcd6870504da90ba4e9b (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding 61cc5dac60d50dee06cf5c7b7ab246f9c825a715 (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding a18dd388045dc7263d99a07db9de4e0f149ca8f1 (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding 9f3e9fe1b155e9b4572054d8d140586bc3512ecf (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding d2b5f637b9b67a79a50d42614d10653c13b4e449 (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding eaa3a29004c063d7e9d5ea55636f693f67e6db0f (affected)
  • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 up to but excluding 0984ebc631792acf8fff105112ee74a6b8f1efcc (affected)
LinuxLinux
  • Default status: affected
  • 5.6 (affected)
  • 0 up to but excluding 5.6 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References