# s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup

CVE record · `CVE-2022-48636`

- **Identifiers:** `CVE-2022-48636`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **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:** 28 Apr 2024
- **Updated:** 5 Aug 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 28 Apr 2024, 12:59 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: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before d86b4267834e6d4af62e3073e48166e349ab1b70` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before 49f401a98b318761ca2e15d4c7869a20043fbed4` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before aaba5ff2742043705bc4c02fd0b2b246e2e16da1` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before 2e473351400e3dd66f0b71eddcef82ee45a584c1` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before f5fcc9d6d71d9ff7fdbdd4b89074e6e24fffc20b` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before d3a67c21b18f33c79382084af556557c442f12a6` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before 650a2e79d176db753654d3dde88e53a2033036ac` (git)
  - affected: `8e09f21574ea3028d5629e5de759e0b196c690c5 to before db7ba07108a48c0f95b74fabbfd5d63e924f992d` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.25`
  - unaffected: `before 2.6.25` (semver)
  - unaffected: `4.9.330 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.295 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.260 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.215 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.146 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.71 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.12 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0 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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux) (used for this record)
- 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.0024, the 14th 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 28 Apr 2024. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/d86b4267834e6d4af62e3073e48166e349ab1b70>
- <https://git.kernel.org/stable/c/49f401a98b318761ca2e15d4c7869a20043fbed4>
- <https://git.kernel.org/stable/c/aaba5ff2742043705bc4c02fd0b2b246e2e16da1>
- <https://git.kernel.org/stable/c/2e473351400e3dd66f0b71eddcef82ee45a584c1>
- <https://git.kernel.org/stable/c/f5fcc9d6d71d9ff7fdbdd4b89074e6e24fffc20b>
- <https://git.kernel.org/stable/c/d3a67c21b18f33c79382084af556557c442f12a6>
- <https://git.kernel.org/stable/c/650a2e79d176db753654d3dde88e53a2033036ac>
- <https://git.kernel.org/stable/c/db7ba07108a48c0f95b74fabbfd5d63e924f992d>

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

---

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