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-97952sunvdc: unmap LDC cookies when the descriptor send fails

Description

In the Linux kernel, the following vulnerability has been resolved: sunvdc: unmap LDC cookies when the descriptor send fails __send_request() maps the request's pages into the LDC channel's map table (ldc_map_sg()), fills in the descriptor and marks it VIO_DESC_READY before ringing the doorbell via __vdc_tx_trigger(). When the trigger fails, the error path only prints a message: the descriptor stays READY and the cookies are never unmapped. The mapping is normally released in vdc_end_one() when the peer completes the descriptor - but a descriptor whose doorbell was never sent will never complete, and since dr->prod is not advanced on failure, the reset path (vdc_requeue_inflight(), which walks [cons, prod)) never visits it either. The map table entries are leaked permanently. Since commit a11f6ca9aef9 ("sunvdc: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN") trigger failures occur in practice under load, so every resulting I/O error also leaks one request's worth of entries from the fixed-size (8192 entries per channel) map table. Because the allocator hands out contiguous ranges, fragmentation makes large multi-segment requests fail first as the table drains, until ldc_map_sg() fails permanently and the disk is dead until reboot. It also makes any retry-based recovery unusable: requeuing the request on -EAGAIN remaps the pages on every attempt, overwriting desc->cookies and orphaning the previous mapping, so the table drains at the retry rate. This is the memory exhaustion observed when the requeue approach was first tested in October 2025. Roll back on failure: unmap the cookies, mark the descriptor FREE again and clear the request entry. If the trigger failed with -ENOTCONN, __vdc_tx_trigger() has already reset the port, which tears down and reallocates both the dring and the LDC channel including its map table - nothing to roll back, and the stale descriptor must not be touched.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < eb9c5f6747fe98b83c78cb5476a914e91d50e8e8
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < 24564576be423f3b5d7e67cd7df848ac66646497
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < 9251573e7cf7d797ae4a30b2a236af8242237a61
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < b0de6463667e9bb9dc14a83a9c24c1b6b3f7b5f7
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < ab81a5c1014a38dab0fb402609fd866b0bcb4726
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < 57835952566f0be9b365a6eb3a70b397a9d5ef47
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < f3322baa3a8ac87730feae952c1146269d78e098
    • affected a11f6ca9aef989b56cd31ff4ee2af4fb31a172ec – < 0c6da21fa35e03fc74f09895433ccd6d4a9c3530
    • affected 627e656239c63d8a81672d08de7885e89c12fa75
    • affected a1ef7d5da9b2c145f811a80bb8197df6037a7572
    • affected 7ab4b6526fdcdfa7772984bbcd2ac4fd14fa223b
    • affected 3fbba4e55051d01a72b56ea192064175924bf56a
    • affected 3e380fc2ae4d18210eec9c472b12e2b2544f7dc1
    • affected 4.4.175 – < 4.5
    • affected 4.9.156 – < 4.10
    • affected 4.14.99 – < 4.15
    • affected 4.19.21 – < 4.20
    • affected 4.20.8 – < 4.21
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 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-97952 badge
[![CVE-2026-97952](https://cveledger.app/badge/CVE-2026-97952.svg)](https://cveledger.app/cve/CVE-2026-97952)

Record last updated .