# trace/blktrace: fix memory leak with using debugfs_lookup()

CVE record · `CVE-2023-53408`

- **Identifiers:** `CVE-2023-53408`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-401](https://cwe.mitre.org/data/definitions/401.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Sept 2025
- **Updated:** 23 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Sept 2025, 13:58 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: `78acc7dbd84a8c173a08584750845c31611160f2 to before a2e4b48d6f9b39aa19bafe223f9dd436a692fc80` (git)
  - affected: `30939293262eb433c960c4532a0d59c4073b2b84 to before 3036f5f5ae5210797d95446795df01c1249af9ad` (git)
  - affected: `30939293262eb433c960c4532a0d59c4073b2b84 to before 5286b72fb425291af5f4ca7285d73c16a08d8691` (git)
  - affected: `30939293262eb433c960c4532a0d59c4073b2b84 to before 83e8864fee26f63a7435e941b7c36a20fd6fe93e` (git)
  - affected: `6418634238ade86f2b08192928787f39d8afb58c` (git)
  - affected: `5.15.27 to before 5.15.99` (semver)
  - affected: `5.16.13 to before 5.17` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `5.15.99 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.16 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2.3 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

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 16 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 18 Sept 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/a2e4b48d6f9b39aa19bafe223f9dd436a692fc80>
- <https://git.kernel.org/stable/c/3036f5f5ae5210797d95446795df01c1249af9ad>
- <https://git.kernel.org/stable/c/5286b72fb425291af5f4ca7285d73c16a08d8691>
- <https://git.kernel.org/stable/c/83e8864fee26f63a7435e941b7c36a20fd6fe93e>

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

---

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