# iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe()

CVE record · `CVE-2022-49323`

- **Identifiers:** `CVE-2022-49323`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-476](https://cwe.mitre.org/data/definitions/476.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:10 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: `9648cbc9625b67c91ed1aaf4b8b77f3f0c537496 to before 3660db29b0305f9a1d95979c7af0f5db6ea99f5d` (git)
  - affected: `9648cbc9625b67c91ed1aaf4b8b77f3f0c537496 to before 98dd53a92825747395649f54d23512a13c3ed471` (git)
  - affected: `9648cbc9625b67c91ed1aaf4b8b77f3f0c537496 to before 80776a71340f57d6a4952635fc89f0342072f3ca` (git)
  - affected: `9648cbc9625b67c91ed1aaf4b8b77f3f0c537496 to before 449fc4561762ad9ad85362d5f01f0d0df397457a` (git)
  - affected: `9648cbc9625b67c91ed1aaf4b8b77f3f0c537496 to before d9ed8af1dee37f181096631fb03729ece98ba816` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.11`
  - unaffected: `before 4.11` (semver)
  - unaffected: `5.10.122 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.47 to 5.15.*, inclusive` (semver)
  - unaffected: `5.17.15 to 5.17.*, inclusive` (semver)
  - unaffected: `5.18.4 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 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.0028, the 20th 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 26 Feb 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/3660db29b0305f9a1d95979c7af0f5db6ea99f5d>
- <https://git.kernel.org/stable/c/98dd53a92825747395649f54d23512a13c3ed471>
- <https://git.kernel.org/stable/c/80776a71340f57d6a4952635fc89f0342072f3ca>
- <https://git.kernel.org/stable/c/449fc4561762ad9ad85362d5f01f0d0df397457a>
- <https://git.kernel.org/stable/c/d9ed8af1dee37f181096631fb03729ece98ba816>

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

---

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