# soc: ti: k3-socinfo: Fix regmap leak on probe failure

CVE record · `CVE-2026-43242`

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

Published by the CVE Program (CNA: Linux) at 6 May 2026, 11:28 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: `c7e8e3e3591cbda98ebe6221e3cc8a971b8eed6e to before c97c21d342838b2a7787b0f1d6ad417e85c906f6` (git)
  - affected: `db5833217f133b74fb76c75c45be07c881d4d985 to before b1006b5892ec8a95d039a89b47e6fd69cf607405` (git)
  - affected: `5f496a9f1c8c7a58f35a8b6bcb826e23c2d58ec0 to before 458136527fe127fd051c1c9537f4540849780d70` (git)
  - affected: `3314310b3f3e69961f421a123ccb1ea9669d75c4 to before d451bf970a0c54b586f8b3161261bdf35d463c99` (git)
  - affected: `06100e642f4b83ec758744e5f992d7a2039ec98f to before eaa16059f9af26d8b8a6f3e887649f58e8ca96c9` (git)
  - affected: `a5caf03188e44388e8c618dcbe5fffad1a249385 to before ab1ac24c407e4df326d7154a4deadd444e9209d9` (git)
  - affected: `a5caf03188e44388e8c618dcbe5fffad1a249385 to before bbaa9e615608c204d384a7d4b1a434580a142d4c` (git)
  - affected: `a5caf03188e44388e8c618dcbe5fffad1a249385 to before c933138d45176780fabbbe7da263e04d5b3e525d` (git)
  - affected: `5108fd2c67647a0b0f65c7c125ef8978b23a68f8` (git)
  - affected: `5.10.238 to before 5.10.252` (semver)
  - affected: `5.15.185 to before 5.15.202` (semver)
  - affected: `6.1.141 to before 6.1.165` (semver)
  - and 3 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.15`
  - unaffected: `before 6.15` (semver)
  - unaffected: `5.10.252 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.202 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.165 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.128 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.0012, the 2nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43242)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/c97c21d342838b2a7787b0f1d6ad417e85c906f6>
- <https://git.kernel.org/stable/c/b1006b5892ec8a95d039a89b47e6fd69cf607405>
- <https://git.kernel.org/stable/c/458136527fe127fd051c1c9537f4540849780d70>
- <https://git.kernel.org/stable/c/d451bf970a0c54b586f8b3161261bdf35d463c99>
- <https://git.kernel.org/stable/c/eaa16059f9af26d8b8a6f3e887649f58e8ca96c9>
- <https://git.kernel.org/stable/c/ab1ac24c407e4df326d7154a4deadd444e9209d9>
- <https://git.kernel.org/stable/c/bbaa9e615608c204d384a7d4b1a434580a142d4c>
- <https://git.kernel.org/stable/c/c933138d45176780fabbbe7da263e04d5b3e525d>

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

---

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