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-68327wan: wanxl: Only reset hardware after BAR mapping

Description

In the Linux kernel, the following vulnerability has been resolved: wan: wanxl: Only reset hardware after BAR mapping wanxl_pci_init_one() stores the freshly allocated card in driver data before the PLX BAR is mapped. Several early probe failures then unwind through wanxl_pci_remove_one(), including failure to allocate the coherent status area or to restore the DMA mask. wanxl_pci_remove_one() unconditionally calls wanxl_reset(), and wanxl_reset() dereferences card->plx. On those early failures card->plx is still NULL, so the error path can dereference a NULL MMIO pointer. Only issue the hardware reset once the BAR mapping exists. The remaining cleanup in wanxl_pci_remove_one() already checks whether later resources were allocated. This issue was found by a static analysis checker and confirmed by manual source review.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 9 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 (16 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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ef394eeb9d5ec6db8d979eec6d27f56c2ebc6523
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3d9617d856ebddcdddbab0ce877c397420f59f55
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 897e289db1e4d00ca6419cfe733c646492147270
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f4834132773f15ffb255127499c8443947fa7d0f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b9e2ff70e96acf83693b27987e0390bad9f83efa
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 59cbe6cfa0fa23c192351cc284e30707309f6741
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2fe22d58b3797d741570f9873b26653fd511576c
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 91957b89da995607cb654b1f9a3c126ddbaee10f
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .