Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99056strparser: make sure __strp_recv isn't running before tearing down the parser

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].

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-99056, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < b09071e2f8460b35c7d355addad0fc7b31c6904d
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 933df60a465b1b82ff92dcd6870504da90ba4e9b
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 61cc5dac60d50dee06cf5c7b7ab246f9c825a715
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < a18dd388045dc7263d99a07db9de4e0f149ca8f1
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 9f3e9fe1b155e9b4572054d8d140586bc3512ecf
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < d2b5f637b9b67a79a50d42614d10653c13b4e449
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < eaa3a29004c063d7e9d5ea55636f693f67e6db0f
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 0984ebc631792acf8fff105112ee74a6b8f1efcc
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99056 badge
[![CVE-2026-99056](https://cveledger.app/badge/CVE-2026-99056.svg)](https://cveledger.app/cve/CVE-2026-99056)

Record last updated .