# spi: spidev: fix lock inversion between spi_lock and buf_lock

CVE record · `CVE-2026-43319`

- **Identifiers:** `CVE-2026-43319`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 8 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 8 May 2026, 13:26 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: `a720416d94634068951773cb9e9d6f1b73769e5b to before fabfed1afe273717ea33b8aee46b767360edbb80` (git)
  - affected: `a720416d94634068951773cb9e9d6f1b73769e5b to before f8431b8672231d378b03176fe74c95adfd3522cf` (git)
  - affected: `a720416d94634068951773cb9e9d6f1b73769e5b to before e341e18215030af2136836b78508e0d798916df7` (git)
  - affected: `a720416d94634068951773cb9e9d6f1b73769e5b to before 41ccfac7d302968a4f32b5f7b012d066c5f5cdf8` (git)
  - affected: `a720416d94634068951773cb9e9d6f1b73769e5b to before 40534d19ed2afb880ecf202dab26a8e7a5808d16` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.2`
  - unaffected: `before 6.2` (semver)
  - unaffected: `6.6.142 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.75 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.16 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.6 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 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

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0009, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 8 May 2026, 13:26 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43319)
- 8 May 2026, 14:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43319)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/fabfed1afe273717ea33b8aee46b767360edbb80>
- <https://git.kernel.org/stable/c/f8431b8672231d378b03176fe74c95adfd3522cf>
- <https://git.kernel.org/stable/c/e341e18215030af2136836b78508e0d798916df7>
- <https://git.kernel.org/stable/c/41ccfac7d302968a4f32b5f7b012d066c5f5cdf8>
- <https://git.kernel.org/stable/c/40534d19ed2afb880ecf202dab26a8e7a5808d16>

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-43319>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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