# ftrace: Fix invalid address access in lookup_rec() when index is 0

CVE record · `CVE-2023-53075`

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

Published by the CVE Program (CNA: Linux) at 2 May 2025, 15:55 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: `9644302e3315e7e36495d230d5ac7125a316d33e to before 2de28e5ce34b22b73b833a21e2c45ae3aade3964` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before 7569ee04b0e3b32df79f64db3a7138573edad9bc` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before ac58b88ccbbb8e9fb83e137cee04a856b1ea6635` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before 83c3b2f4e7c61367c7b24551f4c6eb94bbdda283` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before 2a0d71fabfeb349216d33f001a6421b1768bd3a9` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before 4f84f31f63416b0f02fc146ffdc4ab32723eb7e8` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before f1bd8b7fd890d87d0dc4dedc6287ea34dd07c0b4` (git)
  - affected: `9644302e3315e7e36495d230d5ac7125a316d33e to before ee92fa443358f4fc0017c1d0d325c27b37802504` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.5`
  - unaffected: `before 3.5` (semver)
  - unaffected: `4.14.311 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.279 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.238 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.176 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.104 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.21 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2.8 to 6.2.*, inclusive` (semver)
  - unaffected: `6.3 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.0021, the 10th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 2 May 2025, 15:55 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2023-53075)
- 2 May 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-53075)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/2de28e5ce34b22b73b833a21e2c45ae3aade3964>
- <https://git.kernel.org/stable/c/7569ee04b0e3b32df79f64db3a7138573edad9bc>
- <https://git.kernel.org/stable/c/ac58b88ccbbb8e9fb83e137cee04a856b1ea6635>
- <https://git.kernel.org/stable/c/83c3b2f4e7c61367c7b24551f4c6eb94bbdda283>
- <https://git.kernel.org/stable/c/2a0d71fabfeb349216d33f001a6421b1768bd3a9>
- <https://git.kernel.org/stable/c/4f84f31f63416b0f02fc146ffdc4ab32723eb7e8>
- <https://git.kernel.org/stable/c/f1bd8b7fd890d87d0dc4dedc6287ea34dd07c0b4>
- <https://git.kernel.org/stable/c/ee92fa443358f4fc0017c1d0d325c27b37802504>

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

---

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