CVE-2026-68327: wan: wanxl: Only reset hardware after BAR mapping
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 2fe22d58b3797d741570f9873b26653fd511576c, 3d9617d856ebddcdddbab0ce877c397420f59f55, 59cbe6cfa0fa23c192351cc284e30707309f6741; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2fe22d58b3797d741570f9873b26653fd511576c, 3d9617d856ebddcdddbab0ce877c397420f59f55, 59cbe6cfa0fa23c192351cc284e30707309f6741; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ef394eeb9d5ec6db8d979eec6d27f56c2ebc6523affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3d9617d856ebddcdddbab0ce877c397420f59f55affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 897e289db1e4d00ca6419cfe733c646492147270affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f4834132773f15ffb255127499c8443947fa7d0faffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b9e2ff70e96acf83693b27987e0390bad9f83efaaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 59cbe6cfa0fa23c192351cc284e30707309f6741affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2fe22d58b3797d741570f9873b26653fd511576caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 91957b89da995607cb654b1f9a3c126ddbaee10faffected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68324Aug 10, 2026 · iommu/intel: Fix out-of-bounds memset in dmar_latency_disable()0Monitor
- ← EarlierCVE-2026-68325Aug 10, 2026 · iommu/amd: Bound the early ACPI HID map0Monitor
- Later →CVE-2026-68328Aug 10, 2026 · nfp: Check resource mutex allocation0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2fe22d58b3797d741570f9873b26653fd511576c | Vendor (CNA) |
| Linux Linux | 3d9617d856ebddcdddbab0ce877c397420f59f55 | Vendor (CNA) |
| Linux Linux | 59cbe6cfa0fa23c192351cc284e30707309f6741 | Vendor (CNA) |
| Linux Linux | 897e289db1e4d00ca6419cfe733c646492147270 | Vendor (CNA) |
| Linux Linux | 91957b89da995607cb654b1f9a3c126ddbaee10f | Vendor (CNA) |
| Linux Linux | b9e2ff70e96acf83693b27987e0390bad9f83efa | Vendor (CNA) |
| Linux Linux | ef394eeb9d5ec6db8d979eec6d27f56c2ebc6523 | Vendor (CNA) |
| Linux Linux | f4834132773f15ffb255127499c8443947fa7d0f | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3d9617d856ebddcdddbab0ce877c397420f59f55
- git.kernel.org/stable/c/59cbe6cfa0fa23c192351cc284e30707309f6741
- git.kernel.org/stable/c/897e289db1e4d00ca6419cfe733c646492147270
- git.kernel.org/stable/c/91957b89da995607cb654b1f9a3c126ddbaee10f
- git.kernel.org/stable/c/b9e2ff70e96acf83693b27987e0390bad9f83efa
- git.kernel.org/stable/c/ef394eeb9d5ec6db8d979eec6d27f56c2ebc6523
- git.kernel.org/stable/c/f4834132773f15ffb255127499c8443947fa7d0f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.