CVE-2026-68327wan: wanxl: Only reset hardware after BAR mapping
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 9 days later
· 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)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ef394eeb9d5ec6db8d979eec6d27f56c2ebc6523
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3d9617d856ebddcdddbab0ce877c397420f59f55
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 897e289db1e4d00ca6419cfe733c646492147270
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f4834132773f15ffb255127499c8443947fa7d0f
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b9e2ff70e96acf83693b27987e0390bad9f83efa
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 59cbe6cfa0fa23c192351cc284e30707309f6741
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2fe22d58b3797d741570f9873b26653fd511576c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 91957b89da995607cb654b1f9a3c126ddbaee10f
- 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
- https://git.kernel.org/stable/c/ef394eeb9d5ec6db8d979eec6d27f56c2ebc6523 (opens in a new tab)
- https://git.kernel.org/stable/c/3d9617d856ebddcdddbab0ce877c397420f59f55 (opens in a new tab)
- https://git.kernel.org/stable/c/897e289db1e4d00ca6419cfe733c646492147270 (opens in a new tab)
- https://git.kernel.org/stable/c/f4834132773f15ffb255127499c8443947fa7d0f (opens in a new tab)
- https://git.kernel.org/stable/c/b9e2ff70e96acf83693b27987e0390bad9f83efa (opens in a new tab)
- https://git.kernel.org/stable/c/59cbe6cfa0fa23c192351cc284e30707309f6741 (opens in a new tab)
- https://git.kernel.org/stable/c/2fe22d58b3797d741570f9873b26653fd511576c (opens in a new tab)
- https://git.kernel.org/stable/c/91957b89da995607cb654b1f9a3c126ddbaee10f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55428 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68327)Record last updated .