CVE-2022-50482
What it is
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Clean up si_domain in the init_dmars() error path A splat from kmem_cache_destroy() was seen with a kernel prior to commit ee2653bbe89d ("iommu/vt-d: Remove domain and devinfo mempool") when there was a failure in init_dmars(), because the iommu_domain cache still had objects. While the mempool code is now gone, there still is a leak of the si_domain memory if init_dmars() fails. So clean up si_domain in the init_dmars() error path.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-908
- Record status
- Analyzed
Affected
- Linux Kernel < 4.14.298
- Linux Kernel < 4.19.264
- Linux Kernel < 5.4.221
- Linux Kernel < 5.10.152
- Linux Kernel < 5.15.76
- Linux Kernel < 6.0.6
- Linux Kernel 6.1
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-50482.md and follow it. Check whether this project is affected by CVE-2022-50482. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0365d6af75f9f2696e94a0fef24a2c8464c037c8
- https://git.kernel.org/stable/c/5cecfe151874b835331efe086bbdcaeaf64f6b90
- https://git.kernel.org/stable/c/620bf9f981365c18cc2766c53d92bf8131c63f32
- https://git.kernel.org/stable/c/724483b585a1b1e063d42ac5aa835707ff2ec165
- https://git.kernel.org/stable/c/749bea542b67513e99240dc58bbfc099e842d508
- https://git.kernel.org/stable/c/c4ad3ae4c6be9d8b0701761c839771116bca6ea3
- https://git.kernel.org/stable/c/d74196bb278b8f8af88e16bd595997dfa3d6fdb0
References
- https://git.kernel.org/stable/c/0365d6af75f9f2696e94a0fef24a2c8464c037c8
- https://git.kernel.org/stable/c/5cecfe151874b835331efe086bbdcaeaf64f6b90
- https://git.kernel.org/stable/c/620bf9f981365c18cc2766c53d92bf8131c63f32
- https://git.kernel.org/stable/c/724483b585a1b1e063d42ac5aa835707ff2ec165
- https://git.kernel.org/stable/c/749bea542b67513e99240dc58bbfc099e842d508
- https://git.kernel.org/stable/c/c4ad3ae4c6be9d8b0701761c839771116bca6ea3
- https://git.kernel.org/stable/c/d74196bb278b8f8af88e16bd595997dfa3d6fdb0