# firmware: xilinx: don't make a sleepable memory allocation from an atomic context

CVE record · `CVE-2023-53099`

- **Identifiers:** `CVE-2023-53099`
- **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:** 23 May 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: `acfdd18591eaac25446e976a0c0d190f8b3dbfb1 to before b37d3ccbd549494890672136a0e623eb010d46a7` (git)
  - affected: `acfdd18591eaac25446e976a0c0d190f8b3dbfb1 to before 86afb633beaa02ee95b5126a14c9f22cfade4fd9` (git)
  - affected: `acfdd18591eaac25446e976a0c0d190f8b3dbfb1 to before 162049c31eb64308afa22e341a257a723526eb5c` (git)
  - affected: `acfdd18591eaac25446e976a0c0d190f8b3dbfb1 to before 9bbab2843f2d1337a268499a1c02b435d2985a17` (git)
  - affected: `acfdd18591eaac25446e976a0c0d190f8b3dbfb1 to before 38ed310c22e7a0fc978b1f8292136a4a4a8b3051` (git)
  - affected: `a38a99930883fb1e24f2a34b78a05a6598e86150` (git)
  - affected: `5.9.12 to before 5.10` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.10`
  - unaffected: `before 5.10` (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.0015, the 4th percentile, on 20 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 2 May 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/b37d3ccbd549494890672136a0e623eb010d46a7>
- <https://git.kernel.org/stable/c/86afb633beaa02ee95b5126a14c9f22cfade4fd9>
- <https://git.kernel.org/stable/c/162049c31eb64308afa22e341a257a723526eb5c>
- <https://git.kernel.org/stable/c/9bbab2843f2d1337a268499a1c02b435d2985a17>
- <https://git.kernel.org/stable/c/38ed310c22e7a0fc978b1f8292136a4a4a8b3051>

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

---

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