CVE-2022-49726
What it is
In the Linux kernel, the following vulnerability has been resolved: clocksource: hyper-v: unexport __init-annotated hv_init_clocksource() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, arch/x86/kernel/cpu/mshyperv.c is never compiled as modular. (CONFIG_HYPERVISOR_GUEST is boolean)
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-908
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.200
- Linux Kernel < 5.10.124
- Linux Kernel < 5.15.49
- Linux Kernel < 5.18.6
- 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-49726.md and follow it. Check whether this project is affected by CVE-2022-49726. 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/0414eab7c78f3518143d383e448d44fc573ac6d2
- https://git.kernel.org/stable/c/245b993d8f6c4e25f19191edfbd8080b645e12b1
- https://git.kernel.org/stable/c/937fcbb55a1e48a6422e87e8f49422c92265f102
- https://git.kernel.org/stable/c/cff3a7ce6e81418b6e8bac941779bbf5d342d626
- https://git.kernel.org/stable/c/db965e2757d95f695e606856418cd84003dd036d
References
- https://git.kernel.org/stable/c/0414eab7c78f3518143d383e448d44fc573ac6d2
- https://git.kernel.org/stable/c/245b993d8f6c4e25f19191edfbd8080b645e12b1
- https://git.kernel.org/stable/c/937fcbb55a1e48a6422e87e8f49422c92265f102
- https://git.kernel.org/stable/c/cff3a7ce6e81418b6e8bac941779bbf5d342d626
- https://git.kernel.org/stable/c/db965e2757d95f695e606856418cd84003dd036d