# can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock

CVE record · `CVE-2023-52638`

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

Published by the CVE Program (CNA: Linux) at 3 Apr 2024, 14:54 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: `5b9272e93f2efe3f6cda60cc2c26817b2ce49386 to before 03358aba991668d3bb2c65b3c82aa32c36851170` (git)
  - affected: `5b9272e93f2efe3f6cda60cc2c26817b2ce49386 to before aedda066d717a0b4335d7e0a00b2e3a61e40afcf` (git)
  - affected: `5b9272e93f2efe3f6cda60cc2c26817b2ce49386 to before 26dfe112ec2e95fe0099681f6aec33da13c2dd8e` (git)
  - affected: `5b9272e93f2efe3f6cda60cc2c26817b2ce49386 to before 559b6322f9480bff68cfa98d108991e945a4f284` (git)
  - affected: `5b9272e93f2efe3f6cda60cc2c26817b2ce49386 to before 6cdedc18ba7b9dacc36466e27e3267d201948c8d` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.15`
  - unaffected: `before 5.15` (semver)
  - unaffected: `5.15.149 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.79 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.18 to 6.6.*, inclusive` (semver)
  - unaffected: `6.7.6 to 6.7.*, inclusive` (semver)
  - unaffected: `6.8 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.0018, the 7th percentile, on 21 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 3 Apr 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/03358aba991668d3bb2c65b3c82aa32c36851170>
- <https://git.kernel.org/stable/c/aedda066d717a0b4335d7e0a00b2e3a61e40afcf>
- <https://git.kernel.org/stable/c/26dfe112ec2e95fe0099681f6aec33da13c2dd8e>
- <https://git.kernel.org/stable/c/559b6322f9480bff68cfa98d108991e945a4f284>
- <https://git.kernel.org/stable/c/6cdedc18ba7b9dacc36466e27e3267d201948c8d>

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

---

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