# wifi: rt2x00: avoid full teardown before work setup in probe

CVE record · `CVE-2026-72005`

- **Identifiers:** `CVE-2026-72005`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-404](https://cwe.mitre.org/data/definitions/404.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 15 Aug 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 15 Aug 2026, 05:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 8b58d1f1356df6a7d2de3f55bb665b18b04ffda0` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 59afe6148927395cf86f9429900e029a48b1d42b` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 3c0427d719bddb33caf18ff4ffb77cb47de7eb00` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before eb7474d0253bb2de4793e1d3ce833e8564bbe732` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 66bd9b1a72de7c2f5141b02d796048aafaed8a49` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 816559409e340acaa5c9d868291dab30d8c80263` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 56994852d704535ea354a4627ca667b1b4fa0deb` (git)
  - affected: `0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 to before 536fb3d739d75a03cb318c0c6fe799425cfea501` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.39`
  - unaffected: `before 2.6.39` (semver)
  - unaffected: `5.10.261 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.212 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.178 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.145 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.97 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.40 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.5 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 15 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-72005](https://www.cve.org/CVERecord?id=CVE-2026-72005)
- [NVD: CVE-2026-72005](https://nvd.nist.gov/vuln/detail/CVE-2026-72005)

### References from the CNA

- <https://git.kernel.org/stable/c/8b58d1f1356df6a7d2de3f55bb665b18b04ffda0>
- <https://git.kernel.org/stable/c/59afe6148927395cf86f9429900e029a48b1d42b>
- <https://git.kernel.org/stable/c/3c0427d719bddb33caf18ff4ffb77cb47de7eb00>
- <https://git.kernel.org/stable/c/eb7474d0253bb2de4793e1d3ce833e8564bbe732>
- <https://git.kernel.org/stable/c/66bd9b1a72de7c2f5141b02d796048aafaed8a49>
- <https://git.kernel.org/stable/c/816559409e340acaa5c9d868291dab30d8c80263>
- <https://git.kernel.org/stable/c/56994852d704535ea354a4627ca667b1b4fa0deb>
- <https://git.kernel.org/stable/c/536fb3d739d75a03cb318c0c6fe799425cfea501>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-72005>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-72005/>. Everything for agents: <https://agentprime.io/llms.txt>.
