CVE-2022-49608
What it is
In the Linux kernel, the following vulnerability has been resolved: pinctrl: ralink: Check for null return of devm_kcalloc Because of the possible failure of the allocation, data->domains might be NULL pointer and will cause the dereference of the NULL pointer later. Therefore, it might be better to check it and directly return -ENOMEM without releasing data manually if fails, because the comment of the devm_kmalloc() says "Memory allocated with this function is automatically freed on driver detach.".
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.3% 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.3% 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.3% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 4.19.254
- Linux Kernel < 5.4.208
- Linux Kernel < 5.10.134
- Linux Kernel < 5.15.58
- Linux Kernel < 5.18.15
- Linux Kernel 5.19
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-49608.md and follow it. Check whether this project is affected by CVE-2022-49608. 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/13596e6c9e541e90e5fc2c52b23f08b951370da9
- https://git.kernel.org/stable/c/44016a85419ca0d4f1e4d0127b330f8e4e2a57d0
- https://git.kernel.org/stable/c/5595d30c4dc27d939635c3188c68203b6ece1711
- https://git.kernel.org/stable/c/5694b162f275fb9a9f89422701b2b963be11e496
- https://git.kernel.org/stable/c/6194c021496addc11763d1ffa89ce5751889fe3c
- https://git.kernel.org/stable/c/c3b821e8e406d5650e587b7ac624ac24e9b780a8
References
- https://git.kernel.org/stable/c/13596e6c9e541e90e5fc2c52b23f08b951370da9
- https://git.kernel.org/stable/c/44016a85419ca0d4f1e4d0127b330f8e4e2a57d0
- https://git.kernel.org/stable/c/5595d30c4dc27d939635c3188c68203b6ece1711
- https://git.kernel.org/stable/c/5694b162f275fb9a9f89422701b2b963be11e496
- https://git.kernel.org/stable/c/6194c021496addc11763d1ffa89ce5751889fe3c
- https://git.kernel.org/stable/c/c3b821e8e406d5650e587b7ac624ac24e9b780a8